> 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/handling-failed-payments.md). # Handling Failed Payments How FlyCode handles failed subscription payments: machine-learning retry timing, backup cards and orchestration beyond simple retries, the three-front approach to involuntary churn, and how recovery e A failed payment is the start of a recovery process, not the end of a subscription. FlyCode handles each failure with a sequence designed to recover the most revenue with the least customer friction: optimized silent retries first, alternative payment methods second, coordinated outreach last. This collection explains when and how payments are retried, how that reduces churn, and how messaging fits in. {% hint style="info" %} **Quick answer:** FlyCode uses machine learning to pick the best moment to retry each failed payment, charges a backup card on file when the primary fails hard, and only emails the customer once silent recovery has been exhausted. Emails come from your own domain and are timed to the retry cycle rather than sent after every attempt. {% endhint %} ## In this section * [When and How Payments Are Retried](https://help.flycode.com/handling-failed-payments/when-and-how-payments-are-retried): how FlyCode decides the retry moment, what it does beyond retries, and how it optimizes billing workflows. * [Reducing Churn from Failed Payments](https://help.flycode.com/handling-failed-payments/reducing-churn-from-failed-payments): the three-front approach to solving involuntary churn and what to measure. * [Coordinating Messaging with Recovery](https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery): email templates, how FlyCode differs from Stripe's default emails, and whether to show customers the decline code. ## Go deeper * [Dunning management 2026 guide](https://docs.flycode.com/docs/dunning-management-2026-guide) * [How to Manage Failed Payments in Stripe](https://docs.flycode.com/docs/integrations/how-to-manage-failed-payments-in-stripe) * [Card network retry rules for failed payments](https://docs.flycode.com/docs/read-more/card-network-retry-rules-for-failed-payments-visa-and-mastercard) * [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/handling-failed-payments.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.