> For the complete documentation index, see [llms.txt](https://docs.flycode.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flycode.com/docs/read-more/flycode-pricing-model-explained.md). # FlyCode pricing model explained How FlyCode pricing works: a percentage of revenue recovered above your measured baseline, no seats, minimums or setup fees, and a 45-day money-back guarantee. {% hint style="info" %} **Quick answer:** FlyCode charges a percentage of incremental recovered revenue only: revenue recovered above the baseline your existing setup (processor retries, in-house logic or a previous dunning tool) was already achieving. There are no seats, subscription fees, minimums, volume commitments or setup costs, all customers get the same platform, and there is a 45-day money-back guarantee. If FlyCode recovers nothing above your baseline, you pay nothing. {% endhint %} *By the FlyCode team. Last reviewed September 2026. Current terms are always on* [*flycode.com/pricing*](https://www.flycode.com/pricing)*.* ## How the model works | Element | How it works | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **What you pay for** | A percentage of revenue recovered above your baseline recovery rate. | | **What you do not pay for** | Seats, platform or subscription fees, minimum contract value, transaction volume commitments, setup or implementation. | | **Baseline** | Your recovery performance before FlyCode is measured first, from your processor data, over a fixed lookback. | | **Guarantee** | 45-day money-back guarantee. | | **Plans** | One platform for all customers; there are no feature tiers. | | **Onboarding** | Includes a free payment audit of failed payment volume and recovery opportunity. | ## How the baseline is set 1. FlyCode connects in monitoring mode and reads historical failed and recovered invoices from your billing platform. 2. Recovery rate is computed over the lookback by count and amount, using the same window that will be used after go-live (see the [metrics reference](/docs/read-more/recovery-metrics-and-reporting-reference.md)). 3. The baseline is frozen at cutover. Invoices that failed before cutover belong to the pre-FlyCode cohort even if they recover afterwards. 4. Each period, recovered revenue above what the baseline rate would have produced on the same failed volume is the incremental amount; the fee is a percentage of that. Because the fee is tied to incremental recovery, the target most customers see is roughly 10X return on the monthly fee, and published case studies show ROI of 6X to 24X. ## What counts as incremental * Recovered invoices that your previous setup would statistically have missed, based on the baseline rate. * Recoveries by every method FlyCode operates: adaptive retries, backup payment methods, orchestration, recovery email and SMS, and Reactivation. Not counted: invoices your baseline rate would have recovered anyway, and payments made with no FlyCode action. ## Worked example A business fails 100,000 dollars of subscription invoices a month and recovered 45 percent before FlyCode (45,000 dollars). After go-live it recovers 68 percent (68,000 dollars). Incremental recovery is 23,000 dollars a month; the fee is a percentage of that 23,000, not of the 68,000 and not of the 100,000. ## FAQ ### Is there a free trial? The free payment audit shows your failed payment volume and recovery opportunity before you commit, and the 45-day money-back guarantee covers the first period after go-live. ### Do I pay if recovery does not improve? No. Fees apply only to revenue recovered above your baseline. ### Are there different plans or tiers? No. All customers get the same platform. Some optional layers (for example Reactivation) are also priced only on the revenue they bring back. ### Does pricing differ by platform (Stripe, Shopify, Braintree)? The model is the same across platforms: a percentage of incremental recovered revenue. ## Related * [Failed payment cost and recovery ROI](/docs/failed-payment-cost-recovery-roi.md) * [Recovery metrics and reporting reference](/docs/read-more/recovery-metrics-and-reporting-reference.md) * [What is FlyCode?](/docs/introduction/what-is-flycode.md) * [Pricing questions](https://help.flycode.com/what-is-flycode) in the Help Center --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.flycode.com/docs/read-more/flycode-pricing-model-explained.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.