TL;DR

  • Voluntary churn follows a customer's decision to stop renewal; involuntary churn follows an unrecovered payment failure.
  • A failed renewal is a recovery state first, not automatically churn.
  • Report cancellation intent, payment failure, recovery, and lost access as different events.
  • Use product and plan work for voluntary churn, and a clear recovery path for involuntary churn.
  • Calculate each rate with a stable denominator and cohort rather than one blended loss number.

Two subscribers disappear from the active list. One turned off renewal after deciding the product was not worth another month. The other had a card problem and never found the way back to access. A single churn number makes those events look identical. They are not.

Voluntary churn is a choice to leave. Involuntary churn is an unrecovered payment failure. Separating them keeps product work from being mistaken for a billing fix, and it gives customers the right next step.

What is voluntary churn?

Voluntary churn happens when a customer intentionally cancels or turns off auto-renewal and their paid access eventually ends. In a subscription app, the cancellation decision can happen before the current paid period expires. That makes cancellation intent and loss of access related but distinct events.

Apple’s cancellation reasons reference includes a Canceled category as well as billing-related categories. The labels are useful for reporting, but they are not an explanation by themselves. A cancellation might point toward unmet value, price, plan fit, an expectation set before purchase, or something else that needs product and customer context.

What is involuntary churn?

Involuntary churn happens when payment collection fails and the subscription ultimately ends without recovery. An expired card, insufficient funds, or a bank decline can start that path. The first failed payment is not automatically involuntary churn. It is a payment-recovery state until the platform’s retry and grace rules have run their course.

Stripe’s Smart Retries documentation describes retrying failed subscription payments. The schedule and available recovery tools depend on the billing setup. For store-billed subscriptions, do not copy a Stripe workflow onto an App Store state.

Apple says it can continue attempting to collect an auto-renewable subscription after a billing issue, and its Billing Grace Period documentation explains the opt-in period during which eligible subscribers can retain access while Apple attempts to collect. Check the current subscription state before classifying someone as lost.

Illustration of an active subscription branching into cancellation and payment recovery paths
Illustration: an intentional cancellation and a failed renewal begin different paths. A payment failure may still recover before access is lost.

How are voluntary and involuntary churn different?

The difference is both the cause and the next action.

State Trigger What to investigate first Next customer action
Cancellation scheduled Customer turns off renewal Product value, plan fit, price, expectation Manage the remaining access and any eligible save path
Payment failure Renewal does not collect Billing status, decline type, recovery window Update payment or follow the platform recovery path
Payment recovered A later attempt succeeds Time to recover and repeat failure risk Restore the normal experience
Lost after failure Recovery window ends without payment Where the recovery path failed Treat as involuntary churn and consider a return path

This table is why a cancellation survey cannot solve every lost subscription. It can help a team understand a deliberate cancellation, but it does not update a payment method or resolve a bank decline. Subscription cancellation reasons covers the App Store report labels and where an in-app survey fits.

How should you calculate each churn rate?

Use the same basic rate for a stable cohort, but keep the numerators separate:

voluntary churn rate = customers who lost paid access after cancelling / starting active customers × 100
involuntary churn rate = customers who lost paid access after unrecovered payment failure / starting active customers × 100

Choose the period and active-customer definition before looking at the result. Then retain the events that explain the journey: cancellation scheduled, payment failed, payment recovered, entitlement ended, and re-subscription. A recovered failed payment should not appear in the involuntary-churn numerator just because it began with a decline.

The denominator can vary by business model, but it must be consistent when comparing periods. If annual and monthly plans behave differently, show them separately instead of letting one mix hide the other.

What should you do about voluntary churn?

Voluntary churn calls for a value and fit investigation. Read the affected cohort, plan, tenure, product behavior, cancellation context, and support contacts together. A first-renewal cancellation after weak activation asks a different question from a long-tenure cancellation after a price change.

The next step may be a product change, clearer onboarding, a better plan option, or an eligible save offer. It is not automatically a discount. How to reduce churn maps those customer states to the work that fits them, and churn analysis covers the diagnosis before a team picks a tactic.

What should you do about involuntary churn?

Involuntary churn calls for a recovery path. Make the billing problem understandable, route people to the correct update-payment action, and make access behavior match the store or processor state. Track how long recovery takes and where customers fall out of the path.

For Apple, the store owns the billing mechanics. Apple documents subscription billing handling for the relevant subscription states. Validate purchases and current entitlement before showing a customer a generic acquisition paywall or asking them to buy again.

Failed payment recovery for subscription apps goes deeper on recovery windows, access, and measurement. The important boundary is simple: do not label a recoverable billing issue as proof that the customer chose to leave.

What should the weekly report include?

Keep the summary short enough to act on:

  • Starting active customers, split by plan or platform where that matters.
  • Cancellations scheduled and voluntary losses after expiry.
  • Failed renewals, recoveries, and losses after the recovery window.
  • Time to payment recovery and repeat failure at the next renewal.
  • The product, pricing, release, or billing change that may explain a movement.

A team can then assign the right work. Product and lifecycle owners can investigate a cancellation pattern. Billing and support owners can inspect a recovery breakdown. Neither group has to defend a number that mixed their two problems together.

Refix is built to connect product behavior, subscription events, and support signals so teams can trace a churn change back to the customer state behind it.

See how Refix connects the signals behind retention work.

FAQ

What is voluntary churn?
Voluntary churn occurs when a customer intentionally cancels or turns off renewal and paid access eventually ends. The customer may still have access until the current paid period expires.
What is involuntary churn?
Involuntary churn occurs when a subscription ends after payment collection fails and the failure is not recovered. A failed renewal can be recoverable, so it should not be counted as churn immediately.
How do you calculate voluntary and involuntary churn?
For each category, divide customers whose paid access ended for that reason during a period by the starting active customers in the defined cohort, then multiply by 100. Keep payment failures that are still in recovery out of the involuntary-churn numerator.
Why separate voluntary and involuntary churn?
The underlying actions differ. Voluntary churn may point to value, price, or plan fit. Involuntary churn needs payment recovery, clear customer communication, and correct access handling.