> 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.md).

# Payment Orchestration Agent

FlyCode's Payment Orchestration Agent: a decisioning layer that reroutes failed payments through an alternate processor inside Stripe payment orchestration, with no integration, plus pros, cons, platf

Some failed payments are declined by one processor and approved by another. FlyCode's Payment Orchestration Agent detects those cases and reroutes the retry through an alternate payment service provider, automatically and without developer input, while keeping Stripe as the system of record. FlyCode is one of the first global partners for Stripe payment orchestration, so the agent can be enabled directly from Stripe. This collection covers what orchestration is, how FlyCode adds recovery intelligence on top, where it fits, and how to monitor it.

{% hint style="info" %}
**Quick answer:** you keep your current processors. FlyCode decides, per failed payment, whether retrying through a different processor is more likely to succeed (common for cross-border cards and certain issuers), executes the retry, and syncs the result back to Stripe. Routing decisions are instant and invisible to the customer.
{% endhint %}

## In this section

* [Feature Overview](https://help.flycode.com/payment-orchestration-agent/feature-overview): what an orchestration agent is, how Stripe payment orchestration works, why another PSP can approve, and the pros and cons.
* [Platform Fit & Performance](https://help.flycode.com/payment-orchestration-agent/platform-fit-and-performance): keeping your PSPs, using it with Spreedly or Primer, no UX impact, and one-time payments.
* [Monitoring & Reporting](https://help.flycode.com/payment-orchestration-agent/monitoring-and-reporting): monitoring processor performance inside Stripe.

## Related

* [What if we add other payment processors later?](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode)
* [Stripe integration guide for FlyCode](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode)
* [Payment recovery platforms compared 2026](https://docs.flycode.com/docs/read-more/payment-recovery-platforms-compared-2026)
* [FlyCode Agents on flycode.com](https://www.flycode.com/)


---

# 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.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.