> For the complete documentation index, see [llms.txt](https://docs.flycode.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms.md). # Supported payment and subscription platforms Platforms FlyCode connects to: Stripe, Braintree, PayPal, Adyen, Checkout.com, Chargebee, Recurly, and Shopify via Recharge, Skio, Stay AI and Loop, with status. FlyCode sits on top of the subscription management and payment stack you already run and recovers failed payments from there. There is nothing to replace: FlyCode reads failed-payment events from your platform, decides how to recover each one, and executes the retry through your processor. The full, current list is on [flycode.com/connections](https://www.flycode.com/connections); the table below shows how each connection type works and where the setup guide lives. ## Payment processors | Processor | How FlyCode connects | Setup guide | | ----------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | Stripe (Stripe Billing) | Verified app on the Stripe App Marketplace; one-click install, retries via Stripe API | [Stripe integration guide](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode) | | Braintree | Restricted API user and role in the Braintree Control Panel | [Braintree/PayPal guide](https://docs.flycode.com/docs/integrations/how-to-connect-flycode-to-your-braintree-paypal-account) | | PayPal | Via Braintree vaulted PayPal payment methods | [Braintree/PayPal guide](https://docs.flycode.com/docs/integrations/how-to-connect-flycode-to-your-braintree-paypal-account) | | Adyen | API connection scoped to recurring payments | Contact FlyCode for setup | | Checkout.com | API connection scoped to recurring payments | Contact FlyCode for setup | | Shop Pay | Through Shopify subscription apps | See Shopify below | ## Subscription management platforms | Platform | How FlyCode connects | Setup guide | | ------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | Recharge (Shopify) | App in the Recharge App Marketplace plus three payment settings | [Recharge guide](https://docs.flycode.com/docs/integrations/step-by-step-integrate-flycode-with-recharge) | | Skio (Shopify) | Shopify collaborator access; FlyCode activates in Skio's marketplace | [Skio guide](https://docs.flycode.com/docs/integrations/how-to-install-flycode-on-skio) | | Stay AI (Shopify) | Native integration | Contact FlyCode for setup | | Chargebee | API connection to Chargebee and the underlying gateway | Contact FlyCode for setup | | Recurly | API connection | Contact FlyCode for setup | | FastSpring | API connection | Contact FlyCode for setup | ## eCommerce platforms Shopify (through Recharge, Skio and Stay AI), BigCommerce, Magento / Adobe Commerce, WooCommerce and Wix subscription stores connect through their payment processor or subscription app. Shopify merchants should start with the [FlyCode & Shopify](https://help.flycode.com/flycode-and-shopify) help centre section. ## What FlyCode needs from any platform Regardless of platform, the integration needs three things: real-time notification of failed and successful charges (webhooks or polling), read access to the customer's stored payment methods and subscription state, and the ability to trigger a retry and update the subscription or invoice status. Every supported connection provides these without changes to your checkout, and FlyCode never moves funds; recovered payments settle to your processor account as usual.

FlyCode connections

Have a custom billing build or need help with technical discovery? [Reach out to us](https://www.flycode.com/get-started). ## Related * [How FlyCode handles Shopify subscription failed payments](https://docs.flycode.com/docs/integrations/how-flycode-handles-shopify-subscription-failed-payments) * [Integration Considerations](https://help.flycode.com/understanding-involuntary-churn/integration-considerations) in the Help Center --- # 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://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms.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.