Lorixen.
EN

Failed Subscription Payments: A Recovery Timeline for UK Firms

Short answer: Treat a failed subscription payment as a short, scheduled process rather than a single event. Prevent what you can a month ahead, retry automatically for one to four weeks, email the customer after each failure with a one-tap link to update their card, and decide in advance what happens when the window closes: cancel, pause, or keep the account open as unpaid. Most of this is a settings job in your billing platform, not a development project.

Customers whose payments fail rarely meant to leave. A replaced card, a bank asking for extra authentication, a balance that was short on the wrong day: these quietly end subscriptions that would otherwise have carried on. The usual name for the recovery process is "dunning", and the timeline below shows how the pieces fit together. Stripe and GoCardless serve as examples here; other billing tools have similar settings under different names.

Before anything fails: 30 days out

The cheapest failed payment is the one that never happens.

Expiring card emails. Stripe can send customers an email one month before the card stored as their default payment method expires (as of November 2026). The email links to a page where they can add a new card.

Automatic card updates. Card networks can pass new card details to the payment provider when a bank reissues a card. Stripe's card documentation says it works with the networks to update saved cards automatically when a customer receives a replacement, but it also says issuer participation is required, support is broad in the United States and international support varies by country. So for UK customers, treat the updater as a helpful bonus, not a reason to skip the expiry email.

Renewal reminders. For annual plans especially, a heads-up a few days before renewal avoids the "I forgot about this" decline that turns into a refund request.

Day 0: the first failure

The renewal charge is declined. Three things should happen within minutes.

  1. The customer gets an email. Stripe's "Send emails when card payments fail" setting sends a message after each failed payment, telling the customer what happened and linking to a page where they can update their payment method. Write the subject plainly ("Your payment didn't go through") and skip the guilt.
  2. Your system records the failure. If your website or app controls access, listen for the invoice.payment_failed webhook. Its attempt_count tells you how many attempts have been made, and the invoice shows the next scheduled attempt.
  3. Nothing changes for the customer yet. Cutting off access on the first decline punishes people for their bank's timing. Keep them in.

Not every failure can be retried

Stripe distinguishes "hard" declines, such as a lost or stolen card, an incorrect number or authentication_required, from temporary ones. For hard declines, retries stay on the schedule but only run once a new payment method is added. That is why the email link matters more than the retry count.

When the bank wants authentication

Some UK and European renewals need the cardholder to confirm the payment with their bank, for example through 3D Secure. Stripe can email a hosted link for the customer to complete that step, plus reminders until it is done or expires. Turn this on; without it, these payments simply sit there.

Days 1–14: automatic retries

Smart retry systems pick retry times based on signals rather than a fixed rule. Stripe's Smart Retries let you choose a number of retries within a window of one week up to two months, and new accounts default to up to eight retries within two weeks. You can instead set a custom schedule of up to three retries, each a set number of days after the last.

Which to choose depends on your product. Monthly boxes or memberships usually suit a two-week window; a longer window makes sense for annual plans worth chasing.

What your website or app should show

  • A banner, not a lockout. "We couldn't take your last payment. Update your card" on the account page, with a direct link.
  • A self-serve update page. Stripe's emails can point to its hosted Customer Portal or to your own subscription management page. Either way, the customer should not need to email you or remember a password to fix a card.
  • One place to check status. If customers can see "payment overdue, next attempt 12 November", they are less likely to cancel in confusion.

Direct Debit is a different rhythm

If you collect by Bacs Direct Debit, failures arrive more slowly and for different reasons. GoCardless names insufficient funds and cancelled mandates as the two main causes. A failed payment can be retried from the dashboard with a new charge date, up to three times, and for repeat shortfalls it suggests agreeing a collection date that suits the customer, such as just after payday. A cancelled mandate cannot be retried at all: you need to contact the customer and set up a new one. Stripe also offers optional retries for Bacs Direct Debit on insufficient funds, up to two retries within 30 days, though they are off by default.

Final notice: two or three days before the window closes

Send one last, distinct email from a real person's name. Say exactly what happens and when: "If we can't take payment by Friday, your subscription will be paused and your saved preferences kept." Specifics recover more payments than vague warnings. Your billing tool's automatic emails cover the routine messages; this one is usually worth writing yourself.

When retries run out

Decide this in advance, in your billing settings, not on the day. Stripe offers four outcomes once the retry schedule ends:

  • Cancel the subscription.
  • Mark it unpaid, so invoices keep generating as drafts.
  • Leave it past due, so invoices keep being created and charged under your retry settings.
  • Pause it, for eligible subscriptions, so no new invoices are created until it resumes.

For many small subscription businesses, pausing is the kindest default: the customer's account, history and preferences survive, and coming back is one click. Cancel only where keeping an account open has a real cost to you.

Measuring whether it works

Look at four numbers each month: how many payments failed on the first attempt, the failure rate, how much was recovered, and the recovery rate. Stripe's recovery analytics also splits recovered volume by method (retries, emails, other), which shows whether your emails are doing their job. A rising first-attempt failure rate is a cue to strengthen the prevention stage, not to add more retries.

FAQ

How many times should I retry a failed card payment?

There is no single right number. Smart retry tools choose the timing for you within a window you set; a two-week window suits most monthly plans, and longer can make sense for annual ones.

Should I block access as soon as a payment fails?

Usually not. Keep access during the retry window, show a clear banner with an update link, and only restrict access once your final notice date has passed.

Can I retry a failed Direct Debit?

Yes, if the failure was a shortfall rather than a cancelled mandate. Check your provider's retry limits and notification rules, and consider moving the collection date.

Mapping your own failed-payment emails, retry settings and account screens onto this timeline is a good one-afternoon review, and we're glad to help join the billing side to your site or app via our enquiry page.

Sources

WhatsAppLet’s talk