> 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/read-more.md).

# Reference and comparisons

- [Stripe decline codes reference: meaning, soft or hard, and what to do](https://docs.flycode.com/docs/read-more/stripe-decline-codes-reference-meaning-soft-or-hard-and-what-to-do.md): Every Stripe decline code in one table: meaning, soft or hard, whether to retry, and the recovery action to take, with links to full explainers for each code.
- [Card network retry rules for failed payments: Visa and Mastercard](https://docs.flycode.com/docs/read-more/card-network-retry-rules-for-failed-payments-visa-and-mastercard.md): Visa and Mastercard retry rules for declined recurring payments: attempt limits, the 30-day and 24-hour windows, never-retry codes, fees and a compliance checklist.
- [Failed payment recovery glossary](https://docs.flycode.com/docs/read-more/failed-payment-recovery-glossary.md): Failed payment recovery glossary: involuntary churn, dunning, soft and hard declines, decline codes, Smart Retries, Card Account Updater, network tokens and more.
- [FlyCode vs Churnkey for failed payment recovery](https://docs.flycode.com/docs/read-more/flycode-vs-churnkey-for-failed-payment-recovery.md): FlyCode vs Churnkey: Churnkey is a cancel-flow tool with a recovery module that stacks retries on Stripe; FlyCode replaces the retry engine. Features, pricing, fit.
- [FlyCode vs Butter Payments for failed payment recovery](https://docs.flycode.com/docs/read-more/flycode-vs-butter-payments-for-failed-payment-recovery.md): FlyCode vs Butter Payments: both replace the retry engine with ML; they differ on integrations, backup payment routing, outreach, network data and time to deploy.
- [Payment recovery platforms compared 2026](https://docs.flycode.com/docs/read-more/payment-recovery-platforms-compared-2026.md): 2026 comparison of failed payment recovery platforms: FlyCode, Stripe Smart Retries, Butter, Churnkey, Paddle Retain, Vindicia, Redux and more, with rates and pricing.
- [Recovery metrics and reporting reference](https://docs.flycode.com/docs/read-more/recovery-metrics-and-reporting-reference.md): Definitions and formulas for failed payment recovery metrics: recovery rate, baseline, incremental lift, time to recovery, attempts per recovery, outreach funnel.
- [Involuntary churn benchmarks by segment](https://docs.flycode.com/docs/read-more/involuntary-churn-benchmarks-by-segment.md): Involuntary churn benchmarks by order value, payment method, business model and industry, plus recovery rate benchmarks by tool and published FlyCode results.
- [FlyCode pricing model explained](https://docs.flycode.com/docs/read-more/flycode-pricing-model-explained.md): How FlyCode pricing works: a percentage of revenue recovered above your measured baseline, no seats, minimums or setup fees, and a 45-day money-back guarantee.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flycode.com/docs/read-more.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.