Payment Processing
· 6 minutes
How to Add a Backup Payment Processor Without Leaving Stripe
Learn how to add a second payment processor alongside Stripe, what happens to recurring subscriptions, and how payment failover actually works.
Redux Team
You can add a backup payment processor without leaving Stripe. Keep Stripe as your main processor, get approved by a second provider, and decide which payments it handles. The important catch: a second merchant account isn't the same as automatic failover. Your existing subscribers' cards are stored at Stripe. A new processor can only charge them if that card data is shared securely and your billing system knows when to use it.
This guide covers what a backup processor really gives you, three ways to set one up, and what it takes to make recurring payments work across both. Last reviewed against Stripe's documentation on November 1, 2026.
Why businesses add backup payment processing
Account risk. A restriction, reserve or closure on your only account stops every renewal at once. If that's already happened, read what to do when Stripe is holding your funds.
Outages. Any provider can have downtime. A second route keeps checkout open.
Coverage and approval rates. Different providers perform differently by country and card type.
Leverage. A tested alternative gives you options when terms change.
What a backup payment processor actually means
The phrase covers very different setups. Be clear which one you're building:
Level | What you have | What it protects |
|---|---|---|
1. Second account | An approved merchant account with another provider | New customers, if you can switch checkout over |
2. Live split | Some new payments already running through the second provider | New revenue, with a tested path |
3. Shared card access | Saved cards usable at both providers through a vault | Existing subscribers, too |
Most businesses start at level 1 or 2. Level 3 is where real portability for existing subscriptions comes from, and it's the hardest to build.
Can you keep Stripe and use a second provider?
Yes. Stripe even documents ways to do it. Its guide to managing multiple payment providers describes reliability, coverage and cost as common reasons, and names Stripe products that can work with other processors. Just plan for the cost: Stripe's guide estimates 6 to 18 months of dedicated engineering for a custom multiprocessor integration, plus ongoing work on reconciliation, support and contracts.
Three architectures for a backup processor
1. Split new payment traffic between processors
Route a share of new checkouts, or certain countries or card types, to the second provider. Each customer's card is saved where they first paid. It's the simplest way to keep both relationships active and tested. It doesn't help customers whose cards live only at Stripe.
2. Keep existing subscriptions on Stripe, send new customers elsewhere
Existing subscribers keep renewing on Stripe. New sign-ups go to the second provider. Over time your revenue spreads across both. You'll run two billing flows, or connect the second processor to your billing system. If you use Stripe Billing, see using Stripe Billing with another payment processor.
3. Use an independent vault and routing layer
Store cards in a vault that isn't tied to one processor, then route each charge to whichever provider you choose. Stripe explains the difference: orchestration decides which processor handles a payment, while a vault stores the card for reuse (source). Options include Stripe's Vault and Forward API, which forwards card details from Stripe's vault to supported endpoints such as Adyen, Braintree, Checkout.com and Worldpay, as well as third-party vaults. This is the most flexible setup and the most work to run.
Step by step: adding a second processor
Assess your needs and risk profile. Volume, markets, payment methods, refund and dispute rates, and what you're protecting against.
Choose a provider or acquiring relationship. Check they support your category, countries and recurring billing.
Complete underwriting. Expect to share business details, processing history and policies. Approval isn't guaranteed.
Decide on card portability. New cards only, forwarding from a vault, or a one-time export. Each has different requirements.
Connect checkout and recurring billing. Make sure renewals know which processor and which stored credential to use.
Test the full lifecycle. Charges, declines, retries, refunds, disputes, card updates, cancellations and switching traffic between providers.
Can existing Stripe customers be charged by another provider?
Sometimes, but not by default. A few concepts decide it:
Card vaulting. Stripe stores your customers' card numbers. Other providers can't see them.
Payment method migration. Stripe will transfer card data to another PCI DSS Level 1 compliant processor through an encrypted export. It doesn't export subscriptions, payment history or other objects, and cards saved through Link are excluded (source).
Forwarding. With Vault and Forward, cards stay in Stripe's vault and Stripe sends the details to the other processor when you make a charge. Access needs approval from Stripe, and refunds and disputes for those payments are handled with the other processor (source).
Network tokens. These stand in for the card number and update when a card is reissued (source). Ask how each provider handles them, because support varies.
Subscription state. Billing dates, trials, discounts and retry status live in your billing system. They must stay in sync wherever the charge happens.
Customer authorization. Recurring charges depend on what the customer agreed to. Review your terms before changing where charges come from or what appears on statements.
What Stripe Orchestration offers today
Stripe's Orchestration lets you set rules that route payments across processors, retry failed payments on a different processor, and compare performance. It works with Payments, Billing and Dashboard payments. Key facts as of this review:
Availability: private preview. You request access from Stripe.
Processors: Stripe's feature table lists Adyen, Braintree and Worldpay WPG.
Not supported: non-card payments, Link, Capital, Connect, Terminal and Organizations. Disputes and settlement activity are managed in the other processor's dashboard.
Liability: the third-party processor remains the processor for payments routed to it, and its fees and terms apply.
If you can get access, it removes a lot of custom work. Check the current docs, because preview features change.
Costs, maintenance and operational complexity
Fees: a second provider has its own pricing, and some charge minimums or setup costs.
Engineering: integration, routing logic, webhooks and ongoing updates as each provider's API changes.
Finance: reconciling payouts and fees from two providers.
Support: your team needs to know where to look for a customer's payment, refund or dispute.
Compliance: handling raw card data yourself increases your PCI scope. Vaults and forwarding services exist partly to avoid that.
When a backup processor is worth the effort
It's usually worth it if losing your processor for a week would seriously hurt the business, if you sell in markets where another provider performs better, or if your model sits near the edge of your current provider's risk appetite. It's usually not worth it yet if you're small, in one market and growing on a clean Stripe account. In that case, focus on keeping disputes low and understanding your terms.
Frequently asked questions
Can I keep Stripe and add a second payment processor?
Yes. Nothing stops you holding accounts with more than one provider, as long as each one approves your business. The work is in routing payments between them and making sure recurring charges can still be collected.
Does a backup processor mean automatic failover?
No. A second merchant account only gives you somewhere else to send payments. Automatic failover for existing subscriptions also needs the card data to be usable at both providers, plus logic that decides when to switch. Stripe's Orchestration can retry failed payments on another processor, but it's in private preview.
Can a new processor charge customers whose cards are saved at Stripe?
Only if the card data reaches them securely. Two documented routes are Stripe's Vault and Forward API, which sends card details from Stripe's vault to supported processors, and a one-time PCI-compliant data export. Both need Stripe's involvement and approval.
How much does a backup processor cost?
It depends on the provider, your volume and your risk profile, so we won't quote numbers. Budget for engineering time as well as fees. Stripe's own guide estimates a custom multiprocessor integration can take 6 to 18 months (source), though a simple fallback for new customers is much smaller.
Discuss your backup processing options
Redux helps subscription businesses work out whether a backup processor is worth it and which setup fits their stack. We don't operate a vault or routing layer, and we can't guarantee any provider's approval. We can help you plan the project and avoid the common gaps.
Discuss your backup processing options
Still comparing providers? Read Stripe alternatives for subscription businesses.
