Home / Wiki / R / Retry Cascade

Retry Cascade

PaymentsUpdated 16 Nov 2026

A retry cascade is a predefined sequence of automatic attempts to collect a recurring payment that has failed, in which each step changes something about the attempt: its timing, the payment gateway or acquirer used, or the payment method charged. It combines the timing rules of retry logic with the routing idea of payment cascading, in which a declined transaction is passed to another processor.

A cascade might retry the same card a few days later, send the next attempt through a second acquirer, then charge a backup card or bank account on file, with reminders to the customer between steps. Cascades are meant only for soft declines, such as insufficient funds or a temporary issuer fault. A hard decline, such as a closed account or a card reported stolen, should not be retried. Card schemes restrict repeated resubmission of declined transactions, and many billing systems now set the steps with data-driven smart retry models.

Last updated 16 Nov 2026