> 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/feature-overview.md). # Feature Overview What a payment orchestration agent is, how Stripe payment orchestration works, how FlyCode optimizes it automatically, why retrying through another PSP can succeed, and the pros and cons of running mu Payment orchestration used to require building and maintaining integrations to several processors. Stripe now offers it natively, and FlyCode adds the recovery-specific intelligence that decides when rerouting a failed payment is worth it. This page explains the pieces. ## What is a payment orchestration agent, exactly? It is a decisioning layer that detects failed payments and reroutes them through an alternate payment service provider (PSP), automatically and without developer input. General-purpose orchestration platforms route all transactions by static rules (country, currency, cost). FlyCode's agent is purpose-built for recovery: it looks at a payment that has already failed, predicts whether a different processor is more likely to get it approved given the decline code, issuer, card and geography, and if so retries it there, then reconciles the outcome back to your billing system. ## What is Stripe payment orchestration? Stripe payment orchestration lets you connect additional payment processors to your Stripe account and configure processor selection with rules you create in the Stripe Dashboard. You can route payments based on conditions such as card country, currency, amount and card brand, and view analytics for payment success rates and accepted volume across processors, all without building separate integrations. Stripe remains the single integration point and reporting layer. ## How does FlyCode work with Stripe payment orchestration? FlyCode is one of the first global partners for Stripe payment orchestration. You enable FlyCode's orchestration intelligence directly from Stripe, with no integration work. Instead of relying only on the manual rules you can write in the Dashboard, FlyCode's models decide dynamically, for each failed payment, whether and where to reroute the retry, and they keep learning from the results. Rules cover the cases you can anticipate; the agent covers the ones you cannot. ## Why would retrying a payment through another PSP work better? Because different PSPs have different acquiring relationships with issuing banks, different fraud rules and different approval logic. A charge declined by one processor can be approved by another, most often in cross-border scenarios (a local acquirer in the cardholder's country sees higher approval rates), with certain issuers that treat particular acquirers more favourably, or when a processor's own risk screening was the cause of the decline rather than the bank. ## What are the pros of using payment orchestration? The first is strategic redundancy: if one gateway fails because of an outage, a cyberattack or maintenance, another can take over so transactions continue. Beyond redundancy: global market reach, since each gateway supports different currencies, regions and local payment methods; competitive routing, where the most cost-effective gateway is selected per transaction based on real-time fees; higher approval ratios, because gateways differ in their bank relationships and technology; alignment with consumer preferences and trust in particular payment methods; and risk and compliance diversification across regional regimes such as GDPR and CCPA. ## What are the cons of using payment orchestration? Management overhead, because each gateway has to be configured, monitored and kept working with the others. Cost, since each gateway can carry its own setup, monthly and transaction fees. Integration effort, although with Stripe orchestration the integrations no longer have to be built. And customer experience risk, if differences in payment interface, processing time or available methods between gateways make checkout inconsistent. FlyCode's agent addresses the first and last of these by making the routing decision automatically and only on failed payments, so the customer-facing flow does not change. ## Related * [Platform Fit & Performance](https://help.flycode.com/payment-orchestration-agent/platform-fit-and-performance) * [Monitoring & Reporting](https://help.flycode.com/payment-orchestration-agent/monitoring-and-reporting) --- # 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/feature-overview.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.