Decline Salvage / Cascading

Decline salvage, also widely called cascading, is the practice of automatically reattempting a declined payment transaction on a different gateway or processor, with the goal of recovering a sale that would otherwise be lost. When a primary gateway declines a transaction, decline salvage logic routes that same transaction to one or more secondary gateways in sequence until either an authorization succeeds or all configured options are exhausted.

The commercial rationale is straightforward: not all declines are final. A significant portion of payment declines are soft declines, the result of temporary conditions, risk scoring differences between processors, or acquiring-side issues rather than a definitive "do not honor" from the issuing bank. A transaction declined by Gateway A may succeed on Gateway B because B has a different acquiring relationship with the issuing bank, different fraud scoring thresholds, or a different geographic routing path that the issuer responds to more favorably.

Decline salvage is particularly effective for subscription and recurring billing businesses, where involuntary churn from payment failures is a direct revenue and retention problem. A subscriber whose card fails a payment may not return when manually prompted to update their details. Automatically recovering that transaction on a secondary gateway eliminates the failure entirely, with no customer friction.

The key discipline in decline salvage is knowing which declines to attempt recovery on. Hard Declines, definitive issuer rejections such as lost/stolen card, account closed, or do not honor, should not be cascaded. Attempting a hard decline on multiple gateways risks triggering fraud signals and makes no commercial sense. Soft Declines and processor-level errors are the appropriate targets for cascading logic.