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.

3 min read

  1. Day 0Renewal failsRecord the decline reason
  2. Day 2Retry + email 1Helpful: “this happens”
  3. Day 6Retry + email 2Firmer, still helpful
  4. Day 13Final attemptSay plainly what happens next
  5. AfterPause, don’t deleteRecovery stays one click away
A recovery sequence for a failed renewal: four attempts over about two weeks, each paired with a message.

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 reasonWhat it meansRight response
Insufficient fundsTemporary, usuallyRetry on a schedule — high recovery
Card expiredNeeds new detailsEmail with update link; retry is pointless
Card reported lost/stolenNeeds new detailsEmail; do not retry
Do not honourAmbiguous, issuer-sideOne or two retries, then email
Invalid payment methodStructurally brokenEmail only
Authentication requiredThe issuer wants the customer to confirmSend a one-click authentication link

Retrying an expired card four times does nothing except consume attempts and, on some networks, attract penalties for excessive retries.

The last row is most common in Europe, where Strong Customer Authentication lets an issuer ask the customer to confirm a charge. No retry fixes it — the customer has to act. SCA and subscriptions.

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.

Retry schedule design.

Dunning that converts

The email matters as much as the retry.

  • Be specific. “Your payment of $30.00 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.

Writing dunning emails.

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:

  1. Pause the subscription and keep the contract alive, with a resume-when-fixed link. Best for most consumer subscriptions.
  2. Cancel with a one-click resubscribe. Cleaner reporting, slightly worse recovery.
  3. 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.
  • Encourage tokenised wallets — Apple Pay and Google Pay credentials are typically updated by the network when a card is reissued.
  • Tell customers before a price change so the new amount is not a surprise at renewal.

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.

Questions people ask

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.