The verdict in three sentences
A weekly batch payout via the Flutterwave disbursement API is the best trade-off for a marketplace in Lagos in 2026: it reduces transfer fees (one batch instead of dozens of transfers), smooths cash flow and reassures vendors with a predictable rhythm. On-demand payout looks more attractive but blows up fees and weakens your cash position. With a per-payout cap and automatic retries, the weekly batch scales.
Weekly payout vs on-demand
The rhythm changes everything. Here is a 2026 order-of-magnitude comparison for 40 vendors:
| Criterion | Weekly payout | On-demand payout |
|---|---|---|
| Transfers/month | ~160 (4 batches) | ~600+ |
| Transfer fee (~1 %) | Optimized per batch | Multiplied per transfer |
| Cash-flow predictability | High | Low |
| Vendor satisfaction | Good (clear rhythm) | Variable |
| Operational load | Low (automated) | High |
| Overdraft risk | Controlled | Real |
The weekly batch wins on nearly every axis, except perceived speed for the impatient vendor.
How the disbursement API works
The Flutterwave disbursement API sends money from your merchant account to vendor accounts. Each call must be idempotent: a unique batch identifier prevents a replayed batch from paying twice.
| Parameter | Value (2026 order of magnitude) |
|---|---|
| Transfer fee | ~1 % of amount |
| Per-payout cap | ~₦5,000,000 |
| Vendor credit delay | Near-instant to a few minutes |
| Retries on failure | 3 spaced attempts |
| Final status | SUCCESS / FAILED / PENDING |
A FAILED transfer (wrong number, capped account) is isolated and retried in the next batch, without blocking the rest.
Failure handling and retries
On a batch of 40 transfers, 1 to 2 typically fail (inactive number, receive limit reached). The system never blindly re-sends: it first checks the real status via getStatus before any retry, to avoid paying twice. After 3 failures, the vendor is notified and the amount stays in their payable until fixed.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Chidi runs a crafts marketplace in Lagos with 40 vendors. Monthly volume: ₦28,000,000, of which ₦23,800,000 paid out (85 %). On-demand (~600 transfers, ~1 % each) would cost about ₦238,000 in monthly fees. With weekly batch payouts, grouping transfers, he targets ~1 % on the total but with far less operational load and zero overdraft. The predictable rhythm also halved his vendor complaints.
FAQ
Which day should the weekly payout run?
Monday is common: it settles the past week after the weekend return window. Communicate the day to vendors to build trust.
What happens beyond the payout cap?
The system automatically splits into several batches under the cap. Each batch keeps its unique identifier to stay idempotent and traceable.
Can a vendor request an early payout?
Yes, but charge these on-demand advances (e.g. a flat fee) to cover the extra cost. That preserves the weekly-batch economics for the majority.
How do you avoid a double payout on retry?
Query getStatus before each retry and only re-send if the previous one is truly FAILED. The idempotent batch identifier is the second barrier.
Is payout instant for the vendor?
Usually near-instant to a few minutes on Flutterwave. PENDING cases often resolve on their own; otherwise the next batch retry catches them.
Let's talk about your project. We automate your batch payouts with retries and idempotency. 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.
