> 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/flycode-and-stripe/going-further-with-flycode.md).

# Going Further with FlyCode

What Stripe merchants get beyond recovery: root-cause analytics and anomaly alerts, no-code payment orchestration across additional processors, and outcome-based pricing on incremental recovered reven

Once recovery is running, FlyCode gives Stripe merchants three more things: analytics that explain why payments fail, a way to add other processors without leaving Stripe, and a pricing model tied to results. This page covers each.

## What extra analytics do I get?

FlyCode surfaces root-cause insights, recovery KPIs and anomaly alerts that Stripe's dashboard does not break out. Root-cause views show the distribution of decline codes, the split between soft and hard declines, and how failures cluster by issuer, card type, country and billing date. Recovery KPIs include recovery rate by failure type, recovery speed (days from first failure to success), attempts per recovered invoice, and recovered revenue against your pre-FlyCode baseline. Anomaly alerts flag subscription-status drift, unusual decline spikes from a single issuer or country, and card-testing patterns. Together they answer the questions finance and payments teams ask: what is failing, why, and what is being recovered.

## What if we add other payment processors later?

FlyCode can act as a no-code payment orchestration layer inside Stripe. When a retry keeps failing on your primary processor, FlyCode's Payment Orchestration Agent can route the retry through a secondary PSP (for example a local acquirer for cross-border cards) and sync the result back to the Stripe invoice and subscription, so Stripe remains your system of record. You do not need to migrate off Stripe or run a separate orchestration platform; if you already use one such as Spreedly or Primer, FlyCode adds recovery-specific decisioning on top. See [Payment Orchestration Agent](https://help.flycode.com/payment-orchestration-agent).

## How is FlyCode priced for Stripe users?

Pricing is outcome-based: you pay a percentage of the revenue FlyCode recovers above your current baseline, and nothing on revenue Stripe would have recovered anyway. There is no flat platform fee. Because the fee is a fraction of incremental revenue, ROI is positive by construction; documented customer results range from roughly 6X to 13X. Details and current rates are on [flycode.com/pricing](https://www.flycode.com/pricing). See also [What pricing model does FlyCode use?](https://help.flycode.com/what-is-flycode/getting-started).

## Related

* [What FlyCode Adds to Stripe](https://help.flycode.com/flycode-and-stripe/what-flycode-adds-to-stripe)
* [Failed payment cost recovery ROI](https://docs.flycode.com/docs/failed-payment-cost-recovery-roi)
* [Backup Payment Methods](https://help.flycode.com/backup-payment-methods)


---

# 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/flycode-and-stripe/going-further-with-flycode.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.