# Help Center ## Help Center - [Help Center](https://help.flycode.com/help-center.md): Welcome to the FlyCode Help Center. We've gathered the most frequently asked questions to help you navigate setup, usage, and everything in between. - [What is FlyCode](https://help.flycode.com/what-is-flycode.md): FlyCode is the revenue performance platform for payments: an AI-native failed payment recovery layer for Stripe, Shopify, Braintree and PayPal subscription businesses. What it does, how it differs, ho - [What Makes FlyCode Different](https://help.flycode.com/what-is-flycode/what-makes-flycode-different.md): How FlyCode differs from legacy dunning tools and fixed retry schedules: AI-native per-merchant models, retries separated from emails, alternative payment routing, and network data from Visa, Masterca - [Getting Started](https://help.flycode.com/what-is-flycode/getting-started.md): Getting started with FlyCode: outcome-based pricing with no seats or minimums, launch in hours via the Stripe or Shopify apps or API keys, and how FlyCode runs alongside your billing workflows without - [Results & ROI](https://help.flycode.com/what-is-flycode/results-and-roi.md): What ROI to expect from FlyCode: a 16 to 25 percentage point lift in failed payment recovery rate and a 5 to 9 percent ARR increase, with documented results from SaaS and eCommerce customers. - [Understanding Involuntary Churn](https://help.flycode.com/understanding-involuntary-churn.md): What involuntary churn is, how it differs from voluntary churn, why failed payments cause it, what it costs subscription businesses beyond lost revenue, and how FlyCode prevents it without changing yo - [What Is Involuntary Churn?](https://help.flycode.com/understanding-involuntary-churn/what-is-involuntary-churn.md): Involuntary churn defined: customers lost to failed payments rather than a decision to cancel. How it differs from voluntary and passive churn, and why it accounts for 20 to 40 percent of subscription - [Causes & Risks](https://help.flycode.com/understanding-involuntary-churn/causes-and-risks.md): Why subscription payments fail (insufficient funds, generic bank declines, incorrect details, gateway errors), what hard declines mean for automatic retries, and what failed-payment churn costs beyond - [FlyCode's Approach to Churn](https://help.flycode.com/understanding-involuntary-churn/flycodes-approach-to-churn.md): How FlyCode reduces involuntary churn: AI-optimized retry timing, backup cards, credential updates, coordinated email and SMS, root-cause analytics, and the best practices merchants should keep alongs - [Integration Considerations](https://help.flycode.com/understanding-involuntary-churn/integration-considerations.md): 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. - [Handling Failed Payments](https://help.flycode.com/handling-failed-payments.md): How FlyCode handles failed subscription payments: machine-learning retry timing, backup cards and orchestration beyond simple retries, the three-front approach to involuntary churn, and how recovery e - [When and How Payments Are Retried](https://help.flycode.com/handling-failed-payments/when-and-how-payments-are-retried.md): How FlyCode decides when to retry a failed payment using per-merchant machine learning, what it does beyond retries (backup cards, anomaly detection, dunning orchestration, analytics), and how it opti - [Reducing Churn from Failed Payments](https://help.flycode.com/handling-failed-payments/reducing-churn-from-failed-payments.md): How to solve involuntary churn from failed payments: AI-optimized retries, alternate card on file routing, and predictive dunning that reaches customers before the subscription lapses. - [Coordinating Messaging with Recovery](https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery.md): How FlyCode coordinates recovery emails with retries: templates and models for failed-payment outreach, how this compares with Stripe's default emails, and whether to show customers the raw decline co - [Decline Codes Explained](https://help.flycode.com/decline-codes-explained.md): What payment decline codes are, how to tell soft declines from hard declines, what the most common Stripe codes mean, and how FlyCode uses each code to recover more failed subscription payments. - [What Decline Codes Tell You](https://help.flycode.com/decline-codes-explained/what-decline-codes-tell-you.md): Decline codes are the issuing bank's reason for refusing a charge. Learn what they are, why they matter for subscription revenue, the difference between soft and hard declines, and how decline pattern - [Where to Find Decline Codes (and How to Use Them)](https://help.flycode.com/decline-codes-explained/where-to-find-decline-codes-and-how-to-use-them.md): Where decline codes appear in the Stripe Dashboard, API and webhooks and in FlyCode, whether codes are the same across processors, and which Stripe test cards trigger specific declines. - [How to Handle the Most Common Declines](https://help.flycode.com/decline-codes-explained/how-to-handle-the-most-common-declines.md): insufficient\_funds is the largest decline category in subscription billing, 50 to 70 percent of all failures. What it means, why it dominates, when to retry, and how much more FlyCode recovers on it, - [What to Do When You See These Other Codes](https://help.flycode.com/decline-codes-explained/what-to-do-when-you-see-these-other-codes.md): What generic\_decline, do\_not\_honor, transaction\_not\_allowed and invalid\_account mean in Stripe, whether each should be retried, and what to tell the customer. - [How FlyCode Makes Decline Codes Work for You](https://help.flycode.com/decline-codes-explained/how-flycode-makes-decline-codes-work-for-you.md): How FlyCode ingests decline codes from Stripe and the card networks, classifies soft versus hard declines, applies issuer-specific retry timing and coordinates outreach, without touching your existing - [FlyCode & Stripe](https://help.flycode.com/flycode-and-stripe.md): How FlyCode works with Stripe Billing: installing the Stripe app, what FlyCode adds on top of Smart Retries, expected ARR uplift, analytics, multi-processor routing and outcome-based pricing. - [Connecting FlyCode to Stripe](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe.md): How the FlyCode Stripe app connects to your account, why no engineering time is needed, and how it coexists with your existing Stripe webhooks, Radar rules and other apps. - [What FlyCode Adds to Stripe](https://help.flycode.com/flycode-and-stripe/what-flycode-adds-to-stripe.md): Why add FlyCode if you already use Stripe Smart Retries: higher recovery, adaptive per-merchant retries beyond Stripe's 8-attempt cap, coordinated emails, 5 to 9 percent ARR lift, and subscription ano - [Going Further with FlyCode](https://help.flycode.com/flycode-and-stripe/going-further-with-flycode.md): 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 - [FlyCode vs. ProfitWell (Paddle Retain)](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain.md): FlyCode vs ProfitWell Retain (Paddle Retain) for failed payment recovery: recovery performance, retry engine and email differences, how each works with Stripe, and what you keep if you switch. - [Recovery Performance](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/recovery-performance.md): How much better FlyCode recovers failed payments than ProfitWell Retain (25 to 40 percent more on average) and the extra ARR lift to expect beyond your current baseline (around 8 percent). - [What's Different Behind the Scenes](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/whats-different-behind-the-scenes.md): Why FlyCode's per-merchant AI retry engine outperforms ProfitWell Retain's fixed-interval schedule, and how FlyCode coordinates customer emails with the retry cycle instead of emailing after every att - [Platform Fit & Compatibility](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/platform-fit-and-compatibility.md): How FlyCode and ProfitWell Retain each work with Stripe (replacing versus stacking on Smart Retries), and how the two platforms' technology compares. - [What You Keep (and Gain) If You Switch](https://help.flycode.com/flycode-vs.-profitwell-paddle-retain/what-you-keep-and-gain-if-you-switch.md): Switching from ProfitWell Retain to FlyCode: keep Retain's cancellation flows, add FlyCode for payment recovery with a one-click Stripe app install, and what you gain. - [FlyCode & Shopify](https://help.flycode.com/flycode-and-shopify.md): Using FlyCode with Shopify subscriptions: compatibility with Recharge, Skio, Stay AI and other subscription apps, how to connect your store in minutes without a developer, and the support Shopify merc - [Compatibility & App Support](https://help.flycode.com/flycode-and-shopify/compatibility-and-app-support.md): How FlyCode works with Shopify subscriptions and which subscription apps it supports (Recharge, Skio, Stay AI and others), using it alongside existing Recharge or Skio dunning flows, and the support S - [Setup & Requirements](https://help.flycode.com/flycode-and-shopify/setup-and-requirements.md): Connecting FlyCode to a Shopify store: nothing to change in Shopify, a few-minute login-and-approve setup, and no developer required. - [AI Payment Recovery](https://help.flycode.com/ai-payment-recovery.md): How FlyCode's AI payment recovery works: which decline codes are treated as hard declines, what happens to them, backup payment methods, credential updates, and how recovery emails are timed and deliv - [Hard Declines & Backup Logic](https://help.flycode.com/ai-payment-recovery/hard-declines-and-backup-logic.md): Which Stripe decline codes FlyCode treats as hard declines, what it does with them (faster, action-specific outreach and backup card charging), automatic updates for replaced cards, and backup payment - [Email Behavior & Deliverability](https://help.flycode.com/ai-payment-recovery/email-behavior-and-deliverability.md): When FlyCode emails customers about failed payments (not after every attempt, and never immediately after a soft decline) and how it keeps deliverability high with transactional infrastructure, SPF an - [Failed Payment Outreach](https://help.flycode.com/failed-payment-outreach.md): How FlyCode's failed payment outreach works: your brand and domain, dynamic templates by decline reason, local-time delivery, compliant sending, and coordination with retries and your existing email t - [Messaging Customization](https://help.flycode.com/failed-payment-outreach/messaging-customization.md): Customizing FlyCode recovery emails: send from your own domain with your branding, and adapt tone, call to action and structure by decline reason, customer segment and retry status. - [Delivery Strategy](https://help.flycode.com/failed-payment-outreach/delivery-strategy.md): FlyCode's recovery email delivery strategy: local-time sending, faster action-specific cadences for hard declines, CAN-SPAM and GDPR compliance, how it differs from Stripe and ProfitWell emails, and 9 - [System Integration](https://help.flycode.com/failed-payment-outreach/system-integration.md): FlyCode outreach coexists with your current email platform and subscription tooling: it coordinates sends with retries to avoid collisions and does not duplicate or overwrite existing dunning flows un - [Backup Payment Methods](https://help.flycode.com/backup-payment-methods.md): FlyCode's backup payment method product: automatically charge another valid card on file when the primary fails, why it is standard practice, the legal terms required, how fallback works, and how reco - [Product Overview](https://help.flycode.com/backup-payment-methods/product-overview.md): What FlyCode's backup payment method product is, its benefits (higher and faster recovery, less involuntary churn, no integration), why it is allowed and standard practice, and the terms-of-use langua - [Functionality](https://help.flycode.com/backup-payment-methods/functionality.md): How backup card retries work in practice: what counts as a backup method, why no manual collection is needed, the fallback order, and what happens when every card on file fails. - [Reporting](https://help.flycode.com/backup-payment-methods/reporting.md): Reporting on backup payment method recovery: see which payments were recovered through a backup card, fallback success rates, recovery paths and ARR saved. - [Payment Orchestration Agent](https://help.flycode.com/payment-orchestration-agent.md): FlyCode's Payment Orchestration Agent: a decisioning layer that reroutes failed payments through an alternate processor inside Stripe payment orchestration, with no integration, plus pros, cons, platf - [Feature Overview](https://help.flycode.com/payment-orchestration-agent/feature-overview.md): What a payment orchestration agent is, how Stripe payment orchestration works, how FlyCode optimizes it automatically, why retrying through another PSP can succeed, and the pros and cons of running mu - [Platform Fit & Performance](https://help.flycode.com/payment-orchestration-agent/platform-fit-and-performance.md): 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 - [Monitoring & Reporting](https://help.flycode.com/payment-orchestration-agent/monitoring-and-reporting.md): How to monitor payment processor performance inside the Stripe Dashboard after enabling payment orchestration: success rates by processor, currency, card brand and country, and recovery impact. - [Subscription Compliance](https://help.flycode.com/subscription-compliance.md): Subscription compliance for recurring billing: the FTC Click-to-Cancel rule and its status, ROSCA and state auto-renewal laws, dark patterns, a quick cancellation-flow test, consent records and monito - [Regulatory Rules](https://help.flycode.com/subscription-compliance/regulatory-rules.md): What the FTC Click-to-Cancel rule required and its current status, whether it applies to existing subscriptions, what counts as a dark pattern in cancellation flows, and a fast test for whether your c - [Legal & Tracking Requirements](https://help.flycode.com/subscription-compliance/legal-and-tracking-requirements.md): What billing consent records to store (timestamp, IP, exact opt-in language) and how to monitor whether customers hit friction in your cancellation flow by comparing attempts with completions. --- # 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 This site has an agentic ask interface you may use to query the documentation dynamically 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/index.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.