Not all churn is the same kind of problem.
The share caused by failed payments is fixable without changing a single thing about your product. The share from real cancellations isn't. This shows you which is which.
Enter your MRR, churn rate, and processor. See how much is billing failures (fixable) vs. real cancellations (not).
Splitter
Payment processor
Stripe accounts: ~30% of subscription churn is billing failures, not cancellations
Total churn / mo
$2k
3% of MRR
Involuntary / mo
$450
payment failures
Voluntary / mo
$1k
chose to cancel
Saveable / year
$3k
at up to 60% recovery
12-month MRR projection
with vs without involuntary churn recovery
Related free tools
Involuntary churn benchmarks are per-processor averages. Connect your account to measure your actual split.
Connects to Stripe in under 5 minutes. Starts recovering the same day.
How it's calculated
How it's calculated
Total churned MRR = MRR × total monthly churn rate. At $100K MRR and 5% churn, $5,000 in MRR exits each month.
Involuntary churn MRR = total churned MRR × involuntary churn percentage. If 30% of churn is from billing failures, $1,500/month is involuntary. This portion requires a billing fix, not a product or retention fix.
Recoverable MRR = involuntary churn MRR × (target recovery rate − current rate). If you currently recover 30% and move to 65%, you recover 35% more of the $1,500 — that is $525/month permanently added back.
12-month projection compounds the effect over time. Each recovered payment extends the subscription, which also extends the base for future recovery attempts. The compounding is modest but real.
Churn, split apart
Churn, split apart
Voluntary churn is a decision: the customer clicked cancel because the product wasn't worth the price, they found a competitor, or their needs changed. Involuntary churn is an accident: the card on file expired, the bank declined the charge for insufficient funds, or a routine fraud check blocked a legitimate renewal — and the subscription lapsed even though the customer never chose to leave. The two get reported as one number on most dashboards, which is the problem. They have completely different fixes. Voluntary churn needs product, pricing, or positioning changes that take quarters to land. Involuntary churn needs a better retry and dunning system — infrastructure that can be live in days.
Pull your cancelled-subscription list for the last 90 days from Stripe, Paddle, RevenueCat, or whatever processor you run on, and sort by cancellation reason. Most processors tag this automatically: a subscription that ends because the customer clicked "cancel" is voluntary; one that ends because the system exhausted its retry attempts on a failed charge is involuntary. If your processor doesn't expose the split directly, look at the event right before cancellation — a invoice.payment_failed event followed by customer.subscription.deleted with no intervening cancel action is involuntary churn, full stop. Divide involuntary cancellations by total cancellations and you have your real split — usually somewhere between 25% and 50% depending on processor and audience, per the benchmarks above.
Reducing voluntary churn means changing something the customer experiences — the product, the price, the onboarding — and validating that the change actually moves the number, which takes a full churn cycle (often a quarter or more) to confirm. Reducing involuntary churn means changing something the customer never sees: when the system retries a declined charge, what it says in the recovery email, and whether it catches an expiring card before the renewal date arrives. None of that touches the product or the price, none of it requires customer buy-in, and the impact shows up in the next billing cycle — not the next roadmap review. Dollar for dollar, it is the highest-leverage churn work most subscription businesses aren't doing yet.
Fixing involuntary churn doesn't make total churn disappear — it isolates the part that's actually a product or positioning problem. Once recovery is running and the payment-failure slice has shrunk to a fraction of its former size, what remains on the churn report is mostly people who genuinely decided to leave. That's a smaller number, but a more honest one — and it's the number worth spending product and retention budget against, because every dollar spent improving the product now shows up in the churn rate instead of getting absorbed by a payment-infrastructure problem hiding underneath it.
Related free tools
NRR Calculator
See how payment recovery directly improves net revenue retention
Failed Payment Calculator
Calculate your monthly MRR at risk from billing failures
Payment Recovery ROI Calculator
See the ROI of improving your payment recovery rate
LTV Impact Calculator
See how recovery improvement compounds into higher LTV
Common questions
Common questions
High churn has two distinct root causes: customers choosing to leave (voluntary) and payment failures ending subscriptions without intent to cancel (involuntary). The only way to know the split is to look at churned subscriptions and separate billing-failure exits from deliberate cancellations. Typically 20–40% of SaaS churn is involuntary. If you are applying retention tactics to churn that is actually billing failures, none of it will work — you are solving the wrong problem.
In Stripe, involuntary churn shows up as subscriptions cancelled due to payment failure (status: canceled, cancellation details pointing to payment_failed). Voluntary shows up as subscriptions cancelled at_period_end or via customer-initiated cancellation. The simplest split: count churned subscriptions where the last event was a payment failure versus a cancellation request. Industry average is 20–40% involuntary.
The involuntary share — typically 20–40% of total churn — is fixable with payment recovery alone, no product changes needed. If 30% of your churn is involuntary and you achieve a 60% recovery rate on those failures, you fix 18% of total churn. For a $100,000 MRR business at 5% churn, that is $900 per month recovered.
Involuntary churn is caused by payment failures and is fixed with: failure-code-specific retry timing, dunning email sequences starting within 24 hours, in-app payment update prompts, and proactive card expiry outreach. Together these move recovery from 25–30% (processor defaults) to 60–70%, cutting involuntary churn by more than half.
Yes. Recovered failed payments count as prevented churn, directly reducing your net monthly churn rate. Cutting 0.5 percentage points off a 4% churn rate extends average customer lifetime from 25 months to 29 months — an 18% LTV increase with no acquisition spend.
The billing slice of your churn has a different fix than the rest.
Recurflux handles the fixable portion — code-specific retries, adaptive dunning, card expiry monitoring. The product-and-pricing problems stay yours. Founder plan from $20/month, flat fee.