> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/understanding-involuntary-churn/what-is-involuntary-churn.md). # What Is Involuntary Churn? Involuntary churn defined: customers lost to failed payments rather than a decision to cancel. How it differs from voluntary and passive churn, and why it accounts for 20 to 40 percent of subscription Involuntary churn (also called passive, delinquent or payment churn) is what happens when a customer who wants to keep paying is cancelled because the charge failed. This page defines the term, separates it from the other kinds of churn, and puts a number on why it matters. ## What exactly is involuntary churn? Involuntary churn is when active customers lose access to your service because a recurring payment fails and is never recovered. The customer did not cancel and usually did not know there was a problem; the transaction simply could not go through, most often because of insufficient funds, a generic bank decline, a card that has been replaced or closed, or a processing error. If the failure is not resolved before the billing system's grace period ends, the subscription is cancelled for non-payment and the revenue is lost for the rest of that customer's expected lifetime. The defining feature is intent: the customer still wants the product. That makes involuntary churn an operational problem in the payment flow rather than a product or pricing problem, and it is why it can be reduced quickly. ## How is involuntary churn different from passive or voluntary churn? Voluntary churn is a decision: the customer cancels because of price, a competitor, poor fit or a change in need. Passive churn is disengagement: the customer stops using the product and eventually cancels or lets it lapse. Involuntary churn is triggered by an external payment event outside the customer's control, with no decision and often no awareness. | | Voluntary churn | Involuntary churn | | ------------------ | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | Cause | Customer actively cancels | Payment fails, customer did not intend to leave | | Customer sentiment | Dissatisfied or found an alternative | Still wants the product | | Common triggers | Price, fit, competition, low usage | Insufficient funds, generic declines, replaced or closed cards, bank restrictions, processing errors | | Fix | Product, pricing, onboarding, success programs | Retry timing, backup payment methods, card credential updates, coordinated outreach | | Time to impact | Quarters | Weeks | | Owner | Product, marketing, customer success | Finance, payments, engineering | Each requires its own retention playbook, and the two should be measured separately. A single blended churn number hides the fact that a large share of it can be recovered by payment optimization alone. ## Why should subscription businesses care? Because the number is large and the fix is cheap relative to acquisition. Studies consistently put involuntary churn at 20 to 40 percent of total churn in SaaS and other subscription models, and higher (40 to 55 percent) for consumer and eCommerce subscriptions where debit cards dominate. The average subscription business loses around 9 percent of MRR a year to failed payments. For a company with millions in ARR, a one-point swing in recovery rate equals hundreds of thousands in retained revenue, and every recovered customer keeps paying for months, so the effect compounds. It is also the highest-ROI churn to fix: recovering a customer from a failed payment costs a small fraction of acquiring a replacement, and the recovered customer has already proven willingness to pay. ## Related * [Causes & Risks](https://help.flycode.com/understanding-involuntary-churn/causes-and-risks) * [Involuntary churn: the hidden revenue killer](https://docs.flycode.com/docs/involuntary-churn-hidden-revenue-killer) * [Decline Codes Explained](https://help.flycode.com/decline-codes-explained) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.flycode.com/understanding-involuntary-churn/what-is-involuntary-churn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.