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, Recharge guide, Skio guide and Braintree and PayPal guide 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?
Related
Last updated
Was this helpful?