> 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/es/introduction/how-teams-handle-failed-payments-before-flycode.md).

# Cómo gestionan los pagos fallidos los equipos antes de FlyCode

Los equipos están intentando gestionarlo mediante:

(1) basándose en la recuperación básica de su proveedor de pagos (como la recuperación inteligente básica de Stripe);

(2) usando estrategias de fuerza bruta o de reintento a intervalos fijos, un enfoque heredado que en última instancia reduce las tasas de éxito de los reintentos y aumenta la deserción de clientes;

(3) enviando demasiados o muy pocos correos electrónicos a los clientes (contacte a su banco..).

Uno de los mayores desafíos es que los proveedores de pagos, los bancos emisores y las redes de tarjetas clasifican los errores en distintas categorías y tienen sus propias reglas de riesgo, lo que añade complejidad y hace que muchos errores se agrupen, como ‘No autorizar’.

<figure><img src="https://857825088-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedoXR9BFShbgporwvi7n%2Fuploads%2FhPAgNHFNwpe3u53FAsKS%2Fflycode%20card%20error%20codes.png?alt=media&#x26;token=70b39037-a4d1-4a14-a32a-f28f98490403" alt=""><figcaption></figcaption></figure>

<br>

## Relacionado

* [Gestión de pagos fallidos](https://help.flycode.com/handling-failed-payments) en el Centro de ayuda
* [Guía de gestión de recobros 2026](https://docs.flycode.com/docs/dunning-management-2026-guide)
* [Comparativa de plataformas de recuperación de pagos 2026](https://docs.flycode.com/docs/read-more/payment-recovery-platforms-compared-2026)


---

# 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/es/introduction/how-teams-handle-failed-payments-before-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.