> 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/getting-started.md). # Getting Started Getting started with FlyCode: outcome-based pricing with no seats or minimums, launch in hours via the Stripe or Shopify apps or API keys, and how FlyCode runs alongside your billing workflows without Three questions come up before every FlyCode evaluation: what it costs, how long it takes to launch, and whether it will disturb billing that already works. The short answers are pay-on-results, hours, and no. ## What pricing model does FlyCode use? FlyCode charges only on the dollars it actually recovers above your existing baseline. There are no seats, no platform fee and no minimums. The baseline is what your processor or previous tool was already recovering, so FlyCode is paid only for incremental revenue; if it recovers nothing beyond your baseline, you pay nothing. This aligns incentives: FlyCode's revenue grows only when yours does, and the ROI is positive by construction. Documented customer results range from roughly 6X to 13X. Current rates are on [flycode.com/pricing](https://www.flycode.com/pricing). ## How fast can we launch FlyCode? Most customers go live in hours. On Stripe, install the verified FlyCode app from the Stripe App Marketplace, confirm permissions and set your retry and email preferences. On Shopify, connect through the Recharge, Skio or Stay AI integration. On Braintree and PayPal, create a restricted role and API user for FlyCode. There is no code to deploy and no checkout change. Once connected, FlyCode backfills invoices already in an error state and starts recovering immediately; the model then tunes itself to your customers over the first 6 to 8 weeks. Step-by-step guides are in the [FlyCode docs](https://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms). ## Is this going to break my current billing workflows? No. FlyCode runs in parallel with your billing platform and syncs status updates back to it without overwriting rules or duplicating events. It listens to failed-payment events, decides how to recover each one, executes the retry through your processor's own API, and updates the invoice and subscription state in your platform so it remains the source of truth. Before each action it re-checks the current state of the invoice to avoid double charging or acting on something another system already resolved. Existing webhooks, apps, tax, invoicing and accounting integrations are untouched. The only alignment step is turning off or adjusting your platform's native retry and dunning email schedule so two engines do not act on the same invoices. ## Related * [Connecting FlyCode to Stripe](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe) * [FlyCode & Shopify: Setup & Requirements](https://help.flycode.com/flycode-and-shopify/setup-and-requirements) * [Integration Considerations](https://help.flycode.com/understanding-involuntary-churn/integration-considerations) --- # 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/getting-started.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.