Multiple gateways

Multiple payment gateways on Shopify: how to get real failover, not just more buttons.

Shopify lets you offer several payment methods, but only one provider captures cards, and if that provider declines or goes down the sale is gone. Merchants who have lost a processor once tend to want two. This page explains what Shopify can and cannot do here, and how a cascade routes each attempt across several gateways.

See pricing → How it works →

What Shopify allows

One credit card provider active at a time: Shopify Payments or one third-party gateway.
Wallets and alternative methods beside it: PayPal, Shop Pay, Apple Pay, Google Pay, buy-now-pay-later, crypto, manual methods.
Payment customisation functions that hide, rename or reorder methods based on cart, customer or address.

What it does not allow: two card processors, routing by card BIN or region, or retrying a declined card on another provider. A decline is final at the checkout.

Why merchants want more than one

Outages. Every gateway has them. With one provider, a thirty-minute outage during a launch is thirty minutes of zero revenue.
Soft declines. Issuers decline for reasons that have nothing to do with the buyer's funds: velocity rules, 3DS friction, a risky acquirer country. A second acquirer often approves the same card.
Geography. A domestic acquirer approves domestic cards better. Two acquirers in two regions beat one global one.
Category risk. If your first processor tightens its policy, a second one already live means the change is a rotation, not a rebuild.
Cost. Route high-ticket or low-risk orders to the cheaper acquirer and the rest to the one that approves.

How a cascade works

Routes in priority order

Two, three or four gateway accounts wired behind one checkout, each with health checks and its own credentials.

Every attempt is classified

Hard declines such as stolen card stop. Soft declines, timeouts, throttles and 3DS failures that a second acquirer could clear move on.

Next route captures

The retry happens server-side inside about 400 milliseconds. The buyer sees one spinner and one confirmation. The order lands in Shopify tagged with the route that captured.

Because the checkout is on your own domain, the card is tokenised once and each route is tried with that token; the buyer does not re-enter anything. Idempotency keys guarantee that no cart is charged twice across routes. Deeper detail on the cascade.

What it looks like in your Shopify admin

Each paid order arrives with its line items, buyer, shipping address, discount code and shipping method, plus tags such as [cascade] and [cascade:route-2]. Refunds go back through the route that captured. Reports, fulfilment apps and email flows keep working because the order is a normal Shopify order. What changes is only where the card was captured.

Setting it up

Open accounts with two processors that underwrite your category, ideally on different acquiring banks and, if you sell internationally, in different regions.
Send CascadeCheckout the API keys for each. We wire checkout.your-brand.com, the routes, health checks and order write-back.
Run one live order per route and confirm each lands in Shopify.
Set the priority order and any rules: region, ticket size, product line.
Watch the dashboard for approval rate by route and rotate priorities when one drifts.

Growth plans include up to four routes; adding or swapping a route later is a configuration change, not a rebuild. Plans.

Frequent questions

Can I have two payment gateways on Shopify?

Only one card gateway at a time in Shopify's own checkout, alongside wallets and alternative methods. Two card processors with failover require an external checkout that routes between them.

Does failover charge the buyer twice?

No. Each cart carries an idempotency key across every route, and a route is only tried after the previous one returned a decline or timed out.

How fast is the rotation?

Median rotation is under 400 milliseconds, server-side, so the buyer sees a single loading state.

Which gateways can be routes?

Any gateway with an API: NMI, Nuvei, Airwallex, Checkout.com, PXP, Adyen, Whop, regional acquirers, crypto rails and custom HTTP endpoints.

Bring your store URL and the gateway that already said yes.

Live in 24-48 hours. Founder-answered support on WhatsApp.

See pricing →

Payment gateway cascade → · Payment orchestration → · Processors to pair → · How it works →

CascadeCheckout is checkout software, not a payment service provider, bank or merchant-account seller. You contract with your own gateway or acquirer, disclose your real business category to them, and receive payouts from them. We never hold funds and we do not promise that any processor will approve you.