Failed Subscription Payments: Recovering the Revenue
Failed renewals are the cheapest revenue in a subscription business to recover. Retry schedules that work, dunning that converts, and the decline codes to treat.
A subscriber whose renewal failed still wants your product. That makes recovered failed payments the cheapest revenue in the business — no acquisition cost, no persuasion, just a payment that needs to go through.
Most stores leave a meaningful share of it on the table by treating every failure identically.
Read the decline code
Not all failures mean the same thing, and the correct response differs sharply:
| Decline reason | What it means | Right response |
|---|---|---|
| Insufficient funds | Temporary, usually | Retry on a schedule — high recovery |
| Card expired | Needs new details | Email with update link; retry is pointless |
| Card reported lost/stolen | Needs new details | Email; do not retry |
| Do not honour | Ambiguous, issuer-side | One or two retries, then email |
| Invalid payment method | Structurally broken | Email only |
| Mandate revoked | Customer cancelled outside your flow | Treat as churn signal, request re-authorisation |
| Mandate amount exceeded | Your price is above the registered ceiling | Re-register the mandate |
Retrying an expired card four times does nothing except consume attempts and, on some networks, attract penalties for excessive retries.
The last two rows are India-specific and are frequently the largest category there. Detail.
Time the retries
Fixed offsets — day 1, 3, 7, 14 — are fine as a default. Two refinements help measurably:
Align with pay cycles. Insufficient-funds failures recover far better just after common salary dates. A retry on the 1st of the month beats one on the 28th.
Avoid clustering. Retrying thousands of contracts at midnight produces a load spike and, if your gateway rate-limits, spurious failures that look like declines.
Dunning that converts
The email matters as much as the retry.
- Be specific. “Your payment of ₹1,499 on 17 October didn’t go through” beats “there was a problem with your account”.
- One action. A single button to update the payment method. Not a login, not a portal tour.
- Say what happens next. “We’ll try again on 20 October. Your delivery is on hold until then.”
- Do not threaten early. The first email should be helpful. Cancellation warnings belong in the last one.
Decide the endgame in advance
After the retry sequence ends you need a defined outcome, and it should not be “the subscription sits in limbo”.
Options, roughly in order of preference:
- Pause the subscription and keep the contract alive, with a resume-when-fixed link. Best for most consumer subscriptions.
- Cancel with a one-click resubscribe. Cleaner reporting, slightly worse recovery.
- Leave it active and keep retrying. Almost always wrong — it damages your decline ratio and annoys the customer.
Whichever you pick, the subscriber must be told. The worst outcome is a customer who thinks they are subscribed and is not.
Prevent rather than recover
- Card expiry updaters — networks offer services that supply refreshed card details automatically. How they work.
- Prompt before expiry. You know the expiry date. Email a month ahead.
- Offer UPI Autopay where available — mandates tied to bank accounts do not expire like cards.
- Register mandates with headroom so a price change does not break them.
Measure it
Track recovery rate — failed payments that eventually succeed — and segment by decline reason. A low recovery rate on insufficient funds means your retry timing is wrong. A low rate on expired cards means your dunning email is not converting.
One blended “failed payments” number cannot tell you which.
Frequently asked questions
How many times should I retry a failed subscription payment?
Three to four attempts over about two weeks recovers most of what is recoverable. Beyond that, additional retries mostly annoy the customer and can attract penalties from card networks for excessive retry activity.