The verdict in three sentences
The moment your marketplace passes a handful of vendors, manual payouts become a sink of time and errors. The disbursement API (M-Pesa B2C, MTN MoMo, Airtel Money) processes batches of hundreds of payouts in one request, with confirmation callbacks and automatic retry. Well run, it pays all your vendors the same day, handles the 3% failures and reconciles by batch ID.
Comparing disbursement APIs
The major operators offer similar capabilities, with nuances worth knowing:
| Operator | Payout fee | Batch size | Callback | Daily cap |
|---|---|---|---|---|
| M-Pesa B2C | ~1% | Up to 1,000 | Yes, real time | 5,000,000 FCFA |
| MTN MoMo | ~1% | Up to 1,000 | Yes, async | 5,000,000 FCFA |
| Airtel Money | ~1.2% | Up to 500 | Yes, async | 3,000,000 FCFA |
M-Pesa B2C stands out with a real-time callback confirming each payout individually, while MTN and Airtel confirm the batch asynchronously. For a multi-operator marketplace, you route each vendor to their own operator.
Handling failures: retry and per-batch reconciliation
No payout is 100% reliable. Here are the failure causes and observed rates:
| Failure cause | Rate (2026 estimate) | Handling |
|---|---|---|
| Wrong / inactive number | ~1.5% | Notify vendor, correct |
| Recipient cap reached | ~0.8% | Defer to next batch |
| Operator timeout | ~0.5% | Auto retry 2x |
| Insufficient platform balance | ~0.2% | Treasury alert |
Overall you see about 3% failures per batch. The rule: an automatic retry twice absorbs most timeouts, then residual failures go to a manual queue. Each batch carries a unique ID enabling reconciliation to the last unit: amount sent = sum of successful payouts + amount of failures requeued.
The idempotent batch architecture
As with webhooks, a payout batch must be idempotent: if you re-run a batch after a network timeout, you must not pay twice. You assign an idempotency key per payout (vendor ID + period + amount) that the operator recognizes to ignore duplicates. That is what makes retry safe.
Mini case study
Koffi operates a services marketplace in Nairobi with 80 vendors paid every week, for a payout volume of 6,400,000 FCFA weekly. Manually he spends 5 hours a week keying in numbers and amounts, with a non-trivial risk of entry error.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Switching to the disbursement API, he sends a single batch: prep time 20 minutes, execution a few seconds. The 1% fees come to 64,000 FCFA per week. Of 80 payouts, about 2 to 3 fail (wrong number), caught by retry or manual handling. Gain: 4 hrs 40 per week, over 18 hours a month returned to the business, and zero entry errors.
FAQ
How much are payout fees per operator?
About 1% on M-Pesa B2C and MTN MoMo, 1.2% on Airtel Money as a 2026 order of magnitude. On a 6,400,000 FCFA batch that is 64,000 to 77,000 FCFA.
What failure rate should I expect?
About 3% per batch, mostly wrong or inactive numbers (~1.5%). An automatic retry twice absorbs most timeouts.
How many recipients per batch?
Up to 1,000 recipients on M-Pesa and MTN, 500 on Airtel. Beyond that you split into several batches, each with its reconciliation ID.
Is there a daily payout cap?
Yes, around 5,000,000 FCFA/day on M-Pesa and MTN, 3,000,000 on Airtel. Large volumes are spread out or use a negotiated cap increase.
Could retry pay twice?
No, if you use an idempotency key per payout. The operator recognizes the duplicate and ignores it, making retry completely safe.
Let's talk about your project. We automate your multi-operator vendor payouts with retry, idempotency and per-batch reconciliation. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
