Founder online now · WhatsApp reply < 30 min Talk direct →
From $199/mo Talk to founder →
Cascade vs Shopify Payments

Cascade vs Shopify Payments. Different jobs. Different failure modes.

Shopify Payments is a payment processor — it underwrites the MID, holds funds and issues payouts. CascadeCheckout is not a processor. It is a routing layer that sits above whichever processors you plug in. If Shopify Payments is one of your routes, the cascade can rotate to a second MID when Shopify Payments declines, throttles or freezes. Different problems. Different solutions. Usually best used together, not as replacements.

See pricing →   How it works →

What each one actually does

Shopify Payments is a full-stack payment product built into Shopify. It underwrites your MID, tokenizes cards, captures payments, holds funds until payout, manages chargebacks and settles to your bank. When it works, it is the simplest and cheapest way to take cards on Shopify. When it does not work — category restriction, chargeback threshold, freeze, reserve — everything downstream stops.

CascadeCheckout is middleware. It does not underwrite MIDs. It does not hold funds. It does not touch card data. What it does is stand up a checkout page on your own domain and route every transaction attempt through a prioritized list of MIDs — Shopify Payments included, if you want. When one route fails, the next healthy route captures inside 400ms. The buyer never sees a decline.

Side-by-side

Shopify Payments

  • Full processor (MID + acquirer + payouts)
  • Native to Shopify checkout — one-click setup
  • Lowest transaction fee on Shopify plans
  • Shop Pay + native Apple Pay + Google Pay
  • Single point of failure: category restriction, freeze, reserve stops everything
  • Category list — many verticals ineligible

CascadeCheckout

  • Middleware — routes across your MIDs
  • Own-domain checkout (checkout.your-brand.com)
  • Any gateway with an API — no whitelist
  • Multi-MID cascade (up to 4 on Growth, unlimited on Scale)
  • Rotates on decline / throttle / freeze
  • You bring the MIDs; we do not underwrite

When to pick Shopify Payments alone

You are in a low-risk category (apparel, homeware, electronics, standard DTC). You are small enough that a single freeze is survivable. You accept single-processor risk in exchange for lowest fees. You do not want to think about payment infrastructure.

When Cascade wins

You are in a category Shopify Payments often restricts. You have already been cut, reserved, or throttled. You run two or more MIDs and want a decision layer above them. You want the cheapest MID as primary and a specialist MID as fallback. You cannot afford a single-processor outage.

Cascade + Shopify Payments together. The most common Growth-tier config is Shopify Payments as route 1 (cheapest, best UX) with an NMI or offshore MID as route 2 (fallback). If Shopify Payments declines or freezes, route 2 captures. Buyer never sees the switch. Order still writes to Shopify tagged [cascade].

What we do NOT do

Frequent questions

Is CascadeCheckout a replacement for Shopify Payments?

No. Shopify Payments is a payment processor — it underwrites the MID, holds the funds and issues payouts. CascadeCheckout is a routing layer above whichever processors you plug in. If Shopify Payments is one of your routes, we can rotate to a second MID when Shopify Payments declines.

When should I stay on Shopify Payments alone?

Low-risk category, single-MID risk you accept, small enough volume that a single freeze is survivable. Shopify Payments is the most convenient rail while it works — the question is what happens on day one after it stops working.

Can Cascade run alongside Shopify Payments?

Yes. Common pattern is Shopify Payments as route 1 (cheapest, most convenient) with a high-risk-friendly MID as route 2 (fallback). If Shopify Payments cuts you or throttles, route 2 keeps the sale.

Keep Shopify Payments. Add a cascade behind it.

Route 2 catches when route 1 dies. Buyer never sees the switch.

See pricing →

Shopify Payments banned → · Shopify Payments alternative → · How it works →