> 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/introduction/how-teams-handle-failed-payments-before-flycode.md).
# 🚨 How teams handle failed payments before FlyCode?
Teams are trying to handle it by:
(1) relying on the basic recovery of their payment provider (like Stripe basic smart recovery);
(2) brute forcing or fixed-interval retry strategies, a legacy approach that ultimately reduces retry success rates and increases customer churn;
(3) sending too many or too few emails to customers (contact your bank..).
One of the biggest challenges is that payment providers, issuing banks, and card networks classify errors into different categories and have their own risk rules, which adds complexity and leads to many errors getting bucketed together, such as ‘Do not honor’.
---
# 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:
```
GET https://docs.flycode.com/docs/introduction/how-teams-handle-failed-payments-before-flycode.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.