From $199/mo
Talk to founder →
A high-risk merchant account (MID) is a contract with an acquirer that agrees to underwrite your specific product category, chargeback profile and volume. CascadeCheckout is not that. Cascade cannot underwrite a MID, cannot decide whether your MCC is acceptable to a bank, cannot set your reserve. What Cascade does is sit above two or more MIDs and route each transaction attempt to whichever one is healthiest. You need a MID first. Cascade is what makes a second MID actually useful.
A high-risk merchant account is an acquirer's underwriting decision. The acquirer (or their reseller) agrees to process cards for a merchant in a category they consider elevated-risk — kratom, CBD, peptide, vape, IPTV, adult, delta-8, high-chargeback subscription — often with a reserve, a rolling hold, and pricing that reflects the risk.
CascadeCheckout is software middleware. It has no bank relationship, no underwriting authority, no ability to accept or decline a merchant's category. It runs on top of whatever MIDs the merchant already has. Its job is per-attempt routing: pick the healthiest MID for this transaction, and rotate to the next MID if this one declines, times out or throttles.
Single-MID risk you accept. Volume small enough that a termination is survivable while a new MID onboards. Simplest possible checkout stack. No need for own-domain URL. No need for pixel + CAPI relay.
You have or plan a second MID. Your primary MID has real risk of throttling or termination. You cannot afford the days-to-weeks recovery window between MID one going down and MID two going live. You want an own-domain URL by default. You want per-attempt routing instead of a manual "swap the gateway" scramble when the primary tightens.
The honest angle. You still need a processor. In fact, on the high-risk side, you probably want two or three MIDs — because any one of them can throttle or terminate on scale. What Cascade adds is the routing layer that makes multiple MIDs feel like one checkout, and keeps checkout on the merchant's domain when a route dies.
Yes, at least one. Cascade routes across MIDs you already have or will get. We do not underwrite the MID ourselves. If you do not have a MID yet, we can point you to acquirers active in your vertical, but the underwriting relationship is between you and the acquirer.
Yes. A high-risk MID plus a standalone gateway is a working checkout. What is missing is what happens when that single MID throttles, hits velocity caps, or gets restricted mid-scale. Cascade adds the second MID and the auto-rotation.
Cascade is the software layer above the MIDs; the acquirer fees stay with each acquirer. Adding a second MID has its own cost (setup, minimums, reserve). The question is whether losing revenue when the primary MID throttles is worth more than the second MID plus Cascade.
Second MID wired as fallback. Checkout stays on your domain.
High-risk processor → · Payment gateway cascade → · How it works →