Waterfall routing is a sequential routing strategy in which a payment transaction is attempted on a series of gateways or processors in a predefined order, the "waterfall", until either an authorization succeeds or the sequence is exhausted. If the first gateway declines or fails, the transaction flows to the second; if the second fails, it flows to the third, and so on down the waterfall.
Waterfall routing is closely related to Decline Salvage / Cascading and is sometimes used synonymously. The conceptual distinction is one of design intent: a waterfall is a fully predefined sequence through which transactions flow regardless of performance data, while Dynamic Routing selects the optimal provider for each transaction in real time based on current performance. In practice, most sophisticated routing implementations combine elements of both, a dynamic primary selection followed by a waterfall of fallback options if the primary fails.
Waterfall routing is most commonly used in high-stakes payment contexts where authorization is critical and no transaction should be abandoned without exhausting available options: high-value B2B payments, large subscription renewals, or any scenario where the cost of a failed transaction significantly outweighs the cost of attempting multiple providers. Travel merchants, where a booking failure is immediately costly, are a common use case.
The primary risk of waterfall routing is over-retry. A waterfall that cascades Hard Declines through multiple providers generates unnecessary authorization attempts that may trigger fraud signals, waste processing fees, and produce no incremental authorization. Waterfall logic should be configured to bypass the cascade for hard decline codes and limit the sequence to genuine soft declines and processor-level failures.
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
