> 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/reporting.md). # Reporting Reporting on backup payment method recovery: see which payments were recovered through a backup card, fallback success rates, recovery paths and ARR saved. Backup recovery is tracked separately so you can see exactly what it contributes. ## Can I see which payments were recovered through a backup card? Yes. FlyCode logs the payment method used for every recovered transaction, so reporting shows which invoices were recovered on the primary card, which on a backup, and at what step in the sequence. From that you can view backup success rates, fallback behaviour (how often a backup was attempted and how often it succeeded), the recovery path for any individual invoice, and how much ARR was saved through backup methods specifically. The same data appears in your processor: for Stripe, the successful charge is on the invoice with the payment method that was used, so finance can reconcile it in the usual way. ## Related * [What extra analytics do I get?](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode) * [Results & ROI](https://help.flycode.com/what-is-flycode/results-and-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 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/reporting.md?ask=&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.