> 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/understanding-involuntary-churn/integration-considerations.md).

# Integration Considerations

You do not need to rebuild or replace your billing stack to use FlyCode. It connects natively to Stripe, Shopify subscription apps, Braintree and PayPal and works alongside your existing workflows.

FlyCode is designed to add recovery on top of the billing tools you already run, not to replace them. This page covers the one question every buyer asks before the technical evaluation.

## Do I need to rebuild my billing stack to use FlyCode?

No. FlyCode integrates natively with Stripe as a verified Stripe app, with Shopify subscriptions through Recharge, Skio and Stay AI, and with Braintree and PayPal through a scoped API user. Your processor, subscription platform, invoicing, tax, accounting and email tools stay exactly as they are. FlyCode listens to failed-payment events, decides how to recover each one, and executes the retry or fallback through your processor's own API, so results appear in the system you already use as the source of truth.

There is no data migration, no checkout change and no code to deploy. Setup is an app install (Stripe, Shopify apps) or creating a restricted role and API user (Braintree and PayPal), plus choosing your retry and messaging preferences. The [Stripe integration guide](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode), [Recharge guide](https://docs.flycode.com/docs/integrations/step-by-step-integrate-flycode-with-recharge), [Skio guide](https://docs.flycode.com/docs/integrations/how-to-install-flycode-on-skio) and [Braintree and PayPal guide](https://docs.flycode.com/docs/integrations/how-to-connect-flycode-to-your-braintree-paypal-account) cover each path step by step.

## Will FlyCode conflict with dunning I already run?

It should not run in parallel with another retry engine on the same invoices. At go-live you turn off or align the native retry schedule and dunning emails in Stripe, Recharge or Skio so that FlyCode owns retries and (optionally) messaging. Cancellation flows, offers and other retention tooling are unaffected and continue to work. See [Can I use FlyCode if I already have dunning flows set up in Recharge or Skio?](https://help.flycode.com/flycode-and-shopify/compatibility-and-app-support)

## Related

* [Supported payment and subscription platforms](https://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms)
* [Connecting FlyCode to Stripe](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe)
* [FlyCode & Shopify](https://help.flycode.com/flycode-and-shopify)


---

# 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/understanding-involuntary-churn/integration-considerations.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.