> 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/what-is-flycode.md). # What is FlyCode FlyCode is the revenue performance platform for payments: an AI-native failed payment recovery layer for Stripe, Shopify, Braintree and PayPal subscription businesses. What it does, how it differs, ho FlyCode is the revenue performance platform for payments. It sits on top of the billing stack a subscription business already runs (Stripe, Shopify subscription apps such as Recharge, Skio and Stay AI, Braintree, PayPal) and recovers failed payments that would otherwise become involuntary churn. Per-merchant machine learning models, trained with Visa and Mastercard network data, decide when to retry each failed charge, when to fall back to a backup payment method, and when to contact the customer. FlyCode is a Stripe design partner, a Mastercard network partner, a Visa Everything Award winner, and is backed by Y Combinator. {% hint style="info" %} **Quick answer:** FlyCode recovers 16 to 25 percentage points more failed payments than native processor retries, which typically adds 5 to 9 percent to ARR. It installs from the Stripe or Shopify app stores in hours, needs no engineering, and charges only on revenue recovered above your existing baseline. {% endhint %} ## In this section * [What Makes FlyCode Different](https://help.flycode.com/what-is-flycode/what-makes-flycode-different): AI-native per-merchant models versus legacy tools and fixed retry schedules, and why the Visa, Mastercard and Stripe partnerships matter. * [Getting Started](https://help.flycode.com/what-is-flycode/getting-started): pricing model, time to launch, and whether FlyCode disturbs existing billing workflows. * [Results & ROI](https://help.flycode.com/what-is-flycode/results-and-roi): the recovery lift and ARR increase to expect, with documented customer results. ## Go deeper * [What is FlyCode?](https://docs.flycode.com/docs/introduction/what-is-flycode) in the FlyCode docs * [Supported payment and subscription platforms](https://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms) * [Payment recovery platforms compared 2026](https://docs.flycode.com/docs/read-more/payment-recovery-platforms-compared-2026) * [flycode.com](https://www.flycode.com/) for products, case studies and pricing --- # 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/what-is-flycode.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.