Connect gateway →
High-risk processor for Shopify

Connect any high-risk processor to Shopify. We are the routing layer, not the MID.

Most searches for "high-risk payment processor Shopify" return acquirers pitching a MID. That is one half. The other half is the software that lets Shopify checkout talk to that MID — because Shopify's native checkout only accepts a short list of approved gateways, and high-risk providers rarely appear on it. CascadeCheckout is the software half. Bring the MID you have. We wire it into Shopify checkout on your own domain and rotate to a backup MID when the primary throttles.

See pricing →   How it works →

What usually happens next

Operator gets approved at a high-risk desk (NMI reseller, Nuvei, offshore acquirer). Signs a contract. Gets API credentials. Then discovers Shopify's native checkout does not accept the gateway on the API creds. Shopify's approved third-party list is short and mainstream. High-risk MIDs almost never appear on it.

Default fixes are ugly. Route buyers to a shared marketplace URL (Whop, vendor-checkout) — kills conversion. Bolt on a custom Ruby Storefront rebuild — 2-4 weeks of engineering. Or accept the whitelist and stay on Shopify Payments risk — which is the exact rail the operator is trying to escape.

Own-domain checkout via CascadeCheckout is the shorter path. Point Shopify's Buy button at checkout.your-brand.com. On that page, we call the high-risk gateway's API with card token → capture. Order writes back to Shopify Admin. Buyer never sees a marketplace URL.

Why we are NOT the processor

CascadeCheckout does not underwrite a MID. We do not have a bank relationship you inherit. We do not decide whether your product category is approved. We do not touch the funds. What we do is stand up the checkout page and route each attempted transaction to whichever MID you plug in.

This split matters because "high-risk processor" and "high-risk checkout" are different products. The processor decides whether your MCC is acceptable and sets your reserve. The checkout decides how many MIDs you can run in parallel and what happens when the primary declines. We are the second thing.

What Cascade actually does

1

Wire your MIDs

API keys for each high-risk gateway. One MID for Starter. Up to four for Growth. Unlimited for Scale.

2

Checkout on your domain

Own-domain URL with TLS + PCI tokenization. Buyers stay on your brand.

3

Rotate on failure

Cascade rotates when a MID declines, throttles, or trips a velocity block. Next MID captures in under 400ms.

If you do not have a high-risk MID yet. We can point you to acquirers active in your vertical, but we are not the acquirer. You still contract with the MID provider directly. The best time to sign up for a second MID is before the first one starts throttling.

What we do NOT do

What Cascade is best for

Frequent questions

Do you provide the high-risk MID?

No. We do not underwrite MIDs. You bring the MID from your own acquirer or high-risk gateway (NMI, Nuvei, Airwallex, Adyen high-risk desk, Whop, PXP, offshore). We are the software routing layer above the MIDs you already have or will get.

Which high-risk gateways can I connect?

Any gateway with an API — NMI, Nuvei, Adyen (high-risk desk), Airwallex, Checkout.com, PXP, Whop, Trustly, Coinbase Commerce, MyFatoorah, custom HTTP endpoints.

Can I connect a high-risk MID to Shopify natively?

Only if the MID's gateway is on Shopify's approved third-party list — most high-risk MIDs are not. Own-domain checkout via CascadeCheckout removes that restriction; you plug in any high-risk gateway with an API.

How does cascade routing help with high-risk?

High-risk MIDs throttle, restrict velocity, or terminate faster than mainstream ones. Running two or three in parallel means when one starts declining above threshold, the next captures without buyer-visible failure.

Bring your MID. We wire it to Shopify.

24-48 hours from API keys to first live capture.

See pricing →

Shopify Payments banned → · Payment gateway cascade → · NMI Shopify checkout →