A multi-acquirer strategy is a plan for processing your merchants’ card payments through two or more acquirers, so that losing one acquirer slows your business instead of stopping it. This guide is for PSPs, payment facilitators, e-money institutions and platforms whose revenue depends on acquiring contracts they do not control.
What Is a Multi-Acquirer Strategy?
A multi-acquirer strategy decides how many acquirers you contract, which merchants and segments each one may take, how volume is split and what happens when one of them stops. It is a business and risk decision. Payment routing then carries it out, payment by payment, inside your gateway.
The terms overlap. Multi-acquiring, a multi-acquirer setup and a multi-PSP strategy describe the same idea from different seats. A merchant spreads its volume across payment providers, and a PSP spreads its merchant portfolio across acquiring banks. This guide takes the PSP’s seat.
The strategy and the rules are separate layers. Your white label payment gateway holds the acquiring connections, and its smart routing rules pick one for each payment. The strategy decides which connections exist, what each may accept and which one takes over when another fails.
Three ways to set up acquiring
Criteria
Single acquirer
Primary and backup
Active-active split
When one acquirer stops
All card processing stops
Traffic the backup may accept moves to it
The other acquirers absorb what their limits allow
Volume at each acquirer
All of it
Most at the primary, a small live share at the backup
Split by segment or by weight
Is the backup proven?
No backup
Only if it carries live traffic every month
Yes, every route is live
Contracts, reserves and reports
One of each
Two of each
One set per acquirer
Fits
A first contract, a few low-risk merchants
Most PSPs with one main market
High-risk portfolios, several markets, high volume
Definition
Concentration risk
The share of your processed volume, active merchants and stored cards that depends on a single acquirer. Measure all three: an acquirer can carry a small share of your volume and most of your recurring cards.
Why Do Acquirers Terminate or Freeze a PSP?
Acquirers terminate or freeze a PSP because the acquirer carries the scheme liability for every merchant you bring. When your disputes, fraud or merchant mix move outside its risk appetite, or a scheme flags the acquirer itself, cutting you off is its quickest fix. Outages are the other cause, and they need no decision at all.
The contract usually allows a fast exit. A payment facilitator is a PSP that signs sub-merchants under its own acquirer contract. If you work as one, section 5.3.1.1 of the Visa Core Rules and Visa Product and Service Rules requires your agreement with the acquirer to include its right to immediately terminate you.
The same right covers your sponsored merchants, the sub-merchants you board under that contract. Good cause, fraudulent or other activity, or a request from Visa is enough.
Scheme monitoring programmes
Visa identifies acquirers under the Visa Acquirer Monitoring Program (VAMP) and may evaluate a payment facilitator’s whole portfolio as one aggregated merchant (section 10.4.3.1). A few bad merchants can put all of your volume under review.
Underwriting review
The acquirer re-checks your merchants, their merchant category codes (MCCs) and your KYC files, often after an audit. Gaps in high-risk onboarding are the usual finding.
Change in risk appetite
The acquirer leaves a vertical, a country or a group of high-risk MCCs, or its own regulator or sponsor tells it to. Your own figures do not change that decision.
New limits or reserves
The acquirer lowers a monthly cap, cuts transaction limits on a merchant ID (MID), raises the reserve or delays settlement. Traffic above the new limit fails.
Technical outage
The acquirer’s host times out or answers slowly. Nobody decided anything, but payments stop all the same. One of our cases shows an acquirer failure contained in seconds.
Scheme prohibition
Once Visa prohibits a merchant or a payment facilitator, the acquirer must terminate the agreement no later than the date Visa sets (section 1.5.1.9).
Rule
A termination for cause follows you
Section 10.10.1.1 of the Visa Core Rules and Visa Product and Service Rules covers merchants terminated for reasons such as excessive disputes, laundering or identification in VAMP reports. The acquirer must add each one to the Terminated Merchant File, which Mastercard maintains as MATCH. The deadline is close of business on the day after the merchant is notified.
A terminated third party agent, including a payment facilitator or an independent sales organization (ISO), goes on the Visa Merchant Screening Service (VMSS) when its criteria are met.
Note
Bank accounts carry the same risk
If you hold merchant funds as a payment institution, your safeguarding and settlement accounts sit with banks that can close them too. Article 36 of PSD2, the EU’s second Payment Services Directive, requires that payment institutions get access to bank payment account services on an objective, non-discriminatory and proportionate basis.
Keep a second banking partner as well: Article 36 only obliges a bank that rejects you to give the regulator duly motivated reasons. That gives you a reason on file, not an account. Read more about payment service licences.
What Breaks When You Depend on One Acquirer?
With one acquirer, a cut-off stops four things at once: new authorizations, charges on stored cards, payouts to your merchants and the boarding of new ones. Chargebacks, refunds and the reserve on past volume stay with the old acquirer, so the work goes on after the revenue stops.
What a single-acquirer cut-off does
Area
What happens
Who owns it
Authorizations
Every card payment for every merchant fails or times out
The acquirer stops; you answer to your merchants
Stored cards
Cards kept in the acquirer’s vault cannot be charged elsewhere until that acquirer releases them
Whoever holds the vault
Settlement
The acquirer pays out transaction totals less disputes, fees and reserve funds, promptly after deposit under Visa rules and on the schedule your contract sets
The acquirer
Chargebacks and refunds
Disputes on past payments keep arriving at the old acquirer
The old acquirer receives them; you remain liable for your merchants
A new acquirer
It must underwrite you and register you with Visa before any transaction, and the registration is specific to that acquirer
The new acquirer registers; you supply the documents
Source: Visa Core Rules, sections 1.5.6.2, 1.9.8.6 and 1.9.8.7
The last row hurts most. Under section 1.9.8.6 of the Visa Core Rules, Visa may deny or reject a third party agent’s registration at any time, with or without cause. If you start that process after the cut-off, you process nothing while it runs.
The liability does not leave with the traffic. Whatever your model, you stay financially liable to your acquirers for the transactions of your merchants, including disputes that arrive after the contract ends.
Stored cards decide how fast you recover. In one of our cases a high-risk PSP lost its acquirer overnight. Its tokens were extracted from the old acquirer and re-tokenised. 95% of the tokens the old acquirer made available moved to a new acquirer in about one week, and no customer re-entered a card: see tokens migrated in one week.
What Does a Multi-Acquirer Architecture Need?
A multi-acquirer architecture needs six parts: contracts and MIDs at each acquirer, scheme registration through each of them, tokens your gateway holds, failover rules, a reserve plan for each acquirer and reconciliation of every acquirer’s reports. A backup is only as ready as its weakest part.
What makes a backup acquirer usable
Part
Ready means
How you test it
Who owns it
Scheme registration
Each acquirer has registered you as a third party agent; under Visa rule 1.9.8.7 each one registers you separately
Written confirmation from each acquirer
The acquirer registers; you supply the documents
Contracts and MIDs
MIDs open for the merchants and segments the backup will take, with schemes, currencies and caps agreed
A live payment on each MID every month
You sign; the acquirer underwrites and issues MIDs
Tokens
Stored cards held as gateway tokens or network tokens (issued by the card scheme instead of the acquirer) that every route can charge
A test charge on a stored card through each acquirer
Your platform vendor runs the vault; you choose the token types
Failover rules
Every primary route names a backup, with timeout and error thresholds
A failover drill on a small share of traffic
You write the rules; the gateway runs them
Reserves and settlement
Reserve terms and payout schedule known for each acquirer
A cash forecast of the reserve held at each acquirer
The acquirer holds the reserve; you fund it
Reconciliation
Each acquirer’s settlement file matched to your transactions
A daily match with no unexplained items
You reconcile; the vendor supplies the tool
Tokens that work across acquirers
Acquirer-agnostic tokens are the part most often missing. When the vault belongs to your current acquirer, a new route can charge those cards only after that acquirer releases them for migration, and an acquirer that has just terminated you may release some or none. Our guide to tokenization service providers compares where a vault can sit.
Reserves at more than one acquirer
Each acquirer may hold back part of your settlement against disputes. With two acquirers you fund two reserves, and the one at an acquirer that terminates you comes back on that contract’s schedule. On your side, a rolling reserve on merchant payouts covers the disputes you will owe.
Questions to ask a backup acquirer
Which of your MCCs, countries and currencies will it accept, and under which caps?
How long do underwriting and scheme registration take, and which documents does it need?
What reserve, payout delay and termination notice does the contract set?
Will it accept network tokens or tokens migrated from your vault?
Is there a minimum monthly volume, and what happens if the backup does not reach it?
Which response codes does its host return during an outage, and who answers an incident call?
How Should You Split Volume Between Acquirers?
Split volume so that each backup acquirer carries enough live traffic to prove it works and has limits large enough to absorb what the failing acquirer carried. A backup that sees no traffic for months is a contract, not a route. Too small a share also weakens your position when you negotiate.
Primary and backup
The primary keeps most of the volume and the best fee tier.
The backup takes a small weighted share every day, enough to keep its MIDs active.
Risk: the backup’s caps are sized for its share, not for the primary’s traffic.
Active-active split
Each acquirer takes the segments it approves best, such as one country or card type.
Every route is live, so an outage costs you a share, not everything.
Risk: each acquirer sees less volume, which can move you to a weaker fee tier.
Illustrative example
Can the backups absorb the primary?
Assumptions, all invented for the example: you process EUR 10,000,000 a month. Acquirer A takes 70%. Acquirer B takes 20% under a monthly cap of EUR 5,000,000. Acquirer C takes 10% under a cap of EUR 2,000,000. Every merchant is eligible at all three.
Illustrative figure
Acquirer A
Acquirer B
Acquirer C
Monthly volume today
EUR 7,000,000
EUR 2,000,000
EUR 1,000,000
Monthly cap
n/a
EUR 5,000,000
EUR 2,000,000
Headroom
n/a
EUR 3,000,000
EUR 1,000,000
If A stops, B and C can take EUR 4,000,000 of its EUR 7,000,000. EUR 3,000,000 a month, 30% of your volume, has no route. Raise the caps, or add a backup for the largest segments, before you need it.
Caps are only half of the test. Each backup must also accept the MCCs and countries of the merchants it would inherit, or their traffic has nowhere to go whatever the headroom.
Routing that tracks processing limits can move traffic before a cap is hit, so a backup fills up gradually instead of failing at the cap.
Volume also sets your cost. Acquiring contracts often tie fee tiers or commitments to volume, so every split moves margin. Our guide to the payment gateway business model explains the fee split between you and your acquirers.
What Should You Do When an Acquirer Goes Down?
Treat an acquirer outage as an incident with a runbook: detect it on your own monitors, decide whether the acquirer is slow or dead, isolate it, move eligible traffic, clean up late responses and bring it back in steps. Write the runbook and name the owners before the first outage.
Detect it before merchants do
Your operations team, or your platform vendor’s support, watches response time, error rate and queue depth for each acquirer. In our acquirer isolation case, responses of 30 seconds or more showed on platform monitors before any client ticket.
Decide: slow or unresponsive
If the acquirer is slow but alive, increase the queue depth so it keeps processing while the load is managed. If it does not respond, disable it. The on-duty team decides in real time, with an on-call engineer to confirm.
Isolate it and redirect traffic
You disable the acquirer in the gateway, and the failover rules send eligible payments to the backup routes. Payments that no backup MID may accept fail fast instead of piling up in a queue.
Reverse before you resend
A payment that timed out may still have been approved by the issuer. Your gateway sends a reversal to the first acquirer before a second attempt, and your team reconciles late responses. The failover, cascading and retries section covers the rules.
Tell merchants and the acquirer
Your support team tells affected merchants which payment types are hit. Your account manager opens an incident with the acquirer and asks for a cause and a recovery time.
Bring it back in steps
You re-enable the acquirer on a small weighted share and compare approvals and response times with the backup in your transaction statistics. Then you restore its full weight and update the thresholds.
An outage is not a decline. Timeouts and technical errors call for failover, while declines follow the scheme rules on reattempts. Our guide on how to recover declined transactions covers that second case.
How Is an Acquirer Termination Different From an Outage?
An outage is technical and temporary: you move traffic and wait. A termination, a freeze or a limit change is a commercial decision with a date: you move merchants, stored cards and open liabilities, and the acquirer decides when its reserve comes back. Each event needs its own playbook.
Five ways to lose an acquirer
Event
Warning you get
What you move
What stays behind
Outage
None; your monitors see it first
Eligible traffic, for hours or days
Nothing; traffic returns when it recovers
Lower caps or a higher reserve
The notice period in the contract
Volume above the new cap
Merchants that fit the new limits
Settlement freeze
Often none
New traffic, while the freeze lasts
Funds already held
Termination of your agreement
The notice period, or none for good cause
All merchants, MIDs and stored cards
Reserve, disputes and refunds on past payments
Termination of one merchant for cause
Often none
Only after the next acquirer has reviewed it
That merchant’s disputes and the MATCH or VMSS listing
A merchant terminated for cause changes what you may do next. Moving it quietly to your backup keeps the listing from that acquirer’s underwriting. Disclose it and let the backup decide. In Visa’s Europe and CEMEA regions (Central and Eastern Europe, Middle East and Africa) and in parts of Asia-Pacific, an acquirer may not refuse a merchant solely on a VMSS listing (section 10.17.1.1).
When a termination notice arrives
Confirm the scope in writing: all your MIDs or named merchants, and the effective date.
Move first the merchants your backup has already underwritten.
Keep a team on disputes and refunds that still arrive at the old acquirer.
Agree the reserve release dates with the old acquirer in writing.
Update merchant settings and notices through your merchant management tools.
What Are the Costs and Risks of a Multi-Acquirer Strategy?
A multi-acquirer strategy costs you more contracts, reserves, reconciliation and compliance reviews, and it opens new ways to break scheme rules. The worst is splitting a merchant across acquirers to keep its ratios low. Each risk in the table has a control.
Multi-acquirer risks and how to reduce them
Risk
What goes wrong
How to reduce it
Circumventing monitoring
Changing a merchant’s name, data or performance to keep it out of VAMP: Visa may charge the acquirer USD 25,000 per merchant per month and permanently disqualify the merchant and its principals (Visa Core Rules and Visa Product and Service Rules, section 12.5.3.2)
Route by eligibility and approval rate, never to dilute a ratio. Report every merchant under its real name and MCC
Capital in reserves
Each acquirer holds its own reserve, so cash is locked in several places
Negotiate reserve terms per acquirer and put them in your cash forecast
Thinner volume
Each acquirer sees less traffic, misses a volume commitment or a better fee tier
Split only the segments that need a backup, and keep the minimum weights a contract requires
Reconciliation load
Different settlement files, currencies and payout calendars for each acquirer
Merchants get boarded under the acquirer with the loosest rules
Run one risk policy in your gateway with anti-fraud tools, and add each acquirer’s stricter rules on top
Wider audit scope
Every acquirer audits you, and card data copied to several places widens your PCI DSS scope
Keep card data and tokens inside the gateway, whichever acquirer is used
Compliance gets simpler when one system holds the card data, the risk rules and the reports for every acquirer. Each acquirer then audits the same controls. PCI DSS stays a shared duty: outsourcing PCI DSS to a platform vendor reduces your scope and does not remove it.
Who Does Not Need a Multi-Acquirer Strategy?
You do not need a multi-acquirer strategy yet if you are still signing your first acquirer, or if you serve a few low-risk merchants in one market and could survive a few days without card processing. A written exit plan and portable tokens are enough there. Add the second acquirer when the plan stops being enough.
A second acquirer pays off
A portfolio with high-risk MCCs.
Recurring merchants with a large stored-card base.
Merchants in several countries that need domestic acquiring.
A single acquirer carrying most of your revenue.
An exit plan is enough for now
A first acquirer and licence still being chosen.
A few low-risk merchants in one market.
Volume too small for a second acquirer’s minimums.
Merchants with their own acquiring, using you only as a gateway.
eComCharge is a white-label payment gateway that holds all your acquiring connections in one platform under your brand. You sign the acquirers. The platform connects them, routes between them and keeps stored cards in its own vault, so your merchants stay integrated with your gateway, not with an acquirer.
170+ active connectors with banks and payment methods, and new connectors developed on request.
Smart Routing with more than 50 routing conditions, sequential fallback and weighted distribution between connections.
A local token vault on a PCI DSS Level 1 platform, Visa Token Service and Mastercard Secure Card on File.
Token migration between acquirers: in one case, 95% of the tokens available from the previous acquirer moved in about one week.
Acquirer isolation through the interface in seconds, with eComCharge support watching response times.
A rolling reserve for each shop and payment method, and payout limits by acquirer and currency.
Financial reconciliation of transactions against bank statements in FinStatHub.
A software-as-a-service installation of eComCharge takes from 1 week and an installation on your own servers from 3 months.
eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
A multi-acquirer strategy is a plan for processing your merchants' card payments through two or more acquirers. It decides how many acquirers you contract, which merchants each may take, how volume is split and which acquirer takes over when another stops, so that losing one acquirer slows your business instead of stopping it.
Because the acquirer carries the card scheme liability for your merchants. High disputes or fraud, a failed underwriting review, a scheme monitoring programme, a change in the acquirer's risk appetite or a scheme prohibition can all end the relationship. Visa requires a payment facilitator agreement to give the acquirer the right to terminate immediately for good cause or at Visa's request.
Two is the minimum for any protection: a primary and a backup that already carries live traffic. Add a third when the backup's caps cannot absorb the primary's volume, or when a country, currency or high-risk segment needs its own acquirer. Each extra acquirer adds a contract, a reserve, a settlement file and an audit.
The strategy is the business decision: which acquirers you sign, what each may accept and how volume is split. Multi-acquirer routing carries it out: the gateway's rules pick a connection for each payment and fail over when one stops. Our payment routing guide covers the rules.
Yes, when the tokens are held by your gateway or are network tokens. Tokens in an acquirer's vault can move only if that acquirer releases them: in one eComCharge case, a high-risk PSP that lost its acquirer overnight moved 95% of the available tokens to a new acquirer in about one week, and recurring payments continued.
Only openly. An acquirer must list a merchant terminated for cause, such as for excessive disputes, on the Terminated Merchant File known as MATCH, and in some regions on Visa's screening service. Disclose the termination to the next acquirer and let it decide. Changing merchant data to escape Visa monitoring can bring penalties and permanent disqualification.
Keep card data, tokens, risk rules and reporting in one gateway for all acquirers, so each acquirer audits the same controls and your PCI DSS scope does not grow with every new connection. Run one risk policy and add each acquirer's stricter rules on top, and reconcile every acquirer's settlement files in one tool.
It depends on how many acquiring connections you need, your volume and your deployment model, plus the reserves and fees each acquirer sets in its own contract. On eComCharge, Smart Routing with sequential fallback is a module of the platform. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
Respectfully, the eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
How PSPs and acquirers process high-risk card payments: which merchants count as high risk, who carries the liability, Visa VAMP thresholds, reserves and limits, the gateway features you need, multiple acquirers and the risks.
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, cost drivers and a 9-step launch plan.
How PSPs, acquiring banks and EMIs onboard high-risk merchants: which MCCs count as high risk, the KYB, UBO and sanctions checks EU law requires, underwriting and reserves, Visa registration and monitoring, what to automate and how to keep an evidence trail.
A guide to cascading payments for PSPs and acquiring banks: soft, hard and technical declines, which Visa response codes may cascade, cascade design, duplicate-charge prevention, 3DS, scheme rules, recovery KPIs and who should not cascade.
A guide for PSPs, banks and platforms on custom payment solutions: custom build vs off-the-shelf vs white-label, what can be customised, how a connector or payout flow is scoped and delivered, what drives cost and time, and the risks.
The four types of payment tokenization service provider for PSPs and banks, network vs gateway tokens, token portability and migration, PCI DSS scope, and the questions to ask before you choose.