> 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/payment-orchestration-agent/monitoring-and-reporting.md). # Monitoring & Reporting How to monitor payment processor performance inside the Stripe Dashboard after enabling payment orchestration: success rates by processor, currency, card brand and country, and recovery impact. Orchestration results are visible where your payments team already works: the Stripe Dashboard, alongside FlyCode's own recovery reporting. ## How do I monitor processor performance inside Stripe? After enabling payment orchestration in Stripe for live payments, use the Dashboard to monitor each processor. The Orchestration overview page shows performance analytics and payment success rates across your processors, and you can filter by currency, card brand, card country, card type or transaction type to see where one processor outperforms another. The Payments analytics page shows your overall payment success rate and where payments fail; use the processor filter to view only the payments routed through a specific processor. FlyCode's reporting adds the recovery view: which failed payments were rerouted, to which processor, how many were approved on the second attempt, and the revenue recovered as a result. ## Related * [What extra analytics do I get?](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode) * [Feature Overview](https://help.flycode.com/payment-orchestration-agent/feature-overview) --- # 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/payment-orchestration-agent/monitoring-and-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.