Knowledge Base

Multi-acquirer setups for travel businesses.

A practical guide to multi-acquirer setups in travel — when adding a second acquirer makes sense, how to route transactions intelligently, how reserve and underwriting differ across acquirers, how reconciliation works across MIDs, and the operational picture inside a booking-level ledger.

Book a walkthrough See reconciliation

Acquirersrouted by rule

Reservestracked per MID

Reconciliationunified by booking

Why travel businesses run multiple acquirers.

Most travel businesses start with a single UK card acquirer because that is the simplest setup. As the business scales, three forces typically push toward a second acquirer: resilience against acquirer-side downtime or repricing, optimisation across transaction types, and access to international or currency-specific acquiring that the primary cannot provide. The decision is rarely a single moment - it builds up across several conversations.

Resilience and leverage

A single acquirer is a single point of failure for the entire card book. A second acquirer is leverage at renegotiation time and an insurance policy against an unexpected reprice or restriction.

Mix and price optimisation

Different acquirers price different transaction types differently. Routing premium-card transactions to the acquirer with the better premium-card rate, and standard transactions elsewhere, can shave meaningful basis points off the effective rate.

International and multi-currency

A UK acquirer is the right answer for sterling transactions on UK cards. International acquiring, EUR-denominated transactions, or specialised local methods often need a second acquirer to serve cleanly.

Section 01

How to decide when to add a second acquirer.

Adding an acquirer is operational work. The reconciliation surface doubles, the reporting picture gets more complex, and the team has another relationship to manage. The right time to add one is when the economic or resilience case clearly outweighs that operational cost.

When the reprice would hurt

If the primary acquirer raised the merchant''s effective rate by 30 basis points tomorrow, what would the alternative be? Operators with no alternative pay the full reprice; operators with a warmed-up second relationship usually do not.

When the resilience case is clear

A travel merchant that processes through a single acquirer and experiences a 24-hour acquirer outage during a sales peak loses customers it does not recover. The second acquirer is the insurance.

When mix or currency justifies it

A clear premium-card mix that another acquirer prices materially better, or a multi-currency book that needs international acquiring, gives the second-acquirer decision a positive ROI from day one.

How to route transactions across acquirers intelligently.

Routing is what makes a multi-acquirer setup worth its operational cost. Smart routing puts each transaction through the acquirer that gives the best outcome on rate, authorisation rate or resilience grounds. Routing badly - or not routing at all - means running multiple acquirers without the benefits.

Route by card type, scheme and BIN

The starting point for any routing logic is card-type and BIN-level data. Some acquirers price premium cards better; some price Amex differently from Visa and Mastercard; some have better cross-border pricing. Layering the routing decision on top of these segments often delivers the biggest direct cost saving.

Premium cards Per acquirer

BIN Routing input

Scheme Routing input

See card issuer in the glossary

Route by authorisation outcome

Authorisation rates can vary materially across acquirers for similar transaction segments - sometimes because of different fraud screening, sometimes because of issuer-side relationships, sometimes because of network configuration. Routing the segment with the higher authorisation rate to the acquirer with the better outcome converts more transactions into revenue.

Auth rate gap Measured per segment

Routing decision Recovery-led

Review cycle Monthly

See payment optimisation

Route by resilience and load

Even with a primary acquirer working perfectly, distributing some volume to a second acquirer maintains the relationship and keeps the secondary path warm. During a primary-acquirer incident, immediate failover to the secondary keeps payments flowing - which during a sales peak can be the difference between hitting the quarter and missing it.

Primary Default

Secondary Warm

Failover Automatic

See dynamic routing in the glossary

Section 03

How reserves and underwriting differ across acquirers.

Two acquirers underwriting the same travel merchant rarely arrive at the same answer. Reserve sizing, holdback policy and exposure limits depend on the underwriter''s read of the merchant''s book, the scheme rules and the acquirer''s own risk appetite.

