← Back to blog

What Is Involuntary Churn? (Failed Payments, Not Cancellations)

9 min read

A churn dashboard counts every ended subscription the same way: one more customer gone. Some of those customers decided to leave. Others never decided anything. A renewal charge failed, the retries ran out, and the subscription lapsed. The dashboard files both under churn, and they are not the same problem.

Involuntary churn is a subscription that ends because a payment failed, not because the customer cancelled. Nobody clicked cancel. The card expired, the bank declined the renewal, or the account was short on the day, and the subscription ended before anyone fixed it. This page defines the term, sets it against voluntary churn, covers why failed payments cause it, and lists what recovers the revenue. How to measure your own share, with a worked example, is in what percentage of your churn is actually failed payments. This page does not repeat that method.

What involuntary churn means

"Involuntary" describes the customer's choice, not the customer's mood. They still wanted the product. The payment is what stopped.

On a Stripe subscription the trail is usually the same. A renewal invoice fails. The subscription can move to past_due while retries run. That status means the payment failed or was not attempted. It does not say whether the customer meant to stay. When the retry window closes, the ending you set under Retries is applied: cancel the subscription, mark it unpaid, leave it past due, or pause it. A cancellation or an unpaid subscription is where the revenue stops, and where involuntary churn shows up in your numbers.

Stripe records "subscription ended" as one outcome. The reason is in what happened just before it. That is why a churn report can add the two kinds together without any sign that they differ.

Is passive churn the same thing?

Usually, yes. In subscription billing, "passive churn" is the same idea under a different name: the customer did not act, and the subscription ended anyway. This page uses involuntary churn and treats the two as synonyms. There is no second metric hiding behind the other word. If a report or a vendor uses "passive churn" for something broader, ask what it counts before you compare its number with anything on this page.

Involuntary vs voluntary churn

Voluntary churn is a decision. The customer used the product, weighed it against the price or a competitor, and cancelled. Involuntary churn is a billing outcome. The customer did nothing, and a failed charge ended the subscription.

Voluntary churnInvoluntary churn
What happenedThe customer decided to leaveA payment failed and was not fixed in time
Usual trail in Stripeactive to canceledactive to past_due (or unpaid) to canceled
What it tells youProduct, price, onboarding or fitBilling setup: retries, notices, the card-update path
Who usually owns itProduct, customer successBilling, finance or payments ops
What moves itProduct work, pricing, positioningRetries, a notice the customer opens, a working fix link, the ending you chose

The levers are different, so the owners are different. A product team measured on a churn number that includes failed cards is measured on something it cannot change. A billing owner handed the whole blended number is chasing cancellations that were never about billing. Split the two before you assign either.

Why failed payments cause it

Every involuntary churn event starts with a declined renewal. The decline falls into one of a few groups, and the group decides what can still save the subscription.

The card has expired or been replaced. The card on file reached its expiry date, or the issuer reissued it. The renewal fails because the stored details are stale. expired_card is not on the short list of codes Stripe refuses to retry, so a retry can still run, but a retry does not update the number. The customer has to supply a card that works. Which codes are which is in hard declines vs soft declines.

The account was short, or the issuer said no without saying why. insufficient_funds, do_not_honor and generic_decline are soft declines. The card is not finished, and a later charge can clear. They become churn when the retry window ends before the money lands, or when the customer never learns there is a problem. How to have fewer of them, and when a later attempt is worth running, is in how to reduce soft declines.

The card cannot pay at all. Hard declines such as lost_card and stolen_card mean this card cannot complete the charge, however many times it is tried. Stripe does not run a live retry against a short list of these codes. The slot stays on the schedule, and no new charge is created until a new payment method is attached. Only the customer can end that.

The email arrived and nobody acted. Stripe can email the customer after every failed payment. The same note, repeated, gets archived, and a hosted update link inside it stops working once the subscription has ended. A customer who skipped the message does not experience it as a warning. They experience it as a cancellation they did not choose. Why that email gets skipped is in why customers ignore Stripe failed-payment emails.

In every group the subscription ended while something could still have changed the outcome: a later charge clearing, or a card being updated. That is why involuntary churn is the part of churn that responds to billing work rather than a product roadmap.

What share of your churn is involuntary?

