> 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/connecting-flycode-to-stripe.md). # Connecting FlyCode to Stripe How the FlyCode Stripe app connects to your account, why no engineering time is needed, and how it coexists with your existing Stripe webhooks, Radar rules and other apps. FlyCode connects to Stripe as a verified app from the Stripe App Marketplace. There is no API key to paste, no webhook endpoint to build and no code to deploy. This page covers how the connection works, what the setup involves and how FlyCode coexists with everything else you run on Stripe. ## How does FlyCode connect to my Stripe account? The verified FlyCode app installs from the Stripe App Marketplace using Stripe's standard app permission flow. Once installed it subscribes to Stripe Billing events (failed invoices, payment intents, charges, subscription updates) and passes them to FlyCode's decisioning engine. When the engine decides to retry, it calls the Stripe API to pay the invoice, so the retry, the outcome and any invoice or subscription update appear in your Stripe dashboard and event log exactly like a native Stripe action. Recovered revenue lands in your Stripe balance; FlyCode never touches funds. On installation FlyCode also backfills every invoice currently in an error state, so recovery starts on your existing past-due book, not only on new failures. ## Do I need engineering time to set FlyCode up with Stripe? No. Install the app, confirm the permissions, and set two preferences: how FlyCode should retry (or leave the default, model-driven schedule) and whether FlyCode should send recovery emails on your behalf or leave messaging to your existing tool. Most merchants are live in under an hour. The only coordination step is aligning Stripe's own retry and dunning email settings so Smart Retries and Stripe emails do not run in parallel with FlyCode's; the [Stripe integration guide](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode) walks through those settings with screenshots. The first 6 to 8 weeks are an optimization period during which the per-merchant model learns your customers' issuer, card and payment-timing patterns; recovery improves through that window. ## Will FlyCode interfere with my existing Stripe webhooks or apps? No. The app is designed to coexist. It listens to events through its own app installation and never modifies, replaces or overwrites your webhook endpoints, Radar rules, Billing settings or other installed apps. Before each action it re-reads the current state of the invoice and subscription in Stripe to avoid duplicate charges or acting on an invoice that was already paid, voided or cancelled by another system. It also applies a built-in safeguard that never processes a given customer's charge more than a handful of times per hour. If you later add other processors, FlyCode can route retries across them while syncing results back to Stripe; see [Going Further with FlyCode](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode). ## Related * [What FlyCode Adds to Stripe](https://help.flycode.com/flycode-and-stripe/what-flycode-adds-to-stripe) * [How FlyCode Makes Decline Codes Work for You](https://help.flycode.com/decline-codes-explained/how-flycode-makes-decline-codes-work-for-you) * [Stripe <> FlyCode install steps](https://docs.flycode.com/docs/integrations/stripe) --- # 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/connecting-flycode-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.