Involuntary churn: what it is and what to do about it

How a subscription dies without anyone cancelling

The sequence is unglamorous, which is part of why it goes unnoticed. On Stripe it looks like this.

1. 1.A renewal invoice is created and payment is attempted against the stored card.
2. 2.The card is refused. The invoice stays open and the subscription moves to past due.
3. 3.Retries run on whatever schedule you configured. Stripe's recommended default for Smart Retries is eight attempts over two weeks.
4. 4.If no attempt succeeds, the subscription reaches the end of the dunning period and takes whichever end state you chose: cancelled, unpaid, left past due, or paused.
5. 5.Nobody told you, nobody told the customer unless you enabled the emails, and the MRR is simply lower next month.

That last step is where the damage compounds. A customer who churned voluntarily made a decision you can learn from. A customer who churned because their card expired often does not know it happened, and would have stayed.

Worth knowing: Stripe will not retry nine specific decline codes at all, including lost_card, stolen_card, incorrect_number and authentication_required. The attempt counter keeps rising but no charge is made until a new payment method appears. If your failures are concentrated there, your retry schedule is doing nothing.

How big is it? Two sources that disagree

Most articles quote one figure and present it as settled. It is not. Here are the two most commonly cited, with their dates and their basis.

A gap that wide is not a rounding error, and the honest answer is that both can be right about different populations. Consumer subscriptions with low price points and high card turnover sit at the top of the range. B2B SaaS billed to a company card, with longer relationships and fewer declines, sits lower. A survey of executives also measures what people believe about their own business, which is not the same as transaction data.

Our position: use the range to decide whether to spend twenty minutes measuring, not to decide anything else. If a third of your churn might be involuntary, that is reason enough to look. What you then act on should be your own number.

The three kinds of failure, and why the distinction matters

Every declined payment falls into one of three buckets, and each has a different fix. Treating them as one pile is the most common reason recovery effort gets wasted.

• The card needs updating — expired, wrong number, wrong CVC, replaced by the issuer. Retrying cannot work, because nothing about the card will change. The fix is getting a new card, which means emails and an update page.
• Insufficient funds — the card is valid, the money was not there at that moment, or a limit was hit. The fix is retrying at a better time, which is exactly what Stripe's Smart Retries is built for.
• Hard declines — reported lost or stolen, flagged as fraud, issuer refusal. There is no fix. Retrying is wasted and, for several of these, Stripe advises showing the customer a generic message rather than the real reason.

A fourth bucket matters too: failures whose code you cannot classify. We count none of those as recoverable rather than assuming the best, because an unexplained decline is not evidence of an opportunity.

What to do, in order

1. 1.Turn on Stripe's automatic customer emails if they are off. A failed payment nobody mentioned to the customer is the cheapest recovery available, and plenty of accounts have never enabled them.
2. 2.Check your Smart Retries settings. Stripe's recommended default is eight attempts over two weeks; a custom schedule caps at three retries, which is usually worse.
3. 3.Decide what should happen at the end of dunning. Cancelling immediately loses customers you could still reach; leaving subscriptions past due forever inflates your active count with people who are not paying.
4. 4.Measure what still leaks, split by decline family. This is the step almost everyone skips, and it is the one that tells you whether to buy anything at all.
5. 5.Only then compare tools. If most of your loss is expired cards, you want a recovery flow with a good update page. If it is insufficient funds, Stripe is already doing the main thing. If it is hard declines, no tool will help.

The uncomfortable part of this order is that steps one to three are free and most people have not finished them. A paid tool bought before they are done is paying someone to do work Stripe was willing to do for nothing.

Questions people ask

What is involuntary churn?

A subscription ending without the customer choosing to leave, almost always because a payment failed and was never recovered. It is counted in the same churn figure as a deliberate cancellation, which is why it hides.

What percentage of churn is involuntary?

Paddle's guidance, published 1 September 2023, is that typically 20–40% of churn is involuntary, with one of their own sellers ranging from 19% to 38% over a year. A PYMNTS Intelligence study with FlexPay, published 17 November 2023, puts declined cards at 50% of all customer churn. The two disagree partly because they measure different populations and partly because one is a survey rather than transaction data.

How do I reduce involuntary churn?

In order: enable Stripe's failed-payment emails, review your retry schedule, choose a sensible end-of-dunning state, measure what still fails by decline family, and only then consider a paid tool. The first three cost nothing.

Is involuntary churn the same as failed payments?

No. A failed payment that is later recovered is not churn at all. Involuntary churn is only the part that never recovers, which is why keeping the recovered and still-retrying amounts separate matters when you measure.

Sources

• Paddle — How to reduce SaaS churn — published 1 September 2023, checked 7 October 2026
• PYMNTS — Half of Subscription Cancellations Are Due to Failed Card Payments — published 17 November 2023, checked 7 October 2026
• Stripe Docs — Automate failed payment retries (Smart Retries) — checked 7 October 2026