One bank says no?
The next one says yes.
When a payment is softly declined, your cascade sends it to your next gateway right away, while the buyer is still on the page.
Why a second gateway says yes
Every bank and acquirer has its own risk rules. A card one of them declines can be approved by another a second later. Without a cascade, that buyer is simply gone.
Your cascade keeps the gateways you already pay for working together, instead of leaving your backups idle.
How a cascade works
- Gateway 1 answers “Do not honor”: a soft decline.
- Your cascade sends the same payment to gateway 2.
- Approved. The order lands in your store.
- Reported as “Saved by cascade” in your dashboard.
Which declines move on
Sent to the next gateway
- Do not honor
- Issuer unavailable
- Technical errors and outages
Never retried
- Stolen or lost card
- Fraud suspected
- More than 10 declines on the card in 24 hours
Who it’s for
Questions merchants ask
Does the buyer have to do anything?
No. They pay once. If the first gateway softly declines, the next one is tried in the same session.
Can I choose the order?
Yes. You line up your gateways, per store or per product, next to your routing rules.
What if a gateway is down?
A gateway that keeps failing is paused automatically, and payments flow to the next one.
Can I see what happened on a payment?
Yes. Every attempt is logged with the gateway, its answer and the result.