Backup payment methods on Stripe for subscription recovery
How to collect and use a backup card on Stripe subscriptions: what Stripe does and does not do, consent language, and how FlyCode's adaptive backup cards work.
By the FlyCode team. Last reviewed September 2026.
Key takeaways
A backup payment method turns a hard decline (closed account, replaced credentials) into a silent recovery with no email, no login and no customer effort.
Stripe stores multiple payment methods on a Customer but subscription invoices charge only
default_payment_method; switching to another card is your job, or FlyCode's.Collect the backup at the moments of highest intent: checkout (optional second card), after a successful recovery, and in the card-update page your dunning emails link to.
Consent language should say plainly that the additional method will be charged if the primary fails; keep the order of methods visible and editable in your customer portal.
Why a second card matters
Most failed-payment recovery is about soft declines, which retries fix. Hard declines are different: the card is closed, replaced, reported lost or stolen, or the account no longer exists. Retrying cannot help, so the usual answer is a dunning email asking for a new card, which recovers 40 to 60 percent at best because it depends on the customer reading, clicking and typing.
If a second valid payment method is already on file, none of that is needed. The charge is moved to the backup, the invoice is paid, and the customer sees only a normal receipt.
What Stripe does and does not do
Store more than one payment method per Customer
Yes (PaymentMethod objects attached to the Customer)
Nothing
Charge a subscription invoice
Uses the subscription's default_payment_method, then the Customer's default
Nothing
Fall back to another stored method when the default fails
No
Detect the failure, pick a backup, pay the open invoice with it
Update credentials for replaced or reissued cards
Yes, via Card Account Updater and network tokens
Nothing, but confirm they are enabled
Collect a second card at checkout
Not by default in Checkout; possible via Elements or a post-purchase step
Your checkout or portal design
How to collect backup payment methods
At checkout, optionally. Add an optional "backup card" step after the primary method is saved. Keep it optional; a required second card lowers conversion.
In the customer portal. Let customers add and order payment methods. Stripe's hosted customer portal allows adding methods; make the backup role explicit in your own UI if you build one.
After a recovery. When a dunning email leads to a new card, keep the old method attached if it is still valid, and ask whether the new one should be primary.
For high-value accounts. For B2B plans, invoice-based fallbacks (bank debit, ACH) work as a backup to a corporate card that hits limits.
Consent language
Card network rules for stored credentials require disclosure of how a stored method will be used. When collecting a backup method, state at the point of collection that it will be charged if the primary payment method fails, that the customer can change or remove it at any time, and where to do so. Example wording: "If your primary payment method fails, we will charge this backup method for the same amount. You can change or remove it in your account settings." Keep the wording next to the form field, not only in the terms.
How FlyCode's adaptive backup cards work
A subscription invoice fails on the primary method and the decline is classified. For hard declines the backup path is taken immediately; for soft declines it is taken once the model judges further retries on the primary unlikely to succeed within the recovery window.
FlyCode selects the next best valid payment method attached to the Customer, taking into account card type, issuer behaviour and past success.
The open invoice is paid with the backup method through Stripe's API, so the invoice, subscription status and receipt stay in sync and the customer sees only a normal payment.
Optionally, the backup becomes the new default so the next renewal does not fail the same way.
The event appears in the FlyCode dashboard as a backup-card recovery, separate from retry and outreach recoveries.
The feature is switched on per account during onboarding; no code is required beyond the standard Stripe app install.
FAQ
Does Stripe automatically charge a backup card when a subscription payment fails?
No. Stripe retries the same default payment method. Falling back to another stored method has to be done by you or by a recovery tool such as FlyCode.
Is charging a backup method allowed under card network rules?
Yes, provided the customer agreed to it when the method was stored and can manage it. Disclose the fallback use at collection time and keep it editable.
Does this replace Card Account Updater?
No. CAU and network tokens fix replaced or reissued credentials on the primary card without any customer involvement and should stay enabled. Backup methods cover the cases CAU cannot: closed accounts, cards without an update available, and persistent declines.
How much does a backup payment method recover?
Across FlyCode accounts, backup card charging recovers roughly 10 to 15 percent of failures that would otherwise require the customer to act.
Related
Backup payment methods in the Help Center
Was this helpful?