Failed subscription payments: reducing involuntary churn with retries, card updaters and better recovery flows

Voluntary and involuntary churn

Subscription businesses usually focus on voluntary churn, when customers decide to cancel. Involuntary churn happens when a renewal payment fails and the subscription lapses without the customer intending to leave. For many businesses with card-based billing, failed payments are among the most fixable causes of lost revenue.

Unlike voluntary churn, involuntary churn does not require changing the product or price. It requires payment operations: capturing the right data, retrying intelligently, keeping card details current and giving customers an easy way to fix problems.

Why recurring payments fail

Payment failures fall broadly into soft declines and hard declines. Soft declines are temporary, such as insufficient funds, issuer systems being unavailable or a generic do-not-honour response, and a retry later may succeed. Hard declines indicate that retrying the same details will not work, such as a closed account, a card reported lost or stolen, or an invalid card number.

Expired cards are a major cause. Cards are reissued with new expiry dates and sometimes new numbers, and customers rarely update every subscription. Authentication requirements also play a role in Europe, where a recurring payment set up without the correct initial authentication and indicators may be declined or require the customer to authenticate again.

Keeping card details current automatically

Card networks offer account updater services, such as Visa Account Updater and Mastercard Automatic Billing Updater, that let merchants, usually through their payment provider, receive updated card numbers and expiry dates when issuers reissue cards. Participation depends on the issuer and the payment provider.

Network tokenisation goes further. Instead of storing the card number, the merchant’s provider stores a token issued by the card network, which is updated automatically when the underlying card changes. Network tokens can also improve approval rates because issuers recognise them as more secure.

Checking whether the payment provider has these features enabled is often the single most valuable step, because they prevent failures before any retry or email is needed.

Retrying intelligently

Retrying a declined payment immediately and repeatedly rarely helps and can look suspicious to issuers. Retries should respond to the decline reason: soft declines can be retried after a delay, while hard declines should trigger a request for new payment details instead.

Timing matters. Many payment platforms offer automated retry schedules that use data about when retries are more likely to succeed. Card scheme rules also limit retries for certain decline types, and excessive retries can lead to fees or reduced approval rates, so retry logic should follow the provider’s guidance.

Pre-expiry reminders

Ask customers to update cards before they expire, if updater services do not cover the card.

Decline-aware retries

Retry soft declines on a schedule; stop and ask for new details after hard declines.

Grace period

Keep access for a short period while recovery attempts continue, rather than cutting off immediately.

Recovery emails

Clear messages explaining what happened, with a secure link to update payment details.

Alternative methods

Offer direct debit, wallets or other methods where cards fail repeatedly.

Designing the recovery flow customers use

Recovery emails and in-app messages work when they are clear, calm and easy to act on. The subject should say that a payment failed, the message should name the subscription and amount, and a single button should lead to a secure page where the customer can update details without hunting for a password.

Send reminders in a sequence over the grace period rather than one email, and use more than one channel where the customer has agreed, such as in-app notices for users who are active in the product. Avoid threatening language; most customers in this situation did nothing wrong.

When a customer updates details, retry the outstanding payment immediately and confirm success. If a subscription finally lapses, make reactivation easy, keeping the customer’s data and settings for a reasonable period in line with retention policies.

Measuring recovery

Track the failed payment rate, the recovery rate by decline type and by recovery step, the revenue recovered and the share of subscriptions lost to payment failure. Separate these from voluntary cancellations in churn reporting, so product and marketing decisions are not based on mixed numbers.

Review results by payment method, card type, country and issuer where the data allows. Patterns often reveal specific issues, such as a market where authentication for renewals is failing or a payment method with low approval rates.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• E-commerce Growth System — Store, brand, advertising, lifecycle communication and order automation as one system — with local payment methods and the margin arithmetic checked before launch.
• Quote to cash without re-keying: where the handoffs break
• Product data is the e-commerce growth lever nobody budgets for
• Switzerland’s revised Data Protection Act: what it means for websites, analytics and marketing
• Invoicing in Switzerland: QR-bill, eBill and electronic invoices to the federal administration
• All insight articles