Platform
Fees & Pricing
The Orchestrator uses a volume-tiered per-transaction fee model. No subscriptions, no monthly seat fees, no percentage-based revenue share.
Volume Tiers
Your rate is determined by your 30-day rolling processing volume.
| 30-Day Volume | Rate | Fee on GHS 1,000 |
|---|---|---|
| Below GHS 100K | 150 bps (1.5%) | GHS 1.50 |
| GHS 100K — GHS 1M | 125 bps (1.25%) | GHS 1.25 |
| GHS 1M — GHS 5M | 100 bps (1.0%) | GHS 1.00 |
| GHS 5M+ | 85 bps (0.85%) | GHS 0.85 |
Fee cap: Each transaction incurs a minimum fee of GHS 0.10 and a maximum fee of GHS 10.00, regardless of the calculated rate.
Fee Breakdown
The total Orchestrator fee on a transaction is composed of several layers. Only the Orchestrator execution fee is variable by tier; network and provider fees are passed through at cost.
| Fee Component | Description |
|---|---|
| Orchestrator Fee | Platform execution fee based on your volume tier |
| Moolre Collection Fee | Moolre's fee for collecting the inbound payment |
| Network Fee | Mobile network operator fee for MoMo transactions |
| Moolre Transfer Fee | Moolre's fee for outbound transfers to recipients |
POST /api/v1/fees/preview
Estimate the Orchestrator fee for a transaction before executing it. Useful for showing cost breakdowns to end users.
{
"amountInPesewas": 10000
}Fee Preview Fields
| Field | Type | Description |
|---|---|---|
| amountInPesewas | integer | Transaction amount in pesewas (e.g. 10000 = GHS 100.00) |
{
"feePesewas": 150,
"rateBps": 150,
"effectiveRate": 1.5
}| Field | Type | Description |
|---|---|---|
| feePesewas | integer | Estimated Orchestrator fee in pesewas |
| rateBps | integer | Applicable rate in basis points |
| effectiveRate | number | Effective rate as a percentage |
Machine-Readable Pricing
Our pricing is also available in machine-readable format at /pricing.md, suitable for automated cost calculation and display in your own applications.