> 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.md). # Understanding Involuntary Churn What involuntary churn is, how it differs from voluntary churn, why failed payments cause it, what it costs subscription businesses beyond lost revenue, and how FlyCode prevents it without changing yo Involuntary churn is the loss of customers who never chose to leave: their subscription lapsed because a payment failed. It is the largest fixable source of churn in most subscription businesses, and unlike voluntary churn it does not require product or pricing changes to reduce. This collection defines it, explains what causes it and what it costs, and shows how FlyCode addresses it. {% hint style="info" %} **Quick answer:** studies put involuntary churn at 20 to 40 percent of total churn in SaaS and other subscription models, and the average subscription business loses around 9 percent of MRR a year to failed payments. Most of it is recoverable, because the customer still wants the product and most declines are temporary. {% endhint %} ## In this section * [What Is Involuntary Churn?](https://help.flycode.com/understanding-involuntary-churn/what-is-involuntary-churn): the definition, how it differs from voluntary and passive churn, and why it matters. * [Causes & Risks](https://help.flycode.com/understanding-involuntary-churn/causes-and-risks): why payments fail, what hard declines mean, and what is at risk beyond the invoice. * [FlyCode's Approach to Churn](https://help.flycode.com/understanding-involuntary-churn/flycodes-approach-to-churn): how FlyCode attacks involuntary churn, whether automation prevents it, and best practices to keep. * [Integration Considerations](https://help.flycode.com/understanding-involuntary-churn/integration-considerations): why you do not need to rebuild your billing stack. ## Go deeper * [Involuntary churn: the hidden revenue killer](https://docs.flycode.com/docs/involuntary-churn-hidden-revenue-killer) (benchmarks by segment, KPI framework, 5-step plan) * [Failed payment cost recovery ROI](https://docs.flycode.com/docs/failed-payment-cost-recovery-roi) * [Failed payment recovery glossary](https://docs.flycode.com/docs/read-more/failed-payment-recovery-glossary) * [Free churn analysis for your subscription business](https://www.flycode.com/churn-audit-failed-payments) --- # 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.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.