Payments glossary · Operations
Cascading (Payment Retries)
Cascading is automatically retrying a failed payment through a different acquirer, PSP or payment method, usually within the same checkout, so a customer whose payment was declined or hit a technical error can still complete the purchase.
How Cascading works
A merchant connected to more than one acquirer, directly or through an orchestration platform, sets rules for when to try again elsewhere. Typical triggers are technical failures, such as timeouts or provider outages, and soft declines that another acquirer might get approved, for example because it can process the card domestically. Hard declines, such as a stolen or closed card, should not be cascaded, because no acquirer can get them approved and the attempts count against the merchant.
Cascading can recover sales and reduce dependence on a single provider, but it has limits. Card scheme retry rules still apply: Visa forbids reattempting declines in its issuer-will-never-approve category, caps other reattempts, and bars manipulating data in a reattempt, listing elements such as the acquiring identifier, merchant country and merchant category code, so cascading declined (rather than technically failed) payments should be checked with your acquirers. 3-D Secure authentication is generally tied to the acquirer and merchant details used, so moving a payment to another acquirer may require the customer to authenticate again. Each extra attempt may also incur fees.
Cascading can also mean falling back to another payment method, for example offering a bank payment or wallet when a card fails. Merchants should compare recovered volume with the extra costs, check that each acquirer contract allows multi-acquirer routing, and make sure a customer is never charged twice when a first attempt timed out but was actually approved.