The verdict in three sentences
With a single PSP, every processor outage = 100% lost sales during the incident, while the average failure rate climbs to 8–18% at peak. An orchestration layer routes each transaction to the cheapest/most-available provider and retries the failure on another PSP, recovering 20–30% of failed payments. The orchestration cost (aggregator +0.5–1%) is trivial against the sales saved and uptime rising from ~99.3% to 99.9%.
Single integration vs orchestration layer
A single-PSP integration is simple but fragile: if Paystack hiccups, everything falls. An orchestration layer plugs in several PSPs (Paystack, Flutterwave, plus an aggregator) and applies routing rules by amount, detected operator and country. The customer sees nothing: on failure, the transaction automatically fails over to the fallback.
| Criterion | Single PSP | Multi-PSP orchestration |
|---|---|---|
| Effective uptime | ~99.3% | ~99.9% |
| Loss during outage | 100% | ~0–20% |
| Recovery on retry | 0% | 20–30% |
| Added cost | 0 | +0.5–1% (aggregator) |
| Integration complexity | Low | Medium |
| Fee optimisation | No | Yes (routes cheapest) |
Routing rules and 2026 fees
Orchestration's value lies in its rules: route by the number's operator, the amount, or real-time availability, and fail over on the first failure.
| Routing rule | Primary PSP | Fallback | Primary fee | Conversion gain |
|---|---|---|---|---|
| Card payment | Paystack | Flutterwave | 1.5% + ₦100 (cap ₦2,000) | +3–5% |
| Bank transfer / USSD | Flutterwave | Paystack | 1.4% | +3–5% |
| Unknown method | Aggregator | Paystack | +0.5–1% | +2–4% |
| Large amount (>₦500,000) | Most reliable PSP | 2nd PSP | variable | +2–3% |
| Peak-hour failure | Cross-PSP retry | 3rd option | — | +20–30% of failed |
*2026 estimates; typical webhook latency 200ms–3s.*
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.
Emeka runs an online store in Lagos doing ₦20m/month. On a single PSP with 12% failures at peak, he loses ₦2.4m of failed attempts, part of them permanently. Adding orchestration (Paystack + Flutterwave) that retries failures and recovers 25% saves ₦600,000/month. The aggregator surcharge (+0.75% on routed revenue) costs ~₦150,000, for a net gain of ₦450,000/month — before counting the uptime that reassures customers.
FAQ
What's the average PSP failure rate? At peak, expect 8–18% failures (processor downtime, timeouts, insufficient balance), which is why automatic fallback matters.
How much does a cross-PSP retry recover? Replaying a failure on a second PSP recovers 20–30% of failed payments — sales that would be lost on a single PSP.
What does orchestration cost? An aggregator adds roughly +0.5 to 1% on routed transactions, easily offset by saved sales and routing to the cheapest PSP.
What uptime should I target? Orchestration targets 99.9% vs ~99.3% on a single PSP: over a month, the difference between ~5h and ~40min of downtime.
What webhook latency should I expect? Payment confirmation typically arrives in 200ms to 3s; beyond that, plan a "pending" status and asynchronous reconciliation.
Become a Kolonell referral partner
Know online merchants losing sales to every processor outage? Introduce them to Kolonell: 12% on an e-commerce build, 15% + 5% recurring on a showcase site, 10% on a marketplace, 8% on institutional. The referral (apporteur d'affaires) programme rewards every successful introduction.
Let's talk about your project. We deploy your multi-PSP orchestration so no outage costs you 100% of your sales again. 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.
