Payment Orchestration: Multi-Gateway Routing & Fallback (2026)

The verdict in three sentences

A single-gateway setup exposes you to one point of failure: if Paystack, Flutterwave or MoMo declines or goes down, the sale is lost. Payment orchestration routes each transaction to the cheapest, most reliable provider, then fails over to a second one if the first declines — recovering 4 to 9 points of authorization rate. It becomes worthwhile above 2,000 transactions per month; below that, the added development cost is hard to justify.

Single-gateway vs orchestration: what actually changes

With one provider, your authorization rate is capped by that provider's reliability. A "soft" decline (temporary balance issue, network timeout, expired OTP) turns into a permanent abandonment. Orchestration turns that decline into a second chance: the engine reads the decline code, picks another channel and retries in under 2 seconds — often invisibly to the buyer.

The routing table: auth rate + fees per channel

The heart of orchestration is a decision table that ranks providers per transaction. You combine two signals: observed authorization rate (reliability) and all-in cost (fees). In West Africa you typically route Paystack and MoMo first for local, Flutterwave and Stripe for cards/international, with cross-fallback.

The rule: route first to the most reliable channel for the buyer's country, then switch to the second on a soft decline. "Hard" declines (confirmed fraud, blocked account) are never retried.

Mini case study

Awa runs an online cosmetics shop in Dakar: 3,500 transactions/month, average basket 18,000 FCFA, i.e. 63,000,000 FCFA in volume. On single-gateway her authorization rate is 85 %: 525 sales fail, of which roughly 40 % are recoverable via fallback — that's 210 sales × 18,000 = 3,780,000 FCFA lost every month.

With orchestration she climbs to 93 % authorization and recovers that 3,780,000 FCFA. Development costs her 1,800,000 FCFA once. Payback: under 3 weeks. As a bonus, fee arbitrage saves 0.6 % of volume — an extra 378,000 FCFA/month.

FAQ

At what transaction count does orchestration pay off?

As a 2026 order of magnitude, above 2,000 transactions/month. Below that, the 900,000 to 2,500,000 FCFA of development takes too long to amortize against a few points of auth-rate gain.

Does fallback slow down checkout?

Almost never: the retry on a second channel takes 0.8 to 2.0 seconds and usually stays invisible. The buyer sees one payment screen, not two.

Can every decline be retried automatically?

Only "soft" declines (timeout, expired OTP, temporary balance) — about 60 to 70 % of declines. "Hard" declines (fraud, blocked account) are never retried to avoid losses and disputes.

How much does fee arbitrage really save?

Between 0.3 and 1.1 % of volume depending on the channel mix. On 50,000,000 FCFA/month that's 150,000 to 550,000 FCFA in monthly savings.

Do I need a separate contract with each provider?

Yes: each gateway (Paystack, Flutterwave, Stripe) requires its own merchant account and webhooks. The orchestrator unifies the call in code, but the contracts stay separate.

Let's talk about your project. We wire your multi-gateway orchestration with smart routing and tested fallback so you never lose a sale again. WhatsApp +221 77 596 93 33.