There is no single answer, and this page does not give a RetryFix figure. Industry benchmarks put involuntary churn at 20–40% of total churn for card-based subscription businesses, which is the range the measurement post uses as its illustration. It is not a RetryFix rate and it is not a forecast for your account. Monthly plans tend to see more of it than annual plans, because they have more renewals that can fail. Your own share can sit inside that range or outside it. The number that tells you where to spend effort is the one from your own subscriptions.

What recovers the revenue

Involuntary churn is recoverable in a way voluntary churn is not, because the customer did not leave on purpose. Not every failed payment comes back, and no recovery rate is guaranteed. Four things do the work, and they work together.

1. Retries where a later charge can still collect. A soft decline can clear on a later attempt, and a retry is how it clears. Stripe's Smart Retries choose the times inside the window you set. The setup, and how to match timing to the decline, is in how to retry failed Stripe payments. A retry on a card that cannot pay collects nothing. Smart Retries alone are commonly discussed as recovering around 30–40% of failed payments. That is an illustrative industry figure, not a RetryFix result and not a guarantee. Why the rest stays open is in why Smart Retries alone are not enough.

2. A notice the customer will open. One that names the card, says whether a later attempt can still clear or this card cannot pay, and gives one way to fix it. A note that is identical after every attempt does none of that. What a good one says, and how the whole process fits together, is in what dunning is.

3. A working card-update path. One link that updates the payment method the next attempt will charge, and that still loads when the customer clicks it. Stripe's hosted update link stops working when the subscription is canceled, incomplete_expired or unpaid, so the last notice has to go out while it still works. Automatic card updates can refresh a reissued number before a renewal fails on it. They sit before the failure, and they do not replace a notice when the card is simply expired.

4. An ending you chose. When the window closes, the subscription follows a setting under Retries: cancel, unpaid, past due or pause. That setting decides whether an unpaid invoice appears as a cancellation in your churn report, and the last notice has to name the same ending. The Stripe timeline for all of this is in the dunning process, step by step.

Running those four as one process, rather than as four separate settings, is what payment retry software adds beyond Stripe's own retries.

Common questions

What is involuntary churn?

A subscription that ends because a payment failed, not because the customer cancelled. The card expired, the bank declined the renewal, or the account was short, and the subscription lapsed before the card was fixed. The customer did not decide to leave.

What is passive churn?

Usually the same thing as involuntary churn, under another name. In subscription billing it points at the customer who did not act while the subscription ended anyway. If a report uses it for something broader, check what it counts before comparing numbers.

How is it different from voluntary churn?

Voluntary churn is a decision, and it responds to product, pricing and fit work. Involuntary churn is a failed-payment outcome, and it responds to retries, notices, a working card-update path and the ending you chose. The owners are usually different too.

How do you measure it?

Take the subscriptions that ended in a period and read each one's status just before it ended. Straight from active to canceled is voluntary. A past_due or unpaid stretch first is involuntary. Divide the involuntary count, and the involuntary MRR, by the total. The full method, with a cross-check and a worked example, is in what percentage of your churn is actually failed payments.

How do you reduce it?

Make sure a later charge can still collect on soft declines, send a notice the customer will open, give them one working way to update the card, and choose the ending on purpose. Each is covered above, and how to retry failed Stripe payments is the practical setup for the first.

Where to start

Open a few subscriptions that recently cancelled and read the timeline on each. Look for an invoice.payment_failed event, and a past_due stretch, before the cancellation. Where you find them, that customer did not decide to leave. That is a spot check, not the measurement. The method for the real number is in the measurement post.

On RetryFix, recovery emails go out in your company name, with a line saying RetryFix sent them on your behalf. You do not edit the wording. Branded sending is included on both plans, Pay on recovery (10% of recovered revenue) and Flat rate (£49), at no extra cost. The emails are the customer-facing sequence on top of your processor's retries. They are not a second retry clock. Who the message appears to come from is in branded dunning emails. To see the failed payments on your own account before anything is sent to your customers, try the demo. RetryFix never holds or moves your money; recovered payments land in your own Stripe account.

See how RetryFix recovers failed payments in under 2 minutes

RetryFix never holds or moves your money; recovered payments land in your own Stripe account.