From $199/mo
"Workaround" makes the fix sound bigger than it is. In practice it is: one obfuscated line pasted into your Shopify theme, one gateway API credential handed to us, one DNS pointer for your checkout subdomain. From that point on, buyers land on checkout.your-brand.com, cards capture on your gateway, orders write back to Shopify Admin tagged [cascade]. Shopify Payments is out of the loop. Your ads, storefront, apps and fulfillment continue as if nothing changed except the payment button.
Merchants in categories Shopify Payments restricts. Merchants already banned or reserved and unable to keep feeding new revenue into the freeze. Multi-MID operators who need routing across two or three gateways. International brands that want local acquiring in specific corridors. High-risk operators who need a checkout that survives when the primary MID throttles or gets terminated. Any of the above are the workaround's audience.
It is not a way to open a new Shopify Payments account under a different LLC. Shopify correlates aggressively on operator identity — device, bank, EIN, product catalog — and a fresh LLC does not reset the correlation. It is not a way to falsify transaction data sent to your acquirer, and it is not a chargeback-avoidance tool. Those requests we cannot help with.
It is the productized version of the enterprise pattern where Shopify Plus merchants build custom Storefront checkouts on their own domain. Same architecture. Same Shopify APIs (Storefront + Admin). Same order writeback. Difference is you do not need an engineering team; the checkout ships from CascadeCheckout as a subdomain deployment.
The workaround in one sentence. Move the checkout URL off Shopify Payments' rail; keep everything else on Shopify.
Send the API credentials for whichever gateway already approved your MCC. NMI reseller, Adyen high-risk desk, Nuvei, Airwallex, Whop, PXP, offshore acquirer, custom HTTP.
Point a subdomain (typically checkout.your-brand.com) to our infrastructure. TLS certificate is issued to your brand's domain.
Paste one obfuscated line into theme.liquid. Native Shopify Payments express buttons suppress. Buy button redirects to your subdomain. Done.
Because the captured order writes back to Shopify Admin API on the standard orders/create event, every Shopify app that hooks that event continues firing:
Own-domain checkout via CascadeCheckout. Buy button redirects to your subdomain, transaction captures on your gateway, Shopify Payments is out of the loop. The Shopify order still exists in Shopify Admin so apps and fulfillment continue.
Yes. High-risk categories are the primary use case. Shopify Payments does not underwrite most high-risk MCC codes, so the workaround exists so those merchants can plug in an acquirer that already approved their category.
24 to 48 hours from the moment you send your gateway API keys and DNS pointer for your checkout subdomain. First test transaction goes through inside that window.
No. The captured order writes back to Shopify Admin API on the standard order-created event. Every Shopify app that hooks that event (Klaviyo, ReCharge, ShipStation, subscription tools, ERPs, tracking) continues to fire normally.
Any gateway, any high-risk category, cloaked checkout on your own domain.
Bypass Shopify Payments → · Avoid Shopify Payments ban → · Hide from SP →