> 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.md). # FlyCode & Stripe How FlyCode works with Stripe Billing: installing the Stripe app, what FlyCode adds on top of Smart Retries, expected ARR uplift, analytics, multi-processor routing and outcome-based pricing. FlyCode is a verified Stripe app that sits on top of Stripe Billing and recovers failed subscription payments that Stripe's native Smart Retries leave behind. It installs from the Stripe App Marketplace without engineering work, retries invoices directly inside Stripe so every action stays visible in your dashboard, and charges only on revenue recovered above your existing baseline. This collection covers how the connection works, what FlyCode adds to Stripe, and what you get beyond recovery. {% hint style="info" %} **Quick answer:** Stripe merchants using FlyCode typically recover around 20 percent more failed payments than with Smart Retries alone, which translates to a 5 to 9 percent lift in ARR. Setup is a one-click app install plus choosing your retry and email preferences. {% endhint %} ## In this section * [Connecting FlyCode to Stripe](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe): how the app connects, why no engineering time is needed, and coexistence with your webhooks and apps. * [What FlyCode Adds to Stripe](https://help.flycode.com/flycode-and-stripe/what-flycode-adds-to-stripe): why add FlyCode to Smart Retries, the revenue lift, subscription anomalies, and how involuntary churn is cut. * [Going Further with FlyCode](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode): analytics, adding other processors, and pricing for Stripe users. ## Related resources * [Stripe integration guide for FlyCode](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode) (step-by-step setup and go-live checklist) * [Stripe Smart Retries complete guide](https://docs.flycode.com/docs/stripe-smart-retries-complete-guide) * [How to Manage Failed Payments in Stripe](https://docs.flycode.com/docs/integrations/how-to-manage-failed-payments-in-stripe) * [FlyCode on the Stripe App Marketplace](https://marketplace.stripe.com/apps/flycode-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/flycode-and-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.