> 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/platform-fit-and-performance.md). # Platform Fit & Performance Platform fit for FlyCode's orchestration agent: keep your current PSPs, use it alongside Spreedly or Primer, no impact on processing speed or customer experience, and support for subscriptions and hig Already running several processors, or an orchestration platform such as Spreedly or Primer? FlyCode enhances that setup with recovery-focused intelligence rather than replacing it. ## Do I need to switch to a new PSP to use FlyCode's orchestration? No. You keep your current PSPs; FlyCode works with whatever infrastructure you have. You can add alternate PSPs as fallbacks through Stripe payment orchestration, or let FlyCode manage the routing logic across processors you already use. Nothing about your primary processing changes. ## We already use a tool like Spreedly or Primer. Do we need this? If you already use an orchestration platform, FlyCode does not replace it; it enhances it. General orchestration platforms optimize routing for every transaction based on cost, region and availability. FlyCode's models layer on top and optimize specifically for recovery of failed payments, deciding whether and where a declined charge should be retried. Think of it as recovery-specific orchestration intelligence that you do not have to build or tune yourself. ## Will this delay payment processing or impact my UX? No. The routing decision is made instantly, and recovery attempts happen behind the scenes on payments that have already failed. Customers do not see a different checkout, a slower authorization or an extra step; they will not notice anything unless you send them receipts for the recovered charge. ## Is this just for recurring subscriptions, or one-time payments too? FlyCode's orchestration agent is designed primarily for subscription businesses, where a recovered renewal preserves the whole remaining customer lifetime. It can also be applied to high-value or repeat one-time transactions where recovery matters, such as large orders or invoices paid by card. ## Related * [Feature Overview](https://help.flycode.com/payment-orchestration-agent/feature-overview) * [Integration Considerations](https://help.flycode.com/understanding-involuntary-churn/integration-considerations) --- # 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/platform-fit-and-performance.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.