Business Platforms

Reducing Subscription Churn From Failed Payments

A declined renewal is not a cancellation. How to sort decline reasons, use card updates and retries from your gateway, write dunning emails people act on, and set a fair grace period.

Reducing Subscription Churn From Failed Payments

A member who cancels has made a decision. A member whose renewal was declined has not, and often learns about it only when the login stops working. Failed payment recovery is the set of small mechanisms between a declined charge and a lost subscriber: card updates, retries, emails and a grace period. Most of it is configuration you already own and have never opened.

You will not find recovery rates quoted here. They vary too much by country, price and payment method for someone else's number to mean anything. What follows is the order to set things up in and how to measure your own result.

Sort your failures by reason first

Export the failed renewals from your gateway for the last few months and group them by decline code. The right response depends on the group, and applying one treatment to all of them is how businesses end up retrying stolen cards and giving up on cards that only needed two more days.

GroupTypical codesWhat helps
Temporaryinsufficient_funds, do_not_honor, try_again_laterRetry later, spaced out
Card replaced or expiredexpired_cardAutomatic card updates, then ask the customer
Permanentlost_card, stolen_card, incorrect_numberDo not retry. A new payment method is needed
Needs the customerauthentication_requiredEmail a link so they can confirm the payment with their bank

The code names above are Stripe's. Other gateways use their own names for the same four situations.

Let the card networks repair cards before they fail

When a bank reissues a card, the card networks can pass the new number and expiry date to the payment processor that holds the old one. Gateways expose this under names such as account updater or, at Stripe, automatic card updates. The saved card is corrected without the customer doing anything and the next renewal goes through.

Three things to know before you rely on it:

  • It only works for cards saved with the gateway. A subscription the customer pays by hand each month has nothing to update.
  • Coverage depends on the issuing bank and the country. Stripe describes it as widely supported for cards issued in the United States and variable elsewhere.
  • On some gateways it is a separate service that has to be switched on. Check your provider's documentation and ask support whether it is active on your account.

The second repair is a reminder before the card expires. Gateways return the expiry month and the last four digits of a saved card for exactly this purpose. Use them to show a banner in the account area and send one email a few weeks ahead. Stripe Billing can send that email for you from its revenue recovery settings.

Set a retry schedule that respects the reason

Retrying a temporary decline an hour later usually returns the same decline. Issuers also treat a burst of attempts on one card as suspicious, and the card networks limit how often a declined card may be retried. Space the attempts out and stop when the code says stop.

Where the schedule lives depends on what bills your members:

  • Stripe Billing. Smart Retries chooses the retry times for you. You set the number of attempts and the window they must fit in. The alternative is a custom schedule with a fixed number of days between attempts. Permanent declines are not retried until a new payment method is attached.
  • WooCommerce Subscriptions. Go to WooCommerce > Settings > Subscriptions and tick "Enable automatic retry of failed recurring payments". The default retry rules make several attempts over about a week and email the customer on some of them. A developer can change the rules in code.
  • Your own billing code. Put retries in a queue, widen the gaps as you go, and cap the total. Send a fresh idempotency key with each attempt, built from the invoice and the attempt number, so that a timeout never becomes a double charge.

Whatever the system, the window has to close before the next renewal date. A monthly plan with a five-week retry window ends up owing two invoices at once, and two charges in one week invite disputes.

Keep access during the retry window, and say when it ends

Cutting access on the first decline punishes a paying customer for their bank's caution. Keep access on while retries are running, show a clear notice in the account area, and remove access only when the window closes.

Check what your stack does by default, because it may not match that intention. In Stripe, a subscription with a failed renewal is past_due while retries run, and you choose what happens after the last one: cancel, mark unpaid, leave past due or pause. Your application decides which of those statuses still open the door. On WooCommerce, a subscription goes on hold while payment is being retried, and WooCommerce Memberships pauses a membership whose subscription is on hold. If you want a grace period there, it has to be built deliberately.

