> 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-vs.-profitwell-paddle-retain/recovery-performance.md). # Recovery Performance How much better FlyCode recovers failed payments than ProfitWell Retain (25 to 40 percent more on average) and the extra ARR lift to expect beyond your current baseline (around 8 percent). The comparison that matters is recovery rate on the same invoices. This page gives FlyCode's measured uplift over ProfitWell Retain and what it means for ARR. ## How much better is FlyCode at recovering failed payments than ProfitWell? On average FlyCode recovers 25 to 40 percent more failed payments than ProfitWell Retain, measured on merchants that moved from Retain to FlyCode and compared on their own invoice population. The gap is largest on `insufficient_funds` declines, where retry timing matters most: FlyCode's models predict when each card is likely to have funds, while a fixed-interval schedule retries on the same days for every customer regardless of payday, issuer or card type. In FlyCode's 500-plus merchant cohort study (March 2024 to June 2025, over USD 1 billion in volume), recovery on `insufficient_funds` was 17.6 to 26.2 percentage points higher than the Stripe and ProfitWell baselines. ## What extra revenue lift can I expect with FlyCode beyond the baseline? Around 8 percent additional ARR on average, with a typical range of 5 to 9 percent. The lift comes from four mechanisms: analysing the failure reason for every decline rather than treating them alike, adapting retry timing dynamically per card and issuer, using the full retry window the card networks allow where a fixed schedule stops early, and charging alternate payment methods on file when the primary card fails hard. Because FlyCode charges only on revenue recovered above your existing baseline, that lift is net of what Retain was already recovering, and the fee is a fraction of it. The [Failed payment cost recovery ROI guide](https://docs.flycode.com/docs/failed-payment-cost-recovery-roi) shows how to estimate the figure for your MRR. ## Related * [What's Different Behind the Scenes](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/whats-different-behind-the-scenes) * [Results & ROI](https://help.flycode.com/what-is-flycode/results-and-roi) --- # 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://help.flycode.com/flycode-vs.-profitwell-paddle-retain/recovery-performance.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.