| The short answer
– Does a $200K to $1M+ store need payment orchestration? – What is payment orchestration? Software that sits between your checkout and several payment processors. If one processor declines a payment or doesn’t respond, it sends the same payment to another, so the order still goes through. It’s built for merchants who already run several processors. – What should you set up first? A tested plan for switching checkout when your processor fails, plus a backup card account that’s already approved. Keep it in light use, with a few test payments each month, or it may not hold up when it suddenly has to take all your orders. – When does a second processor pay off? When your revenue per hour is high, your sales peak sharply, your processor has a history of incidents, or a payout freeze would stop your business. – What can you skip for now? Live routing across many processors. Published prices start at $750 a month for one vendor’s card storage alone. |
Your store does somewhere between $200K and $1M+ a year, and nearly all of it runs through one payment processor. Last month, card payments failed for part of a sale day. Customers emailed you before your processor’s status page said anything.
A week later, a vendor shows you a payment orchestration demo. Several processors, automatic routing, “no more failed payments.” The price isn’t on the website.
So do you need it, or do you need something simpler?
Our answer is that orchestration solves the wrong problem for most stores your size. It’s built to win back a small share of declined payments across millions of transactions and many processors. Your bigger risk is blunter: a processor pausing your account, which stops every card payment at once and can hold your money for months.
Of the 40 WooCommerce stores we manage, 90%+ configure and rely on a single payment gateway. E.g. between Stripe and PayPal they would keep only Stripe because it offers the best conversion rates. The ones which have set up more gateways require them to service multiple geographies where no single gateway services all necessary geographies.
But we had a payment processor block our client for selling CBD for dogs on a subsite, though this is completely legal and the gateway advertises their willingness to work with even weed businesses.
There are many reasons a payment gateway can stop working for your website, they can be accidental or deliberate, but the only business prepared to handle this is an one who has faced this issue before.
The moral of the story is, setting up a second payment processor de-escalates a business critical revenue threatening situation into an urgent but non critical situation.
We can just turn on the second payment processor and instantly be back in business.
It can even programmatically be toggled based on payment success rate of the primary payment gateway. That only works if the backup has been in recent use. A gateway that has sat switched off for months may not hold up when it suddenly takes your full payment volume, so it needs a few test transactions every month.
Let’s look at why. We’ll explain what payment orchestration does, then introduce a simple way to size your backup, which we call the Payment Backup Ladder, and give you a plan for the day your processor goes down.
Payment orchestration is a layer between your store and several payment processors that decides where each payment goes, and where to retry it if one processor fails. Large merchants use it to manage many processors across many countries.
Our team at WisdmLabs has looked after business-critical WordPress and WooCommerce sites for 14+ years and has completed 300+ subscription migrations, including moving saved cards between payment gateways.
Two checkout incidents we handled
1. The CBD store blocked by its payment processor
Coming back to the CBD store we mentioned earlier, the one blocked by its payment processor: CBD was a small part of the entire website. Here is how we handled it:
- We moved the CBD products to another website.
- We requested our payment processor to verify and re-activate the main website.
- For the new CBD-specific website, we took on a newer payment gateway, as the current one refused to work with us for CBD.
2. A PHP upgrade, YITH Memberships, and a PayPal gateway that wasn’t working
We had another issue recently where we had to upgrade PHP and hence YITH Memberships, but there wasn’t any PayPal payment gateway that was working. We had to switch immediately to Stripe, and it caused a 2 day downtime while we tested everything for regular products. We also had to push subscription renewals by a week.
The plan below comes from that work.
One honest note: we sell website management, and a payment backup plan is part of it. We don’t sell or resell any orchestration platform. Every claim below links to its source, so you can check it yourself.
Our view: most stores this size don’t need an orchestration platform yet. They need a written plan for when the processor fails, and a backup account that’s approved before the day they need it. That account also needs a few test payments each month to stay ready. A live second card processor becomes essential at a certain point, and the sections below show how to tell when you’ve reached it.
We’ll also look ahead, because processors are starting to build orchestration in, and that changes less for stores your size than the announcements suggest.
First, it helps to see exactly what an orchestration platform does at checkout, and what WooCommerce can already do without one.
What payment orchestration is, in plain words
| In short
What does a payment orchestration platform actually do? – Who uses it? Mostly large merchants with several processors in several countries. – Can WooCommerce do this on its own? It can show several payment options, but it doesn’t switch between them automatically. – Is there a WooCommerce plugin for it? We found no widely used one. |
Orchestration solves a multi-processor problem. If you have one processor, you don’t have that problem yet.
Stripe describes payment orchestration as “the process of centralizing payment gateways, processors, acquirers, and other financial service providers in a single platform” (Stripe, updated 13-09-2024) [Recheck: over two years old].
Glenbrook Partners, a payments consultancy that doesn’t sell orchestration, puts it more simply: “Orchestration Platforms facilitate a merchant’s multi-acquirer setup” (Glenbrook, 02-02-2024). [Recheck: over two years old]
Here’s how it plays out at checkout. A customer pays $120 by card. The platform sends the payment to processor A. Processor A declines it or doesn’t respond, so the platform sends the same payment to processor B, and the order goes through. With the right setup, the customer never sees the first attempt fail.
A platform can also route by rule. For example, it might send UK cards to a processor with lower UK fees and US cards to another. That kind of rule only saves money if you sell in several countries at volume.
What WooCommerce already does
WooCommerce lets you run several payment gateways at once. In WooCommerce > Settings > Payments, you choose “Enable to turn on an available provider” and “Use the drag handle at the left of a provider to change the order” (WooCommerce docs, updated 05-09-2026). That’s how most stores show a PayPal button next to a card form.
However, WooCommerce doesn’t move a failed payment from one gateway to another. If your card processor is down, the card form fails, and the customer has to pick another option themselves.
We looked for a plugin that adds automatic failover. The few that claim it have fewer than 100 active installs on WordPress.org, so we can’t recommend them. On WooCommerce, failover is a manual switch or a custom build.
| Section recap
The takeaway: Orchestration routes and retries payments across several processors. WooCommerce shows several payment options but doesn’t switch between them for you. – Your next step: Open WooCommerce > Settings > Payments and write down every gateway you have enabled, and which company processes each one. – Why it matters: Two gateways run by the same company, such as WooPayments and the Stripe plugin (both run on Stripe), fail together. – What the result tells you: If every option runs through one company, you have no backup yet. The next section shows which level of backup fits you. |
That list tells you where you stand today. Next, it helps to split “a second processor” into three levels, the Payment Backup Ladder, because each costs very different amounts and protects you from different things.
The Payment Backup Ladder: three levels of protection
| In short
What does “a second processor” actually mean for a store your size? – Level 1: a second payment method, such as PayPal next to your card form. – Level 2: a verified backup card account, set up but switched off. It still needs a few test payments each month. – Level 3: live routing between processors, which is what orchestration sells. |
Most stores already have level 1, and most should add level 2 before they consider level 3.
We call it a ladder because each level builds on the one below it. A store that skips to level 3 without level 2 has paid for routing but still has no plan for a frozen account.
Level 1: A second payment method
This is a PayPal button next to your Stripe or WooPayments card form, for example. Neither Stripe nor PayPal charges a monthly fee for standard online checkout: Stripe lists “No setup fees, monthly fees, or hidden fees,” and PayPal Checkout has no monthly fee (Stripe pricing, PayPal fees, both checked 04-11-2026).
It protects you partly. If cards fail, customers with a PayPal account can still pay. Customers who want to pay by card can’t.
Level 2: A verified backup card account
This is a second card processor, such as Square or Authorize.net next to Stripe, that’s fully set up and approved but switched off at checkout. You turn it on only when your main processor fails.
Its value is time. Without one, you’d be opening a new account in the middle of a crisis. Stripe asks you to “allow us 3-5 business days for Stripe to review your documents,” and PayPal says it will “try to review your documents within 2 business days, but sometimes it may take longer” (Stripe, PayPal).
PayPal also says new sellers can have payments held, so an account you open on the day of an outage can still be held (PayPal User Agreement, updated 14-09-2026).
Level 3: Live routing between processors
This is orchestration: two or more processors live at once, with software deciding where each payment goes. It’s the only level that retries a failed card payment on another processor automatically. It’s also the only one with significant ongoing cost and setup, which the section “What vendors sell that a store your size can skip” covers.
Where are you now?
1. Do you offer a payment option run by a different company from your card processor?
2. Do you have a second card processor account that’s already approved?
3. Has anyone on your team switched checkout to it in a test, in the last six months?
4. Do you know where your processor’s status page is?
No to 1: Add level 1. It costs no monthly fee with Stripe or PayPal.
Yes to 1, no to 2 or 3: You’re at level 1. Read the next section to see whether level 2 is worth setting up now.
Yes to all four: You’re at level 2, which covers most stores this size.
| Section recap
The takeaway: Level 1 is a second payment method, level 2 is an approved backup card account that gets a few test payments each month, and level 3 is live routing. – Your next step: Answer the four questions above and note your level. – Why it matters: Stripe verification takes 3–5 business days, so a backup opened during an outage won’t help that day. – What the result tells you: At level 1, the next section helps you decide whether level 2 is worth it. At level 2, skip to the failover plan. |
So how do you know whether level 2, or more, is worth the setup time? The answer depends on two numbers: what an hour of sales is worth to you, and how long you could go without payments.
When a second processor makes sense
| In short
At what point is a backup card processor worth it?When a few days without card payments would cost more than you’d accept losing. For most stores this size, that point comes sooner than the vendor pitch suggests. – How long do outages last? Documented ones run from under an hour to about 15 hours. – What’s the bigger risk? An account freeze. Stripe can pause payouts for 120 days. – What about refunds and disputes? Processors publish dispute limits, but no refund-rate limit. |
An outage costs you hours. A frozen account can cost you months, and a backup account is the only thing that keeps you selling through it. That holds only if the backup has been kept in regular use.
What an outage costs, using real incidents
Processor outages are usually short, but they do happen. Three documented examples:
- Square, 07-09-2023: payments were down from “1:54 PM ET on September 7, 2023” and restored “by 5:19 AM ET” the next day, about 15.5 hours. On Square Online, “websites stayed up, but customers could not complete payments” (Square incident summary).
- Square, 04-11-2026: “a disruption that is impacting some Square services,” which affected Payment Acceptance and Orders for about 1.5 hours (IsDown incident record).
- Stripe, 12-03-2025: “elevated error rates and response times with the API” for about 2.5 hours (Stripe status page).
- Authorize.net, 10-04-2026: “a service disruption currently preventing certain transactions from being processed” for about 4 hours (status-page record).
Here’s what those durations mean at your size, assuming sales spread evenly across the day and every payment ran through the failed processor:
| Annual revenue | Revenue per hour | 2.5-hour outage | 4-hour outage | 15.5-hour outage |
| $200K | $23 | $57 | $91 | $352 |
| $500K | $57 | $143 | $228 | $880 |
| $1M | $114 | $285 | $457 | $1,760 |
Calculation: annual revenue ÷ 8,760 hours. Real losses run higher on sale days and lower overnight, and some customers return later or pay with PayPal.
Those numbers are real but survivable. On their own, they don’t justify an orchestration contract. However, they’re not the whole risk.
The bigger risk: an account freeze
A processor can stop you taking payments entirely. Stripe’s policy lists “Restricting or pausing charges so the User will not be able to accept new payments,” and says it “will typically restrict or pause payouts to the User’s bank account for 120 days” (Stripe Unacceptable Risk Policy, updated 29-07-2026).
PayPal can hold a balance “for up to 180 days” (PayPal User Agreement).
Because of this, the useful question is how long you could go with no card payments while you open a new account. Using Stripe’s 3–5 business days of review:
| Annual revenue | Revenue per day | 5 days with no card payments | 120 days of paused payouts |
| $200K | $548 | $2,740 | About $65,800 |
| $500K | $1,370 | $6,850 | About $164,400 |
| $1M | $2,740 | $13,700 | About $328,800 |
Calculation: annual revenue ÷ 365. The last column shows the scale of sales processed over 120 days, as an upper bound for funds a payout pause could hold back.
What triggers a freeze? Stripe lists reserve triggers such as “elevated dispute activity” and “an unexplainable sharp increase in processing volume” (Stripe reserves FAQ). PayPal names “higher-risk categories like electronics or tickets” and “a high rate of buyer dissatisfaction or disputes” (PayPal User Agreement).
What a hold looks like in practice
In practice, the length of a review is the part that hurts most. On the CBD store we mentioned earlier, here is what happened:
A hold on the CBD store kept it offline for 2 weeks, the review process was long and tedious.
If we had a secondary gateway we could have come online the same day (Provided that gateway had been getting regular test payments.)
That is the real cost of relying on a single gateway. The review took 2 weeks, and with a second gateway already set up, the same store could have been taking payments the same day. “Set up” here means set up and kept in light use, rather than leaving untouched since the day it was connected.
The next question is what causes holds like this, and how often they can be avoided.
Dispute rate matters more than refund rate
No processor publishes a refund-rate limit. PayPal lists “Multiple customers reported problems or requested refunds” as a reason for holds, but gives no number (PayPal). Dispute rates do have published lines:
- Stripe: “The credit card processing industry standard recognizes dispute activity above 0.75% as excessive,” and a sudden spike can trigger a monitoring program before that (Stripe).
- Mastercard: its Excessive Chargeback Merchant program starts at 100 chargebacks and a 1.5% ratio in a month, and a store has to pass both (ChargebackStop, 2026, Beancount, 10-07-2026). Mastercard’s ratio uses this month’s chargebacks divided by last month’s Mastercard transactions.
- Visa: its monitoring program applies at a 1.5% ratio from 01-04-2026, but only once fraud reports and disputes reach 1,500 a month (Visa fact sheet, Stripe).
For a store your size, Stripe’s 0.75% is the line to watch. A $1M store with an $80 average order takes about 1,040 orders a month, so it can’t reach Visa’s 1,500-case minimum. At that volume, 0.75% is about 8 disputes a month.
Learning: Keeping disputes under these lines lowers the chance of a freeze, but it doesn’t remove it. As the triggers above show, a sudden jump in processing volume can also lead to a review.
That is why the CBD store’s two weeks offline matter: a secondary gateway means a review on one account doesn’t stop you taking payments. This assumes the second gateway gets regular use. One that has been idle can face the same sudden-volume problem the moment you switch everything to it.
Which level fits your store
| Your situation | Action | Why |
| One processor, steady sales, dispute rate well under 0.75% | Write the failover plan and add level 1 if you don’t have it. | Outages at your size cost hundreds of dollars, and nothing points to a freeze. |
| Five days without card payments would hurt cash flow | Add level 2: an approved backup card account from a different company. Run a few test payments through it each month. | Setup takes days at a quiet time, and much longer in the middle of a crisis. |
| Disputes near 0.75%, fast growth, preorders or a higher-risk category | Add level 2 now, and keep both accounts in good standing.That includes regular use of the backup. | These are the triggers Stripe and PayPal list for reserves and holds. |
| Several countries, several processors already live, high volume | Consider level 3 and price an orchestration platform. | Routing rules start to pay for themselves once you have real multi-processor volume to route. |
If one of the middle two rows is yours and you want help, it’s the work our team sets up and maintains every day. We scope every website management engagement up front, so you know what it involves, what it costs and how long it takes before any work starts.
Keep a secondary gateway ready
The CBD store’s two weeks offline came down to having only one way to take payments. A second gateway doesn’t have to be a big commitment, and it doesn’t have to run all the time. Our tech lead, Varun, explains how he approaches it:
“I believe everyone should have a secondary gateway, it can be deactivated for now and need not be always active. It will need to be used once a month at least, maybe for test transactions.
If your transaction volume is 100+ thousand dollars a month you may need more than just test transactions.”
In other words, a switched-off gateway isn’t a set-and-forget backup. Without some regular use, it may not hold up when your full payment volume suddenly lands on it.
Get a Payment Backup Plan your Team can Actually Use
We help you set up and maintain the store behind your checkout, from updates and monitoring to the fixes that keep orders coming in. Critical issues are picked up within 2 hours on working days.
- Checkouts working uninterrupted
- Critical issues in 2 hours
- 14+ years managing critical sites
- 99.9% uptime across systems
| Section recap
– The takeaway: Outages cost hours of sales, while a freeze can stop payments for months. A pre-approved backup account protects against both. – Your next step: Work out your revenue per day, then check your dispute rate in your processor dashboard this week. – Why it matters: Stripe treats disputes above 0.75% as excessive, and opening a new account takes 3–5 business days. – What the result tells you: If five days of card sales would hurt, set up level 2. Either way, you need the plan in the next section. |
Whichever level you choose, the day your processor fails will feel the same at first. The plan below covers what to do, in order.
What to do when your only processor goes down
| In shortWhat should you do when card payments start failing?Confirm the cause, tell customers, switch checkout, then recover the orders that failed. Write it down now, so nobody has to work it out on the day.· How do you know it’s the processor? Check its status page, your gateway logs and one test order.· How do you switch? Turn the failing gateway off in WooCommerce payment settings and the backup on. This works best if the backup has had recent test payments.· What about subscriptions? Renewals stay with the processor that saved the card, so a backup won’t charge them. |
The first 30 minutes decide how many orders you lose, so the plan has to exist before the outage does.
| Step | Who and how long | What to do |
| 1. Confirm the processor is the problem [TEST ON STAGING] | You or your developer, about 10 minutes | Check the processor’s status page (Stripe, PayPal and Braintree, Square, Authorize.net), the gateway log under WooCommerce > Status > Logs and the notes on a failed order. Then place one test order with another payment method. If PayPal works and cards fail, it’s your card processor. |
| 2. Tell customers | You, about 10 minutes | Add a checkout banner: “Card payments are temporarily unavailable. Please pay with PayPal, or try again in an hour. Your cart will be saved.” |
| 3. Switch checkout to your backup [TEST ON STAGING] | Your developer, about 15 minutes | In WooCommerce > Settings > Payments, turn the backup on and drag it to the top. If it hasn’t taken a payment in the past month, it may see more declines at first, so watch the first orders closely. Turn the failing gateway off in the same screen, but don’t deactivate its plugin. Make sure the backup runs through a different company, then place one real test order. |
| 4. Recover failed orders [TEST ON STAGING] | Your developer, 1–2 hours after the outage | Let delayed payment updates arrive, compare “Pending payment” orders with your processor dashboard, and email customers whose payment failed. |
| 5. Review the plan | You, about 30 minutes, within a week | Note when the problem started, when you noticed, when you switched and how many orders failed. A long gap before noticing is a monitoring problem. A slow switch is a plan problem. |
Three details in that table cause most of the trouble:
- Deactivating the plugin instead of switching the gateway off: WooCommerce’s docs say that if the plugin is deactivated, “the subscriptions using that payment method will switch to Manual Renewal,” while switching it off in payment settings keeps renewals automatic (WooCommerce Subscriptions docs).
- A backup on the same company: WooPayments and the WooCommerce Stripe plugin both run on Stripe, so a Stripe outage takes out both.
- Clearing pending orders too early: Stripe “attempts to deliver events to your destination for up to three days with an exponential back off in live mode” (Stripe), and PayPal reattempts “up to 25 times over the course of 3 days” (PayPal). Orders paid during an outage can still update on their own.
If you sell subscriptions, a backup won’t save your renewals
Renewals stay with the processor that saved the card. WooCommerce’s docs say Subscriptions “handles the payment through the payment gateway used for the initial purchase” (WooCommerce), and saved cards are stored against that gateway.
So during an outage, your backup can take new orders, but it can’t charge existing subscribers. Those renewals wait for WooCommerce’s retry schedule, which by default tries five times over seven days, at 12, 12, 24, 48 and 72 hours (WooCommerce docs).
Moving saved cards to another processor is a formal project. Stripe will only transfer card data “to another PCI DSS Level 1-compliant payment processor” (Stripe). Braintree is blunter: “We will not run any periodic exports for backup or failover” (Braintree).
Renewal problems can also be silent. One subscription brand we worked with, MollyMy, found its renewals had stopped after an earlier migration by another agency broke the link between each subscription and its payment method. There were no errors and no alerts, only revenue drying up.
Our team traced and repaired the data in 30 hours, and every renewal processed again without asking a single customer to re-enter their card (case study).
How a magazine brand recovered every frozen renewal in 30 hours
MollyMy's renewals stopped with no errors and no alerts. Our team found the broken link between subscriptions and their payment method and restored it without touching a single customer.
- 100% renewal success
- 0 customer-facing errors
- 30 hours, end to end
- No cards re-entered
If your biggest sales days are close, our Black Friday readiness checklist covers peak-season payment failover alongside load testing and checkout freezes.
| Section recap
– The takeaway: Confirm, tell customers, switch, recover, review. A backup takes new orders but can’t charge existing subscribers. – Your next step: Copy the five-step table into a shared document this week, add your status page links and the name of whoever switches checkout. – Why it matters: Deactivating a gateway plugin instead of switching it off moves every subscription on it to manual renewal. – What the result tells you: If nobody on your team can do step 3 in 15 minutes, test it on a staging copy before you need it. |
With a plan in place, the vendor pitch looks different. The next section sorts what orchestration platforms sell into what matters at your size and what can wait.
What vendors sell that a store your size can skip
| In short
– Which orchestration features matter for a $200K to $1M+ store?A few, and most of them you can get without a platform. The rest are built for merchants routing across many countries. – What matters now? A ready backup, the right to move saved cards, and clear reporting. – What can wait? Cost-based routing, multi-country processors and coordinating card security checks across processors. – What does it cost? Most vendors say “contact sales.” One publishes $750 a month for card storage alone. |
At your size, a written plan and a backup account cover most of what an orchestration platform would do for you.
| Feature | What it does | At $200K to $1M+ |
| Failover and retries | Sends a failed payment to another processor | Matters, but a manual switch to a level 2 backup covers most outages at your size. |
| A portable card vault | Stores saved cards outside any one processor, so you can move them | Matters most for subscription stores. Ask your current processor about its export rules first. |
| Unified reporting | One dashboard across processors | Useful only once you run two processors live. |
| Cost-based routing | Sends each payment to the cheapest processor | Skip for now. Savings need volume across several processors. |
| Local processors by country | Routes cards to a processor in the buyer’s country | Skip unless you sell heavily in several countries. |
| Network tokens and 3D Secure across processors | Card-network tokens and coordinated security checks | Skip. Stripe’s docs show security checks across processors need separate details for every processor you route to. |
Sources: vendor feature pages and Stripe’s orchestration docs, checked 04-11-2026.
What it costs
Most vendors don’t publish prices. Primer, Gr4vy, IXOPAY, Yuno and APEXX all route you to sales. Spreedly is the exception: its card vault starts “at $750 per month” (Spreedly, checked 04-11-2026). That’s $9,000 a year, or 0.9% of revenue for a $1M store and 4.5% for a $200K store, before any routing fees.
Stripe announced its own orchestration feature in May 2025, which lets you “manage multiple payment processors with full control and visibility, from right within Stripe” (Stripe).
As of 04-11-2026, its docs say it’s in private preview, and the other processor’s “fees and liability… remain subject to the terms that you agreed to with that processor” (Stripe docs).
For WooCommerce, Hyperswitch, an open-source orchestration project, offers a WooCommerce plugin and a free self-hosted edition (Hyperswitch docs). Self-hosting means your team runs payment infrastructure, which is a bigger job than most stores this size want to take on.
The performance claims, and what they mean for you
Vendors publish approval-rate gains, and these are their own figures. Spreedly claims a “30%+ Increase in authorization rates,” IXOPAY says it “typically delivers around a 15% increase in payment acceptance rates,” and Yuno claims “up to a 7% uplift in approval rates” (Spreedly, IXOPAY, Yuno).
For comparison, Stripe says its Authorization Boost features, which work on a single processor, “Increase acceptance rates by 3.8% on average” (Stripe). Ask any vendor how much of its claimed gain you’d get from your current processor’s own tools.
Independent voices are more cautious. Glenbrook’s Samantha Gordon writes that for smaller merchants, “the simplicity of a full-stack solution offered by a single PSP may outweigh incremental benefits.”
Adyen, which sells to large merchants, says orchestration “tends to come up most often for large enterprises running high transaction volumes across multiple markets” (Adyen, 27-04-2026).
Not everyone agrees. Checkout.com argues that “From small online merchants to large multinational enterprises, payment orchestration platforms can benefit any company” (Checkout.com, 19-01-2023), though it sells an orchestration product. [Recheck: over two years old] We found no independent data on how many stores your size use orchestration, so the decision comes down to your own numbers.
Move saved cards between gateways without asking subscribers to pay again
When you switch processors, the hard part is the saved cards and renewal dates. As an official WooCommerce Subscriptions migration partner, we move payment tokens and billing schedules so renewals keep running.
- 300+ subscription migrations
- Official Woo migration partner
- Saved cards moved securely
-
subscription revenue lost
| Section recap
– The takeaway: At your size, backup readiness and card portability matter. Cost routing and multi-country features can wait. – Your next step: Before any demo, ask your current processor about its card export rules and which Authorization Boost-type features you already have. – Why it matters: One vendor’s card vault alone costs 0.9% of revenue at $1M, and you’d need more than that back in extra approvals to break even. – What the result tells you: If a vendor can’t show savings above its cost using your numbers, you don’t need it yet. The next section covers when that changes. |
The vendor picture is also shifting. Processors have started building orchestration into their own products, which raises a fair question: will your current processor soon do all of this for you?
What changes when processors build orchestration in?
| In short
– Will built-in orchestration make a backup processor unnecessary? Probably not. It can route payments to other processors, but it still runs on the one account a freeze would stop. – What’s available? Stripe’s orchestration feature, announced in May 2025 and still in private preview. – What does it cover? Card payments routed to other processors you already have contracts with. – What should you do now? Keep a backup account with a different company in regular use,, and revisit when the feature is generally available. |
Built-in orchestration may make routing cheaper and easier. It doesn’t remove the need for a backup that sits outside your main processor.
Stripe announced its orchestration feature at its Sessions conference in May 2025. It lets businesses “manage multiple payment processors with full control and visibility, from right within Stripe” (Stripe). As of 05-11-2026, Stripe’s docs list it as private preview (Stripe docs).
The docs set out some limits. It doesn’t support non-card payments, Link, Connect or disputes, and each processor you route to keeps its own fees and liability. You also need your own contract with every processor you route to, so it doesn’t replace opening those accounts.
Because of this, our view is that built-in orchestration doesn’t change the advice for stores your size. It’s configured on your Stripe account. Stripe hasn’t published how routing behaves if that account is restricted, so we wouldn’t count on it during a freeze. A backup account with a different company, ready to switch on in WooCommerce, still covers that risk.Ready means it gets test payments every month.
Where it could help is cost. If routing comes built into a processor you already use, the main argument against level 3 for a store your size, the price of a separate platform, gets weaker. Stripe hasn’t said whether the feature will reach WooPayments or the WooCommerce Stripe plugin, so for now it remains something to watch.
Our tech lead, Varun, on what he’d want to see before recommending it to a client:
“Built-in orchestration can make routing easier, but it runs on the same Stripe account. If that account is restricted, I wouldn’t assume the routing keeps working. Before I recommend it to a client, I’d want to see it available in WooPayments or the WooCommerce Stripe plugin, a clear answer on what happens when the account is restricted, and support for subscription renewals on saved cards.
Until then, I’d keep a secondary gateway with a different company. It can stay switched off, but we can’t keep an inactive gateway for infinite time. Because it may or may not work when you suddenly need it. It’s not guaranteed, so there’s a bit of risk. So, a few test transactions every month lower that risk. Even so, reactivating an existing gateway is still simpler than registering a new one from scratch.”
| Section recap
– The takeaway: Processors are adding orchestration, but it runs inside the account a freeze would stop.· Your next step: Keep your level 2 backup with a different company, use it regularly, and set a reminder to recheck Stripe’s orchestration docs in six months. – Why it matters: Stripe’s feature is still in private preview and doesn’t cover non-card payments or disputes. – What the result tells you: If it becomes generally available in WooCommerce at no extra platform fee, level 3 gets cheaper. Your need for an outside backup stays the same. |
Whether routing comes from a vendor or your processor, the question of when one processor is too risky stays the same. Some stores reach that point, and the signs are usually visible ahead of time.
When a second processor becomes essential
| In short
– When is one processor too risky? When a short gap in payments would do lasting damage. Five situations push you there. – Revenue per hour: an outage costs more than you’d tolerate. – Peaks and history: a big share of sales lands in a few days, or your processor keeps having incidents. –Freeze exposure: preorders, fast growth or a higher-risk category. |
If any of these apply, a live second card processor stops being optional, even if a full orchestration platform still is.
1. Your revenue per hour is high. Use the table in “When a second processor makes sense.” If a 4-hour outage would cost more than a day of a developer’s time, keep two processors live, with the backup listed second at checkout.
2. Your sales peak sharply. If a large share of your year lands on a handful of days, a two-hour outage on one of them costs far more than the average suggests. Our Black Friday readiness checklist covers peak planning.
3. Your processor keeps having incidents. Check its status page history. If card payment incidents keep repeating, a second live processor turns each one into an inconvenience.
4. A freeze would stop your business. Preorders, sudden growth and higher-risk categories are all on Stripe’s and PayPal’s lists of reserve and hold triggers. A second processor in good standing keeps you selling while you resolve a review.
5. You sell heavily outside your home country. Stripe adds 1.5% for international cards (Stripe pricing). At real cross-border volume, routing to local processors can start to pay, and that’s when level 3 is worth pricing.
The evidence on “how much is enough” is thin. No processor or analyst publishes a revenue level at which a second processor becomes necessary, so treat these as signals to weigh against your own numbers.
| Section recap
– The takeaway: High revenue per hour, sharp peaks, repeat incidents, freeze triggers or cross-border volume make a second live processor essential. – Your next step: Mark which of the five apply to you and look at your processor’s incident history for the past year. – Why it matters: These are the situations where one processor failing costs more than running two. – What the result tells you: None apply: level 2 is enough (with monthly test payments). One or two apply: run two processors live. Cross-border volume at scale: price level 3. |
Back to that sale day with failed card payments and a vendor demo waiting in your inbox. You now know the demo solves a problem you may not have yet.
For most stores your size, the answer is a written plan and an approved backup account, tested once, with a live second processor added when one of the five signals appears.
Key learnings for stores doing $200K to $1M+
| What we learned | What it means for you | Example |
| Orchestration routes payments across several processors. | It solves a multi-processor problem. With one processor, you need a plan and a backup first. | Spreedly’s card vault alone starts at $750 a month, or $9,000 a year. |
| WooCommerce doesn’t switch gateways automatically. | Someone on your team has to switch checkout by hand, so write down who and how. | Turning the failing gateway off in Payments settings takes minutes when the steps are already written. |
| A freeze is a bigger risk than an outage. | Keep a backup account approved in advance, because new accounts take days to verify. Put a few test payments through it each month so it’s ready for real volume. | Stripe can pause payouts for 120 days, and its verification takes 3–5 business days. |
| Dispute rate is the number to watch. | Track it monthly in your processor dashboard and act well before 0.75%. | At about 1,040 orders a month, 0.75% is roughly 8 disputes. |
| Built-in orchestration doesn’t replace an outside backup. | Watch Stripe’s feature, but keep a backup account with a different company in regular use. | Stripe’s orchestration is configured on your Stripe account and is still in private preview as of 05-11-2026. |
| Subscriptions don’t move with a backup. | During an outage, renewals wait for the retry schedule. Moving saved cards is a separate project. | WooCommerce retries a failed renewal five times over seven days by default. |
Your next steps
This week: Write the five-step failover plan, bookmark your processor’s status page, turn on gateway logging and check your dispute rate. This is free and covers most of your risk.
Over the next 30 days: Open and verify a backup card account with a different company, then test the switch on a staging copy of your store. After that, put a few test payments through it every month. Doing it now takes days at a calm time instead of during a crisis.
At month six: Run the switch test again and check the five signals in “When a second processor becomes essential.” That tells you whether to run two processors live.
Hold off on: Signing an orchestration contract until a vendor shows savings above its cost using your own numbers.
Payment orchestration FAQs
What is payment orchestration?
It’s a layer between your store and several payment processors that decides where each payment goes and retries failed payments on another processor. It’s mainly used by large merchants with several processors across several countries.
What are the best payment orchestration platforms?
Well-known platforms include Spreedly, Primer, Gr4vy, IXOPAY, Yuno and the open-source Hyperswitch. Stripe also has an orchestration feature in private preview. Most don’t publish prices, so compare them on your own volume and ask what they add beyond your current processor’s tools.
Can WooCommerce use multiple payment processors?
Yes. You can enable several gateways in WooCommerce > Settings > Payments and set their order. WooCommerce doesn’t move a failed payment to another gateway automatically, so failover is a manual switch.
Does a backup processor protect subscription renewals?
No. Renewals use the gateway that took the first payment, and saved cards are stored against it. A backup can take new orders during an outage, while renewals wait for WooCommerce’s retry schedule.
What dispute rate is too high?
Stripe says the industry treats dispute activity above 0.75% as excessive, and a sudden spike can trigger monitoring sooner. No processor publishes a refund-rate limit, though high refunds can still prompt a review.
Will Stripe’s orchestration feature replace a backup processor?
Not for the main risk. It routes card payments to other processors you contract with, but it’s configured on your Stripe account, and it’s still in private preview. Keep a backup account with a different company for the day your main account is restricted.
How long does it take to set up a backup payment account?
Plan for at least a week. Stripe asks for 3–5 business days to review documents, and PayPal aims for 2 business days but says it can take longer. Set it up and test it before you need it.
Key reads from this guide
In case you missed them along the way, here are the WisdmLabs pages linked in this guide:
| Link | Summary |
| Website management services | If you’d rather not be the one switching checkout during an outage, this covers how we look after your store day to day. |
| MollyMy case study | Renewals stopped with no warning? See how one subscription brand got every one of them running again in 30 hours. |
| WooCommerce Subscriptions migration | Planning to change processors with subscribers on file? Start here to keep saved cards and renewal dates intact. |
| Black Friday readiness checklist | Perfect for stores heading into peak season. Covers payment failover alongside load testing and checkout freezes. |
| Ecommerce website management services | Wondering what a management partner should cover for a growing store? This sets out the weekly, monthly and quarterly work. |
| Building a custom WooCommerce payment gateway | For developers: if your processor has no WooCommerce plugin, this walks through building a gateway. |
If you’ve just realized your store has no failover plan, here’s how we can set one up with you:
1. A short call. We look at your processors, your checkout and how much of your revenue runs through subscriptions.
2. A written plan. Your five steps, with status page links, names and the exact settings to change.
3. A tested backup. We help you connect a backup gateway and test the switch on a staging copy of your store.
4. Ongoing care. We keep checkout, gateways and renewals working as part of website management, and update the plan as your store grows.