Write dunning emails a busy person can act on

Dunning is the sequence of messages about an unpaid renewal. Four is enough: at the first failure, midway through the window, a final notice before access ends, and one after cancellation with a link to come back. Each of them should follow the same rules.

  • Say what happened in the subject. "Your payment for the Pro plan did not go through" beats "Action required".
  • Give the facts. The amount, the last four digits of the card, the date of the next attempt and the date access will end.
  • One button, no password hunt. Link to a payment update page that works from the email. Stripe can host that page or its customer portal for you. In WooCommerce the customer changes the payment method from the subscription in My Account.
  • Charge straight away. When the card is updated, pay the open invoice immediately and confirm by email. Waiting for the next scheduled retry leaves the member unsure.
  • Sound like a person. Send from an address that accepts replies and skip the debt collector tone. Most of these customers want to pay.

These are transactional emails, so send them through your transactional mail service with SPF, DKIM and DMARC in place. A recovery email in the spam folder recovers nothing.

Make sure your site and the gateway agree

Recovery breaks quietly when the gateway knows something your site does not. The gateway reports payment results through webhooks, and a site move, a firewall rule or a cached endpoint can stop them arriving. With Stripe Billing these are the events to handle:

  • invoice.payment_failed, which carries the attempt count and the time of the next attempt.
  • invoice.paid, to restore access and send the confirmation.
  • customer.subscription.updated and customer.subscription.deleted, for status changes at the end of the window.
  • payment_method.automatically_updated, to refresh the expiry date you store.

Add a nightly job that compares subscription statuses at the gateway with the ones in your database and reports differences. It catches the member who paid but is locked out, and the one who was canceled months ago and still has access. Handling webhooks reliably is ordinary API integration work, and it is where we find most billing bugs on sites we take over.

Measure your own failed payment recovery

Each month, count five things: renewals attempted, renewals that failed on the first try, failures recovered by a retry alone, failures recovered after the customer acted, and subscriptions lost. Split them by the decline groups from the first section.

The split tells you where effort pays. Losses that are mostly temporary declines point at the retry schedule. Losses where the customer never updated the card point at the emails and the update page.

For most sites this is settings, email copy and one afternoon of testing with the gateway's test cards. It turns into development when billing runs through your own code, when you use more than one gateway, or when the grace period and notices have to appear inside a member area or a mobile app. Those are the cases we handle on membership and subscription platforms, on WooCommerce and on custom builds. Two related guides go further: renewal pitfalls in WooCommerce Subscriptions and plans, trials and proration in SaaS billing.

Frequently asked questions

How long should the retry window be?

Long enough to pass a payday and short enough to finish before the next renewal. For monthly plans that usually means one to three weeks. Annual plans can run longer, since there is no next invoice close behind.

Is it safe to retry a declined card several times?

For temporary declines, yes, with days between attempts. For lost, stolen or closed cards, no: the answer will not change. Let the gateway's retry system apply those rules instead of looping in your own code.

Should I offer a discount to members whose payment failed?

Not in the dunning sequence. These customers did not decide to leave, so a discount gives away revenue to solve a problem they do not have. Keep offers for people who cancel on purpose.

Do direct debit payments fail in the same way as cards?

No. A direct debit can be reported as failed days after it was submitted, and the rules for collecting again are set by the scheme and the mandate. Gateways handle them with separate retry settings, so configure and test them separately from cards.

Add WorldWin Coder to your preferred sources

Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

Swati Priyadrshni
· Founder & CEO at WorldWin Coder

I'm Swati Priyadarshani, Founder & CEO of LMS Advisor and Co-Founder of WorldWin Coder Pvt. Ltd. (est. 2019). Over the last 10+ years, I've helped enterprises build learning platforms that actually get used - not just deployed.

Keep reading

Have something to build, fix or move?

Tell us where you are. A developer reads every inquiry, and you get next steps and a free quote within one business day.