> 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/backup-payment-methods.md).

# Backup Payment Methods

FlyCode's backup payment method product: automatically charge another valid card on file when the primary fails, why it is standard practice, the legal terms required, how fallback works, and how reco

When a customer's primary card fails, the fastest recovery with the least friction is to charge another valid payment method the customer already has on file. FlyCode's backup payment method product does this automatically, using the cards your billing platform already stores, with a single toggle and no extra collection flow. This collection covers what the product is, when it applies, what your terms need to say, how it behaves, and how results are reported.

{% hint style="info" %}
**Quick answer:** backup card retries are standard practice at Netflix, Amazon, Microsoft and LinkedIn. FlyCode charges the next valid card on file when the primary fails, without asking the customer or interrupting service, provided your terms of use disclose it. If every card fails, normal retries and outreach take over.
{% endhint %}

## In this section

* [Product Overview](https://help.flycode.com/backup-payment-methods/product-overview): what the product is, its benefits, why it is allowed, and the terms-of-use language you need.
* [Functionality](https://help.flycode.com/backup-payment-methods/functionality): what counts as a backup method, why no manual collection is needed, and what happens if every card fails.
* [Reporting](https://help.flycode.com/backup-payment-methods/reporting): seeing which payments were recovered through a backup card.

## Related

* [Hard Declines & Backup Logic](https://help.flycode.com/ai-payment-recovery/hard-declines-and-backup-logic)
* [Reducing Churn from Failed Payments](https://help.flycode.com/handling-failed-payments/reducing-churn-from-failed-payments)
* [Involuntary churn: the hidden revenue killer](https://docs.flycode.com/docs/involuntary-churn-hidden-revenue-killer)
* [Failed payment recovery glossary](https://docs.flycode.com/docs/read-more/failed-payment-recovery-glossary)


---

# 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://help.flycode.com/backup-payment-methods.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.