> 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/flycode-and-stripe/what-flycode-adds-to-stripe.md). # What FlyCode Adds to Stripe Why add FlyCode if you already use Stripe Smart Retries: higher recovery, adaptive per-merchant retries beyond Stripe's 8-attempt cap, coordinated emails, 5 to 9 percent ARR lift, and subscription ano Stripe Smart Retries are a good baseline: they are free, on by default for Stripe Billing, and trained on Stripe's aggregate data. FlyCode layers a per-merchant recovery engine on top of them. This page answers what changes, how much revenue that is worth, and what else FlyCode catches inside Stripe Billing. ## I already use Stripe Smart Retries. Why add FlyCode? Because Smart Retries optimize for the average across millions of Stripe merchants, and a model trained on your own transactions consistently recovers more. Merchants moving from Smart Retries to FlyCode recover on average about 20 percent more failed payments. Four things account for the difference. **Adaptive retry engine.** Stripe applies one fixed strategy and caps attempts at 8 per invoice. FlyCode analyses the failure reason, issuer behaviour, card type, geography and timing for each invoice, adapts the retry schedule dynamically, can use more attempts where card network rules allow, and falls back to alternative payment methods on file. This alone adds roughly 8 percent to ARR on average. **Coordinated customer communication.** FlyCode times emails to the retry cycle instead of firing them at every failure. No email goes out after a soft decline while silent retries still have a good chance (which avoids turning involuntary churn into voluntary cancellations), hard declines get a purpose-built cadence rather than Stripe's one or two default emails, sends land in the customer's local time, and templates are transactional and sent from high-reputation domains for deliverability. **Root-cause analytics.** Decline code distribution, recovery rate by failure type, retry performance and anomaly alerts, none of which Stripe's dashboard breaks out. **Outcome-based pricing.** FlyCode charges a share of revenue recovered above your prior baseline, so if it does not beat Smart Retries you pay nothing. ## How much extra revenue can FlyCode unlock? Stripe merchants typically see a 5 to 9 percent increase in ARR from recovered payments alone. Documented examples include GitBook (+29 percent recovery improvement, 8 percent ARR lift) and Framer (+18 percent recovery improvement, 6 percent ARR lift). The lift is larger for businesses with a high share of consumer debit cards and for those whose renewals fall on fixed dates, since those have the most recoverable `insufficient_funds` declines. The [Failed payment cost recovery ROI guide](https://docs.flycode.com/docs/failed-payment-cost-recovery-roi) has a framework for estimating your own number. ## Can FlyCode fix subscription-status anomalies Stripe sometimes misses? Yes. FlyCode's Subscription Anomaly Agent monitors invoices, proration events, refunds and invoices marked uncollectible, and flags cases where Stripe still shows a subscription as active even though it is no longer being paid, or where billing state has drifted from what the customer should be charged. These anomalies leak revenue quietly because nothing in the default Stripe reporting surfaces them. See [Managing the Stripe Billing lifecycle and reporting](https://www.flycode.com/blog/stripe-guide-manage-stripe-billing-lifecycle-and-reporting) for the full breakdown. ## How does FlyCode cut involuntary churn for Stripe businesses? By addressing the main causes of involuntary churn in order of impact: recovering soft declines (insufficient funds and generic declines) with optimized retry timing before the customer is contacted; charging a backup payment method on file when the primary card fails hard; keeping card credentials current through Card Account Updater and Network Tokens; and reaching customers who do need to act with well-timed, specific messages. Customers who would otherwise have been cancelled for non-payment stay active, and because they never chose to leave, retained revenue continues for the rest of their lifetime. ## Related * [Stripe Smart Retries complete guide](https://docs.flycode.com/docs/stripe-smart-retries-complete-guide) * [Understanding Involuntary Churn](https://help.flycode.com/understanding-involuntary-churn) * [FlyCode vs. ProfitWell (Paddle Retain)](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain) --- # 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/flycode-and-stripe/what-flycode-adds-to-stripe.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.