What is cascading in payments?

Cascading sends a transaction that was softly declined by one acquirer to a second acquirer, usually once and within seconds. The customer does not see it: from their side, the payment simply goes through.

When it works

Cascading succeeds when the second route is genuinely different. That can mean a better connection with the issuer, local acquiring in the cardholder's country, or a different risk setup that accepts what the first acquirer refused.

When it does not

Cascading a hard decline, such as a stolen card or a closed account, is pointless and breaks scheme rules. Cascading too often, or across too many routes, can also look suspicious to issuers and counts toward scheme retry limits.

What it requires

• At least two acquirer connections for the same payment method and market.
• Decline codes mapped to decide which ones deserve a cascade.
• Shared credentials or tokens usable on both routes.
• Limits on the number of attempts.

What it means for payment operators

Cascading is a form of fallback. On the platform, the return code mapping decides whether a retry goes to the same provider or another, per decline code, and the NORBr Vault token is reusable across the providers configured on a merchant account. Your merchants set the logic in the Console without custom code per provider.