Failed Payments & Involuntary Churn

Involuntary churn is when a subscriber's payment fails and they are dropped from the subscription without ever making a conscious decision to cancel. Their card expired. Their bank declined the charge. Their payment details were outdated. A technical processing error occurred.

The subscriber did not choose to leave. In many cases, they do not even know they have been cancelled until they try to use the product and find they no longer have access.

This is fundamentally different from voluntary churn — where the subscriber actively decided the subscription was not worth continuing. Involuntary churn is not a value problem or a product problem. It is a plumbing problem. And it is draining revenue from almost every subscription business, every single month.

For a business with £100,000 MRR, 3–9% means £3,000 to £9,000 in revenue silently disappearing every month. Over a year, that is £36,000 to £108,000. For a business with £1M MRR, the numbers become £360,000 to £1,080,000 annually.

The gap between average and best-in-class compounds every month. A business that recovers 30% of failed payments versus one that recovers 65% has a significantly different churn rate, a significantly different LTV, and over 2–3 years, a dramatically different revenue trajectory — all from the same subscriber base paying the same price.

Payment failures are not random. They have specific, identifiable causes:

Expired cards are the most common cause. Credit and debit cards have expiry dates. When the card on file expires, the next billing attempt fails. This is predictable — you know when cards will expire — and largely preventable.

Insufficient funds account for a significant portion of failures, particularly in B2C subscriptions. The subscriber's account did not have enough balance to cover the charge at the moment the billing system attempted it.

Bank declines can occur for fraud prevention reasons, spending limits, or bank-side technical issues. These are often temporary — the same charge may succeed if retried at a different time.

Outdated billing information — the subscriber got a new card (replacement after loss or fraud) and did not update their details with your service.

Technical processing errors — gateway timeouts, network issues, processor-side failures. These are typically transient.

Understanding the cause matters because different causes require different solutions. An expired card needs a card updater. Insufficient funds needs a smart retry. A bank decline needs a retry at a different time. Outdated information needs a subscriber notification.

Card updater services (also called account updaters) automatically refresh expired or replaced card details with the subscriber's new card information. They work through partnerships between payment processors and card networks (Visa, Mastercard) that share updated card details when a card is reissued.

How it works: When a subscriber's card is replaced — new expiry date, new card number after loss/fraud — the card network notifies the merchant's payment processor with the updated details. The billing system updates automatically. The next billing attempt uses the new card. The subscriber never notices.

Impact: Card updaters alone can recover 15–25% of what would otherwise be involuntary churn from expired cards. They require no action from the subscriber and run entirely in the background.

Implementation: Most modern billing platforms (Stripe, Braintree, Recurly, Chargebee) support automatic card updating. If you are not using this feature, turn it on. It is the single easiest payment recovery measure to implement.

When a payment fails, the billing system can retry the charge. The question is when and how often.

Naive retry: Retry immediately, then again in 24 hours, then again in 48 hours. This is better than nothing but ignores the cause of the failure.

Intelligent retry: Vary the retry timing based on the failure reason and the likelihood of success. Insufficient funds? Retry at the start of the next month (when payday deposits are more likely). Bank decline? Retry in 4–6 hours (transient issues often resolve quickly). Expired card? Don't retry the same card — trigger a card update request or subscriber notification instead. For the complete framework, see the payment optimisation chapter in Subscribe & Conquer.

Retry schedule best practices:

Do not over-retry. Excessive retry attempts can trigger fraud alerts at the subscriber's bank, resulting in a hard block that prevents any future charges.

Dunning is the process of notifying the subscriber that their payment has failed and asking them to update their payment information. A well-designed dunning sequence is direct, helpful, and non-alarming.

SMS dunning: For mobile-first audiences, SMS dunning (with permission) can be significantly more effective than email — higher open rates, faster response times. Use sparingly: one SMS at the Day 3 or Day 7 stage alongside the email.

Recovery rates: A well-designed dunning sequence recovers 10–20% of failed payments on top of what card updaters and retries already capture.

If you know a subscriber's card will expire next month (and you do — the expiry date is on file), you can notify them before the payment fails.

Send a notification 2–4 weeks before the card expiry date: "Your card ending in 4829 expires next month. Update your payment details to avoid any interruption to your subscription."

This is proactive, helpful, and prevents the failure from ever occurring. It also positions the business as competent and caring — rather than sending frantic "your payment failed" emails after the fact.

Combined, a well-optimised payment recovery stack can recover 50–70% of otherwise-lost revenue from payment failures. The difference between a business operating without these systems and one with a fully optimised stack is enormous — and it compounds every single month. Pair this with strong voluntary retention strategies and you address both sides of the churn equation. Track the impact using the metrics that matter.

Subscribe & Conquer: Payment Optimisation & Margin Control

Chapter 6 covers the complete payment optimisation and margin control framework — card updaters, retry schedules, dunning sequences, annual billing incentives, and cost management.