Voluntary vs involuntary churn: what's the difference, and which to fix first

Short answer: Involuntary churn is when a subscription ends because a payment failed — an expired card, insufficient funds, a bank decline — while the customer didn't choose to leave. Voluntary churn is when the customer decides to cancel. Involuntary churn is fixed with payment recovery (retries, card-update emails). Voluntary churn is fixed earlier, by noticing that a customer stopped getting value while they're still paying.

The two side by side

Involuntary churn: a billing problem

A customer whose card expired didn't decide anything. They'd renew if you asked them the right way at the right time. That's why involuntary churn responds so well to mechanics: retrying the charge when it's likely to succeed, emailing a link to update the card, reminding customers before a card expires.

Stripe includes some of this (Smart Retries, emails for failed payments), and dedicated tools — Churn Buster, Paddle Retain, Baremetrics Recover — go further with SMS, in-app notices, and tuned retry schedules. If a large share of your cancellations come from failed payments, start here: it's the fastest revenue to win back, because the customer never wanted to go.

Voluntary churn: a value problem

The customer who cancels on purpose made the decision long before they clicked the button. The team that logged in every day started logging in once a week. The account that paid for four months never finished setting up. The billing record shows none of it — every invoice was paid on time.

That's what makes voluntary churn hard: there's no billing event to react to until it's too late. The early signal is behavior, and it lives in your product analytics, not in Stripe.

Fixing it means joining the two:

1. List paying customers with their MRR from your billing system.
2. Pull recent usage per customer from your analytics — this week against last week, plus the last date seen.
3. Flag the patterns: usage that dropped, accounts gone silent, and customers who never started.
4. Rank by MRR and put an owner on each account.

The step-by-step version is in How to detect churn risk from Stripe data.

Which should you fix first?

Look at your last 20 cancellations and sort them into two piles: the ones that followed a failed payment, and the ones that didn't.

• Mostly failed payments? A recovery tool pays for itself first. The customers wanted to stay.
• Mostly on-purpose cancellations? Recovery tools won't touch them. You need to see usage decline before the decision — that's the problem Keep is built for.
• Both? Most subscription businesses have both, and the tools don't overlap: one reacts to billing, the other watches usage.

FAQ

Is a downgrade voluntary churn?

It's contraction rather than churn, but it's voluntary: the customer chose to pay less. It's often the step before a cancellation, so it's worth an alert.

Does a customer who doesn't renew an annual plan count as involuntary?

Only if the renewal failed on payment. If they turned off auto-renew or told you they're leaving, it's voluntary.

Can you prevent voluntary churn with a cancel flow?

Sometimes. A cancel flow with an offer can save customers at the last step. But by the time someone reaches the cancel button, the decision is mostly made; reaching out when their usage first drops gives you more room.

Which one is bigger?

It varies by business. Products billed to cards with small monthly amounts tend to see more involuntary churn; higher-priced B2B products billed by invoice see more voluntary churn. Your own cancellation history is the only reliable answer.