The verdict in three sentences
A failed transaction is not always a lost sale: with orchestration, you replay the payment on another provider within seconds. If Paystack returns an error, the customer routes to Flutterwave or Monnify without leaving the checkout. Tuned well, this cascade recovers 4 to 9 points of conversion, which flows straight to revenue.
How routing works
An orchestration engine applies rules: trigger (failure, timeout, low success rate), action (retry, failover, queue), limit (max attempts). Here are the most profitable rules (conversion-point uplift, 2026 order of magnitude).
| Routing rule | Trigger | Action | Estimated uplift |
|---|---|---|---|
| Provider failover | Paystack failure | Route to Flutterwave | +2 to +4 pts |
| Timed retry | Network timeout | Replay after 20-40 s | +1 to +3 pts |
| Method fallback | Two card failures | Offer bank/USSD | +1 to +2 pts |
| Cost-based routing | Same method, 2 gateways | Pick the cheaper | -0.3 to -0.6 pt of fees |
| Anti-fraud cap | Too many attempts / IP | Block and alert | Cuts chargebacks |
The typical cascade: Paystack -> Flutterwave -> Monnify (or bank/USSD). Three chances instead of one, with no painful re-entry for the customer.
What it costs, and build vs buy
An orchestration engine is judged on setup and maintenance cost against conversion gain. Order of magnitude for a store doing meaningful monthly volume.
| Option | Setup | Monthly cost | Timeline |
|---|---|---|---|
| Simple rules (in-house) | Low-to-moderate | Maintenance only | 3 - 7 days |
| Custom advanced engine | Higher one-off | Server + monitoring | 2 - 4 weeks |
| Orchestration SaaS | Low | % or subscription | 1 - 2 weeks |
Decision rule: below high monthly volume, simple in-house rules are enough. Above it, an advanced engine or dedicated solution pays back fast because every conversion point is worth a lot.
Mini case study
Emeka runs a Lagos electronics store doing solid monthly sales at an 88 % payment success rate. We add a cascade: Paystack -> Flutterwave -> bank transfer. Success climbs to 93 %, a +5-point gain. On his volume that recovers meaningful monthly revenue that would otherwise go to competitors. The engine was a one-off build: paid back in under six weeks.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Does orchestration slow down checkout?
No, when tuned: failover fires only after a failure or timeout, in 1 to 3 seconds. Customers whose first choice succeeds notice nothing.
How many conversion points can I really gain?
Between 4 and 9 points depending on baseline quality and method mix. Moving an 88 % success store to 92-94 % is realistic.
Do I need multiple gateways?
Not at first: cascading between card, bank transfer and USSD via a single gateway captures most of the gain. Multi-gateway mainly hedges against provider outages.
How do I avoid infinite retries?
Set a cap (2-3 attempts max) and an anti-fraud rule per IP/card. That protects against chargebacks and provider blocks.
Should I build or buy the engine?
Below high monthly volume, simple in-house rules suffice (3-7 days). Above it, an advanced engine or a dedicated SaaS is justified.
Let's talk about your project. We install a payment cascade that recovers your lost sales. 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.