Каскадирование
Payment Cascading
Payment cascading is the sequential routing of a payment through several payment providers or acquirers: if one declines the transaction, the system automatically tries the next one.
What is Каскадирование (Payment Cascading)?
Payment cascading (also called a waterfall) is a routing rule under which a transaction passes through a chain of channels in a set order. The first channel receives the request. If it returns a decline, the request goes to the second channel, then the third, and so on, until the payment succeeds or the chain runs out.
## How it works
A cascade is usually built from several acquirers or PSPs connected to different partner banks. A decline from one channel does not necessarily mean the card or wallet is blocked. The cause may be a limit set by the specific issuing bank, a risk rule at the acquirer, or a temporary failure. For this reason, retrying through another channel sometimes produces a successful payment.
## Where it is used
In fintech and payments, cascading is used to increase the share of approved payments and reduce revenue lost to declines. In gambling and betting, it most often applies to deposits: a player should not lose a stake because of a technical decline on a single gateway. This logic is typically implemented through a payment orchestration platform or an in-house router.
## What it affects
Cascading directly affects the approval rate and deposit conversion. It also increases the number of charge attempts, which is visible to banks and card schemes. For this reason, cascading has limits: requests should not be retried after hard declines (stolen card, account block, suspected fraud), and moving a payment to a different descriptor or a different MCC without the provider's approval may be treated as a violation of the rules.
## Common mistakes
Typical mistakes include: cascading without analysing decline codes, so a fraudulent transaction is attempted five times in a row; having no limit on the number of attempts; sending different amounts or payer data through different links in the chain, which breaks anti-fraud checks; and failing to account for chargeback risk on each channel. Every additional channel increases both availability and the combined chargeback risk.
## How to configure it correctly
FAQ
How does payment cascading differ from smart routing?
Cascading works through channels in a fixed queue until a payment succeeds. Smart routing selects a channel in advance based on weights, cost, and historical performance. In practice, the two are often combined in one system.
Can a declined payment be retried indefinitely?
No. Retries are limited by the number of attempts and by time, and hard declines are not retried at all. Frequent retries can lead to blocking by the provider or the card scheme.
Do players need to be told about cascading?
Usually it is enough to provide clear information about the payment status and an accurate description of the transaction. Specific requirements depend on provider contracts and jurisdictional rules.