Every merchant with one provider is one review away from a business with no revenue. Not because the provider is bad — because a policy change, a spike in disputes or a routine audit can pause acceptance for a week, and a week without card payments is not something most businesses have planned for.
A backup payment provider is the answer, and the question people actually ask is not whether to have one but what it costs to keep one idle. That number is smaller than most expect, and this is how it breaks down.
Contents
- What a backup actually protects against
- Backup is not the same as cascading
- What it costs to keep one warm
- How much volume to send through it
- Setting it up so the switch takes minutes
- Do not describe yourself differently to the second one
- When to open the second one
- In short
What a backup actually protects against
- A pause, not a closure. Most interruptions are temporary: documents requested, a limit review, a vertical reclassified. Acceptance stops while the questions are answered.
- One route going down. Technical outages happen to everyone, and they arrive without warning on the busiest day.
- A rate rise you cannot argue with. With one provider you negotiate from a position of having nowhere to go.
- The slow start. Onboarding takes as long as it takes, and starting it after the pause means the whole pause is downtime.
What happens when a pause turns into a closure is set out in our piece on what to do when a merchant account was terminated.
Backup is not the same as cascading
Cascading routes a declined transaction to another route inside the same setup, and it lifts the approval rate. It does not help when the whole acceptance is paused, because every route belongs to the same agreement. That mechanism is explained in our piece on payment cascading and orchestration.
A backup is a separate agreement with a separate provider, approved and technically connected, sitting at low volume. The distinction matters because the two solve different failures and neither replaces the other.
What it costs to keep one warm
There is no standing fee for having an approved account that is barely used. What you pay is the per-transaction economics on whatever volume you send through it: MDR 3%–5% depending on the type of business, 0,50 EUR per transaction, settlement in EUR over SEPA 0,20%, term T+7, rolling reserve 10% for 180 days. The exact figure is set per merchant, and we consider individual solutions for your business.
The real cost is elsewhere: the reserve on the backup starts building from its first transaction, and the documents have to be maintained on both sides. Budget the reserve, not a subscription. What the whole picture looks like is in our piece on what card acceptance costs.
All published lines sit on the pricing page.
How much volume to send through it
Zero is the wrong answer. An account with no traffic is an account that has never been tested, and it will be tested for the first time on the worst day of your year. It also drifts: keys expire, the descriptor is wrong, the callback was never verified.
Send a small, steady share — enough that settlements arrive, refunds work and reports reconcile. It also gives the backup provider real numbers about you, which is exactly what shortens the conversation when you need to scale it up overnight. The mechanics of routing and settlement are described under payment processing.
Setting it up so the switch takes minutes
- Both providers configured in the same checkout, switchable by a setting rather than a deployment.
- The descriptor decided for each. Customers should recognise the charge whichever route it took.
- Recurring payments mapped. Card-on-file tokens do not move between providers; know in advance what re-authorisation means for your subscribers.
- Refund paths tested on both. The refund route is the one that most often turns out to be unconfigured.
- Reconciliation that handles two sources. Two settlement reports in different formats is the part finance discovers too late.
Do not describe yourself differently to the second one
The temptation is to present a cleaner version of the business to the backup provider. It fails the same way it fails everywhere: the description has to match the site, and the site is the same site. Applying honestly to both is also what makes the second file quick — you already assembled it once. The full list is in our merchant approval checklist.
When to open the second one
The wrong moment is the obvious one: after the first pause, when you need it working today and onboarding starts from zero. The right moments are less dramatic.
- When the volume becomes worth protecting. If a week without acceptance would hurt, you are already past the point.
- While the numbers are good. A clean dispute ratio and steady turnover make the second application quick; applying during a bad quarter makes it slow.
- Before a season. Whatever your peak is, the worst time to discover a limit is inside it.
- When the vertical is being reclassified. Policy changes arrive with notice more often than people expect — that notice is the signal.
In short
A backup provider is insurance priced as transaction economics rather than as a subscription. Approve it before you need it, keep a small steady share of traffic flowing through it, test refunds and callbacks on both, and describe the business identically to each. Then a pause on one merchant account is an inconvenience instead of a week without revenue.