Skip to content
Churn & retentionMetric 24 of 35

Involuntary Churn

Customers lost to failed cards, not unhappiness.

Abderrahim Ben Jazia, PhDBy · Founder of FlowMRR, previously built and sold AIS (Avance Immédiate Services), French tax-credit softwareUpdated:

Ready to act on this metric? See how FlowMRR helps you reduce involuntary churn right inside your Stripe MRR dashboard.

Churn caused by payments that failed and were never recovered — expired cards, insufficient funds, fraud blocks — rather than by a decision to leave. FlowMRR counts a churned subscription as involuntary when Stripe records the cancellation reason as payment_failed or payment_disputed, or when the subscription is unpaid with no reason recorded; everything else is voluntary. The loss is dated at the end of the last period actually paid for. FlowMRR shows the involuntary share of subscriber churn and the rate itself: subscriptions lost to failed payments ÷ subscriptions active at the close of the previous month, with a revenue version on MRR. It is often the most recoverable part of churn.

Formula

Involuntary Churn Share = Subscriptions lost to failed payments ÷ Total cancellations

Worked example

12 of the 35 subscriptions that ended this month were lost to failed payments → involuntary share = 12 ÷ 35 = 34%. With 1,000 subscriptions at the close of last month, that is an involuntary churn rate of 12 ÷ 1,000 = 1.2%, out of 3.5% total subscriber churn.

Other definitions you will see

Some tools report only the rate, others only the share; a share can rise simply because voluntary churn fell, so read both. Some count customers rather than subscriptions, or count a subscription as lost at the first failed payment instead of when retries end.

Illustrative comparisons

Recovery rate

These unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.

Higher recovery
70%+ recovered
Middle scenario
40–60%
Lower recovery
< 30%

Why it matters

Payment recovery can prevent involuntary churn through smart retries, card updates, and well-timed emails. If total churn is 2% and half of a 30% involuntary share is prevented, churn falls by 0.3 percentage points to 1.7%. Measure the impact using your own churn mix.

Common mistakes

  • Treating involuntary churn the same as voluntary in reporting — they need different fixes.
  • Retrying immediately on failure (banks decline back-to-back) rather than using exponential backoff.
  • Leaving Stripe's automatic card updates off: they can refresh expired or reissued cards before a renewal fails.

Calculating it from Stripe data

Involuntary churn starts with a failed renewal. The invoice stays open, the subscription becomes past_due and Stripe retries the payment according to your retry settings (Smart Retries or a custom schedule). If the last retry fails, Stripe applies the outcome you chose in your Billing settings: cancel the subscription, mark it unpaid, or leave it past_due. While it is past_due the customer has not churned yet; that revenue is at risk, not lost.

To classify an ended subscription, read cancellation_details.reason on the Stripe subscription: payment_failed and payment_disputed are involuntary, cancellation_requested is a deliberate cancellation. FlowMRR tags a churned subscription as involuntary when the reason is payment_failed or payment_disputed, or when it is unpaid with no reason recorded; everything else counts as voluntary. One edge case: if someone on your team cancels a delinquent subscription by hand, Stripe records it as a requested cancellation, so it reads as voluntary although the cause was a failed card.

Date the churn at the end of the last period the customer actually paid for, not the day dunning ends. FlowMRR reports the split as voluntary and involuntary subscriber churn (subscriptions lost ÷ subscriptions at the start of the month), with revenue versions alongside. A first payment that fails is not involuntary churn: the subscription stays incomplete and expires, and a trial whose first charge never succeeds was never a paying customer. If your settings leave subscriptions past_due after the last retry, they never churn by status; they stay in MRR as at-risk revenue until you cancel them, so watch how long they have been in dunning.

Reading the result

Track the involuntary share of churn and the involuntary rate itself; the share can rise simply because voluntary churn fell. Then follow the money upstream: past_due MRR is what is at risk now, unpaid MRR has already churned but can still be recovered, and the two together are the amount to recover. If involuntary churn rises while past_due MRR stays flat, retries are ending faster than customers are reached.

The decline codes on failed payments tell you what to fix. Insufficient funds often clear on a later retry timed around paydays; expired or replaced cards need the customer to update their payment method, so the dunning email and a payment link matter more than another retry; fraud blocks and generic declines may need the customer to contact their bank. Measure what share of failed renewals end paid, and how long recovery takes.

Frequently asked questions

What is the difference between voluntary and involuntary churn?

Voluntary churn is a customer choosing to cancel. Involuntary churn is a subscription ending because payment failed and was never recovered, while the customer may still have wanted the product. They need different fixes: product and pricing work for the first, payment recovery for the second.

How do I find involuntary churn in Stripe?

Look at ended subscriptions and their cancellation_details.reason: payment_failed and payment_disputed mark involuntary endings. If your settings mark subscriptions unpaid instead of cancelling them, count unpaid subscriptions too, dated at the end of their last paid period.

Is a failed first payment after a trial involuntary churn?

No. A customer who never paid was never in MRR, so they cannot churn. A failed first charge is a failed conversion: report it with trial conversion, not with churn.

How can I reduce involuntary churn?

Retry at better times rather than immediately, email the customer with a direct link to update their card before and after a failure, act on decline codes, and follow up on unpaid subscriptions, which are still recoverable. Fix the process first, then measure the share of failed renewals that end paid.

Contact us
FlowMRR

Let's talk

A question, a technical issue or an idea for a partnership? Write to the FlowMRR team.