In payment processing, cascading is a routing technique in which a card transaction that fails with one acquirer is sent automatically to another, and if necessary a third, in a set order. The customer sees a single attempt. The aim is to recover sales that would otherwise be lost to a technical fault or to a decline that a different route might avoid.
Cascading is configured in a gateway or payment orchestration platform connected to several acquirers. It differs from payment failover, which reacts to an acquirer being unavailable, in that it also retries certain refusals. Only a soft decline is worth cascading; a refusal for a stolen or closed card will fail everywhere. Card networks restrict repeated attempts on a declined card and charge for excess retries, so rules must read the response code. Used carefully, cascading raises the authorization rate, most often for cross-border and higher-risk merchants.