> 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-and-stripe/what-flycode-adds-to-stripe/i-already-use-stripe-smart-retries-why-add-flycode.md).

# I already use Stripe Smart Retries—why add FlyCode?

\- Higher recovery rate: FlyCode recovers, on average, 20 % more failed payments than Stripe.

\- Smarter, adaptive retry engine: Our models go further than Stripe—analyzing failure reasons, adapting retry strategies dynamically (vs. fixed), expanded retry capabilities (Stripe limits to 8) and leveraging alternative payment methods to recover revenue. This adds \~8 % to ARR on average.

\- Data-driven customer communications: FlyCode coordinate emails with the retries. No immediate emails after soft declines (reduces voluntary churn), customized cadences for hard declines (Stripe sends only 1–2), delivery in the customer’s local time, and simple transactional templates sent from high-sender-score domains for maximum deliverability.

\- ROI-linked pricing: Our pricing is tied to the extra revenue we recover, typically delivering a 20× positive 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-and-stripe/what-flycode-adds-to-stripe/i-already-use-stripe-smart-retries-why-add-flycode.md?ask=<question>&goal=<endgoal>
```

`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.