Payment gateway cascade. Multi-MID failover for checkout.

What a payment gateway cascade actually is

Three ingredients:

1. A prioritized list of MIDs. Route 1 primary, route 2 backup, route 3 fallback. Each MID has its own gateway API credentials.
2. A scoring engine per attempt. Every transaction is scored on the response signals: hard decline, soft decline, timeout, 3DS challenge failure, MCC restriction, velocity block. Signals are cheap; running them per attempt is what makes cascade work.
3. An auto-rotation trigger. If the primary returns a failure signal above threshold, the request is re-issued against route 2 immediately with the same card token. Median rotation time under 400ms — inside the buyer's attention span.

Why a single backup gateway is not a cascade

"Backup gateway" usually means a manual switch — the operator notices the primary is down, logs in, changes a setting, hopes buyers refresh. That works for planned outages. It does not work for the two failure modes that actually cost real money:

• Silent degradation. Gateway approval rate quietly drops from 92% to 74% over a week as risk scoring tightens. No outage alert. Just missing revenue.
• Category-specific throttling. Gateway starts declining a specific MCC or a specific corridor while others go through. Manual failover flips everything, including transactions that would have succeeded.

A cascade handles both. Per-attempt scoring catches silent degradation because failed attempts trigger rotation. Per-attempt routing catches category throttling because only affected transactions rotate.

What Cascade actually does

What we do NOT do

• Not a bank. Not a processor. Not a merchant of record.
• Never hold funds. Never touch card data.
• Do not underwrite your MIDs — you contract with each gateway.
• Do not hide your MCC.
• Do not disguise the cascade from the acquirer — the acquirer sees the transaction attempt against their gateway like any other.

When cascade routing pays off

• Multi-MID operators running 2+ gateways in production.
• Post-scale merchants where a single MID's velocity cap starts hurting conversion at peak.
• Category-flagged categories where any single MID has a real ban-risk.
• International brands with corridor-specific decline patterns.

Frequent questions

What is a payment gateway cascade?

A payment gateway cascade is a checkout layer that routes each transaction attempt through the healthiest gateway in a prioritized list of MIDs. When a route declines, times out or throttles, the next route captures the sale — usually under 400ms — so the buyer never sees an error.

Why not just use a single backup payment gateway?

A single backup is a manual failover — someone still has to detect the outage and swap the gateway. A cascade automates that decision per transaction. And running three or four MIDs means a single MID's slow degradation does not silently kill conversion.

Does cascade routing work with any gateway?

Any gateway with an API can join the cascade. Stripe, NMI, Nuvei, Adyen, Airwallex, Checkout.com, Whop, PXP, Coinbase Commerce, Trustly, MyFatoorah, custom HTTP endpoints.

How fast is the failover?

Median rotation under 400ms. Buyer stays on the same checkout page. No visible decline screen. Order writes back to the underlying storefront (Shopify or WooCommerce) tagged with the route that captured.

High-risk processor → · Shopify Payments alternative → · How it works →