Multiple payment gateways: when two providers beat one

Using multiple payment gateways makes sense when one provider can't cover every payment method your customers want, when downtime would cost you real money, or when you sell in more than one country. For many small businesses a single gateway is enough; the case for a second one grows with your volume, your customer mix and how much a failed checkout hurts.

Below is a practical way to decide, plus the routing patterns and back-office habits that stop a multi-gateway setup turning into a reconciliation headache.

Why businesses add a second gateway

Payment method coverage

No provider offers every method. One gateway may be strong on cards and QR wallets, another on instant EFT, and a third on mobile money in East Africa. If a meaningful share of customers want a method your gateway lacks, a second provider pays for itself quickly.

Resilience

Every provider has incidents, planned maintenance or bank-side problems. With a second gateway ready, you can switch checkout traffic across while the first recovers, rather than losing sales for hours.

Cross-border reach

South African gateways are built around ZAR and local methods. If you also sell in Kenya, Nigeria or Ghana, a pan-African provider such as Paystack, Flutterwave, DPO Pay or Pesapal, or direct M-Pesa and MTN MoMo integrations, can handle local methods there.

Cost and negotiating power

Different providers price different methods differently. Routing each method to the provider that suits it can lower your blended cost, and having an alternative gives you a stronger position when you negotiate rates.

Different products for different jobs

A common South African combination: a card and EFT gateway for online checkout, a card machine provider in store, and a debit order provider for monthly collections. These are separate tools doing separate jobs.

The costs of running more than one

Be honest about the downsides before adding a provider.

• More integration work. Each gateway has its own API, webhooks and test environment.
• More onboarding. Each provider verifies your business separately.
• Split reporting. Payouts arrive from several sources on different schedules, with different settlement report formats.
• Saved cards don't move. Card tokens are tied to the gateway that issued them, so subscribers on gateway A can't simply be charged through gateway B. See card tokenisation explained for why.
• Lower volume per provider. Splitting volume may reduce your ability to reach volume discount tiers.

Four routing patterns

Most businesses should start with method-based or purpose-based routing. They're predictable, easy to explain to your support team, and don't need clever real-time logic. Automatic failover is valuable, but make sure you can detect an outage reliably first, or you'll end up flip-flopping.

A note on retries: re-sending a declined card to a different gateway isn't a fix for genuine declines. If the issuing bank declined for insufficient funds or suspected fraud, a second gateway will generally get the same answer, and repeated attempts can look suspicious. Failover is for provider outages, not for decline codes. Our guide to card declined reasons explains which declines are worth retrying.

A worked example

A Cape Town online training company sells courses once-off and a monthly membership at R299.00. Customers in South Africa and Kenya.

• Checkout in South Africa: Gateway A for cards, Apple Pay and instant EFT.
• Checkout in Kenya: M-Pesa STK Push via Daraja, so customers approve on their phone.
• Memberships: saved cards on gateway A; members who prefer not to use cards pay by debit order.
• Backup: gateway B is configured and tested but hidden; if gateway A has an incident, the team switches card checkout to B.

The finance team receives payouts from three sources. To keep month-end sane, every payment is recorded against a single invoice or order reference, regardless of which provider collected it.

Keeping the back office under control

The real work of multiple gateways is in finance, not checkout.

1. One source of truth for what's owed. Invoices and subscriptions should live in one system, with each payment linked back to them.
2. Consistent references. Pass your invoice or order number to every gateway so it appears in their reports.
3. Verify every webhook. Check signatures and confirm the payment status with the gateway before marking anything paid.
4. Reconcile payouts, not just payments. Match each bank deposit to the gateway payout, and each payout to the payments and fees inside it.
5. Keep an exceptions queue. Unmatched deposits, missing payouts and refunds need an owner.

Our reconciliation docs show how statement matching works in practice.

Should you add a second gateway? A quick test

Answer yes or no:

• More than a small share of customers ask for a method you don't offer.
• An hour of checkout downtime would cost more than a day of extra admin.
• You sell, or plan to sell, outside South Africa.
• You collect both once-off payments and recurring debits.
• You have someone who can own reconciliation across providers.

Two or more yes answers suggest a second gateway is worth exploring. If the last answer is no, fix that first. For choosing which provider to add, see how to choose a payment gateway in South Africa.

How CentraPoint helps

CentraPoint is built for multi-gateway setups. PayFast, Netcash Pay Now and Debit Orders, Ozow, Yoco, Peach Payments, PayGate, Paystack, Flutterwave, DPO Pay, Pesapal, M-Pesa Daraja STK Push, MTN MoMo and manual EFT are enabled as separate modules, all feeding the same invoices, subscriptions and reports. Inbound gateway webhooks are signature-checked and then re-verified server-side, and statement import auto-matches collections, fees and payouts, leaving an exception queue for anything that doesn't match.

Frequently asked questions

Is it allowed to use more than one payment gateway?

Generally yes. Most businesses can contract with several providers, but read each agreement for exclusivity clauses or volume commitments before you sign.

Can I move subscribers from one gateway to another?

Not automatically, because saved-card tokens only work on the gateway that issued them. You usually need customers to re-enter card details, unless both providers support a secure card-data migration.

Does a second gateway reduce declined payments?

It helps when the problem is a provider outage. It usually doesn't help with genuine issuer declines such as insufficient funds, which will typically be declined by the bank whichever gateway you use.

How do I reconcile payments from several gateways?

Link every payment to one invoice or order reference, then match each bank deposit to a gateway payout and each payout to its individual payments and fees. Software that imports statements and auto-matches saves most of the effort.