Payment cascading is a payment failover process that automatically retries a failed transaction through another eligible provider, acquirer, account, or route.
Instead of ending the payment after the first failed attempt, the system moves the transaction to the next available route based on predefined logic. The goal is to recover payments that might fail because of provider downtime, technical errors, limits, routing restrictions, or temporary processing issues.
In simple terms, payment cascading gives a transaction another chance to be completed without asking the customer to start again.
Payment cascading works through a sequence of payment routes. When a transaction is initiated, the system first selects a route according to the configured payment logic. If that route cannot complete the payment, the system checks the next eligible route and retries the transaction.
The next route may be chosen based on factors such as:
The process continues until the payment is successful, no eligible routes remain, or the retry limit is reached.
Payment routing decides where a transaction should go first. It sends a payment to the most suitable provider, acquirer, account, or payment method based on defined rules. Payment cascading decides what happens if that first route fails. It automatically tries another eligible route to recover the transaction.
In simple terms, routing chooses the path, and cascading provides the backup one.
Not every failed payment is caused by the customer. A payment may fail because a provider is temporarily unavailable, an account reaches a limit, a route does not support the transaction currency, or a technical error occurs. Without cascading, these failures can turn into lost revenue even when another provider could have processed the same transaction.
Payment cascading can help businesses:
Using Corefy's Routing & Cascading engine, teams can configure failover logic, define provider priority, use routing conditions such as BIN, country, currency, amount, or custom attributes, monitor provider health, and retry failed payments through eligible routes without customer re-entry or extra checkout friction. The same infrastructure also supports use cases such as recurring token cascading, turnover caps, and routing strategies based on priority, balance, weight, or predicted conversion.