Rolling reserves vary widely

One acquirer may set a 5% rolling reserve over 180 days; another may set 10% over 90 days; a third may waive it entirely on a long-tenure relationship. The cash-flow impact is material.

Underwriting reads the book differently

Each acquirer sees the merchant''s book through its own risk lens. Holding the same clean evidence for both - chargeback ratios, refund discipline, ATOL or trust evidence, supplier exposure - typically improves both relationships over time.

Settlement timing differs

One acquirer may settle T+1, another T+2, another with a one-day holdback. Reconciliation has to track each cadence independently.

How to reconcile across multiple MIDs and acquirers.

Multi-acquirer reconciliation is where the operational cost gets paid. Each acquirer sends its own settlement files, its own fee structure, its own refund and chargeback workflow. Without booking-level matching, this becomes spreadsheet work that scales linearly with the number of acquirers.

Match each settlement back to bookings

The reconciliation is per-acquirer at the file level and per-booking at the transaction level. With booking-level matching in place, the reconciliation work is the same regardless of how many acquirers are running - because the matching logic looks at the booking, not the acquirer.

Match level Per booking

Files Per acquirer

Effort Constant

See reconciliation

Track fees and refunds per MID

Each MID has its own interchange, scheme fees, processor markup and acquirer margin. Tracking these per MID against the bookings they covered is what reveals the true effective rate per acquirer - and is the foundation for the next renegotiation.

Effective rate Per MID

Fee categories Tracked

Renegotiation Evidence-led

See MDR in the glossary

Surface acquirer-side exceptions

Every acquirer-side event - chargeback, refund adjustment, retrieval request, settlement adjustment - should land against the booking. That surface keeps each acquirer relationship transparent and gives the operator a unified view of acquirer-side service and quality.

Event source Per acquirer

Resolution Per booking

View Unified

See financial control

Section 05

How to keep reporting clean under multi-acquirer.

ATOL APC reporting, trustee reports, audit packs and management accounts all need to handle multi-acquirer cleanly. Done well, it is invisible; done badly, it becomes the most painful reconciliation work in the business.

One booking-level ledger

APC and trustee reporting are booking-level by design. As long as each transaction matches back to its booking - regardless of acquirer - the reporting picture stays clean.

Per-MID rollups for audit

External auditors often want to see per-MID summaries to tie back to acquirer-supplied evidence. Producing these from the booking-level ledger rather than from spreadsheets makes the audit conversation routine.

Consolidated exposure for the trustee

Where the operator runs a CAA-approved trust account, the trustee needs a consolidated picture of customer payments across all acquirers held against protected travel liability. Multi-acquirer must not mean multi-trustee-report.

Section 06

How to make the economic case for multi-acquirer.

The decision usually comes down to four numbers: the rate saving, the resilience value, the operational cost and the leverage at next renegotiation. Each is quantifiable; the operators that get this right write it down rather than relying on instinct.

Rate saving = basis points × volume

If smart routing recovers 20 basis points on £20m of card volume, that is £40,000 of direct margin a year. Compare against the operational cost of running the second relationship.

Resilience value = downtime cost

Estimate the cost of a 24-hour acquirer outage during a peak period. For a sales-driven travel business, this can run into hundreds of thousands. The second acquirer is the insurance.

Leverage at renegotiation

A merchant with a credible second acquirer relationship negotiates from a different position than a merchant with none. The leverage value shows up at every contract review.

Operational cost = team hours plus tooling

The honest cost is the finance team hours, the tooling to keep reconciliation clean, and the relationship management time. With a booking-level ledger, this is bounded; without one, it grows quickly.

What multi-acquirer handling looks like in felloh.

felloh treats each acquirer as another input to the same booking-level ledger. Routing decisions, settlement matching, fee tracking and chargeback handling all live against the booking, not against the acquirer - so adding the second acquirer does not double the operational picture.

See this guide running on your booking data.

Bring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.