> 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/platform-fit-and-compatibility.md). # Platform Fit & Compatibility How FlyCode and ProfitWell Retain each work with Stripe (replacing versus stacking on Smart Retries), and how the two platforms' technology compares. Both tools connect to Stripe, but they interact with Stripe's native recovery differently, and that affects authorization rates as well as recovery. ## How does FlyCode work with Stripe compared with ProfitWell? FlyCode replaces Stripe's native retry schedule with its own per-merchant models: at go-live you align Stripe's Smart Retries and dunning emails so FlyCode owns the retry decision, and FlyCode then executes each retry through the Stripe API with a schedule built for that invoice. ProfitWell Retain stacks additional retries on top of Stripe's own attempts. Running two retry engines on the same card can push the total number of attempts past what issuers and card networks tolerate, which degrades authorization rates and can trigger excessive-retry fees. FlyCode's approach keeps a single coordinated schedule inside network limits, and every action remains visible in your Stripe dashboard. See [FlyCode & Stripe](https://help.flycode.com/flycode-and-stripe) for the connection details. ## Who's using better technology, ProfitWell or FlyCode? They come from different eras. ProfitWell was founded in 2012 and Retain was built around fixed-interval retries and email sequences, the standard approach at the time. FlyCode was purpose-built as an AI-native payment recovery platform: per-merchant machine-learning models trained with Visa and Mastercard network data, retries separated from communication, backup payment method routing and payment orchestration across processors, and outcome-based pricing. FlyCode is a Stripe design partner, a Mastercard network partner and a Visa Everything Award winner. The measurable difference is the 25 to 40 percent higher recovery described under [Recovery Performance](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/recovery-performance). ## Related * [Stripe Smart Retries complete guide](https://docs.flycode.com/docs/stripe-smart-retries-complete-guide) * [What Makes FlyCode Different](https://help.flycode.com/what-is-flycode/what-makes-flycode-different) --- # 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/platform-fit-and-compatibility.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.