Retry cascade
DEFINITION
A retry cascade is an ordered sequence of automatic attempts to collect a failed subscription payment, varying timing, gateway, or method.
TABLE OF CONTENTS
RELATED TERMS
A retry cascade is an ordered sequence of automatic attempts to collect a failed subscription payment. Instead of giving up when a charge is declined, the billing system retries the payment on a schedule, sometimes varying the timing, the gateway, or the payment method, until the charge succeeds or the sequence ends.
Most failed recurring payments are not deliberate cancellations. They fail because a card expired, a balance was temporarily insufficient, or an issuer declined a charge it did not recognize. A retry cascade is designed to recover this involuntary churn by trying again in a smarter way than a single fixed repeat. The order and timing of attempts matter, since retrying at a better moment or through a different path can turn a decline into an approval. A subscription platform such as Recurly can run a retry cascade against failed invoices, adjusting attempts based on the decline reason and using signals from networks and machine learning to schedule retries and ensure compliance.
Why a retry cascade matters for subscription businesses
Involuntary churn drains recurring revenue, because a customer who still wants the service stops paying only because a charge failed. A retry cascade recovers a share of those payments without the customer doing anything, which protects revenue and retention at the same time. Done well, it also protects the customer relationship, since the person is never asked to re-enter details for a payment the system can recover on its own.
The design of the cascade is what separates a good result from a wasted one. Retrying too aggressively can trigger more hard declines or extra fees, while retrying too rarely leaves recoverable revenue on the table. Adapting the sequence to the reason a payment failed is what makes the difference, and listening to the unique network signals from each gateway, processor ,and card brand are intrinsic to a successful solution.
How a retry cascade works
A scheduled charge fails and the billing system records the decline reason and network signals.
The system decides whether the failure is allowed to be retried, based on those reasons.
It schedules the next attempt at a time chosen to improve the odds of success or after a delay mandated by the network(s).
Each attempt can vary a factor such as the timing, the gateway, or a backup payment method.
The cascade continues through its defined attempts until the payment succeeds, the network-defined limits are reached, or the sequence is exhausted.
If every attempt fails, the subscription follows the business's dunning and cancellation rules.
How to use a retry cascade
Retry based on the decline reason, since an insufficient signal is worth more attempts than a hard decline.
Space attempts to improve the odds, for example around a likely payday or account top-up.
Pair retries with an account updater so an expired card is refreshed before the next attempt.
Coordinate the cascade with customer messaging so dunning emails and retries reinforce each other.
Set a clear end point where the subscription moves to a final dunning state or cancellation.
Benefits and examples
Recovered revenue: payments that would have been lost are collected automatically.
Lower involuntary churn: customers who still want the service are not lost to a failed charge.
No customer effort: recovery happens in the background for most cases.
Better use of the payment stack: varying timing or path across attempts raises the chance of approval.
For example, a subscription business charges a customer on the first of the month and the payment is declined for insufficient funds. Rather than cancelling, the system waits and retries a few days later, when the customer is more likely to have funds available. The second attempt clears, the subscription stays active, and the customer never has to act. If the reason had been a hard decline such as a closed account, the system would stop retrying sooner and move the account into dunning.
Frequently asked questions
What is a retry cascade? It is an ordered sequence of automatic attempts to collect a failed subscription payment, retrying on a schedule until the charge succeeds or the sequence ends.
How is a retry cascade different from a single retry? A single retry repeats the charge once on a fixed schedule. A cascade runs multiple attempts and can vary the timing, gateway, or payment method between them to improve the odds of success.
Does retrying a payment annoy the customer? Usually not, because recovery happens in the background and the customer is not asked to act for most failures. Businesses often pair retries with clear dunning messages only when action is genuinely needed.
When should a retry cascade stop? When the payment succeeds, or when the attempts are exhausted or the decline reason shows the payment cannot be recovered, at which point the account moves to a final dunning state or cancellation.
