Restaurant & Hospitality Group Payments: EPOS, Fees and Multi-Site Payment Strategy

Restaurant & Hospitality Group Payments: EPOS, Fees and Multi-Site Payment Strategy

A hospitality group does not have a card-machine problem.

It has a payments estate.

A customer might reserve a table online, pay a deposit, order drinks at the bar, settle the bill on a handheld terminal, add a discretionary service charge and use a gift card — all during one visit.

Across a larger group, payments might also arrive through:

restaurants → bars → hotels → spas → events → online ordering → delivery → booking systems → payment links

Behind those transactions could sit several EPOS platforms, booking systems, merchant accounts, acquiring relationships and bank settlements.

For a single restaurant, some of that complexity can remain invisible.

For a group processing millions of pounds each year, it cannot.

The C-suite question is no longer:

“What card rate are we paying?”

It is:

“Is our entire payments estate structured efficiently?”

That means looking at processing costs, EPOS restrictions, integrations, reconciliation, authorisation performance, service charges, property structure, online channels and future growth together.

This guide is primarily written for restaurant groups, pub and bar groups, multi-site hospitality operators, hotel groups with significant food-and-beverage operations and established hospitality brands processing substantial card volumes.

For the wider enterprise picture, see our High-Volume Merchant Processing guide and Payments Strategy Library.

Find Your New Processor

Quick Summary

For a multi-site hospitality business, payment-provider selection should not be based on the headline card rate alone.

A proper review should consider:

• total group processing volume;

• effective payment cost;

• EPOS and payment-provider compatibility;

• card-present and card-not-present transactions;

• booking deposits and card guarantees;

• table-side and handheld payments;

• restaurant, bar, spa and hotel integrations;

• online ordering;

• delivery channels;

• events and private dining;

• tips and service charges;

• gift cards;

• international and commercial cards;

• merchant accounts by site or legal entity;

• group-level versus site-level settlement;

• reconciliation;

• payment resilience during service;

• authorisation rates;

• multiple acquirers; and

• whether the current structure will support future sites and acquisitions.

For larger groups, aggregated processing volume can also materially change the commercial conversation with payment providers.

But lower rates only create value if the payment technology still works properly across the operation.

The right hospitality-payment strategy therefore sits at the intersection of:

EPOS + payments + operations + finance + guest experience.

A Hospitality Group Has a Payments Estate

Imagine a restaurant group operating 40 sites.

On one Saturday evening, customers might pay through:

At group level, finance then needs to answer:

Which site generated the transaction?

Which channel generated it?

Which fee applied?

Which bank account received settlement?

Did the EPOS record agree with the PSP record?

How much represented food and drink?

How much represented tips or service charge?

Was the transaction refunded?

Which legal entity owns the revenue?

That is why payment strategy at scale needs to be reviewed as an estate, not as a collection of terminals.

EPOS Can Quietly Determine Your Payment Strategy

For hospitality businesses, this is one of the most important questions to establish early.

What payment providers can your EPOS actually support?

Modern hospitality platforms can combine:

• ordering;

• kitchen management;

• reservations;

• online ordering;

• loyalty;

• reporting;

• payments;

• handheld devices; and

• multi-location management.

Toast's current UK platform, for example, combines restaurant POS, integrated payments, online ordering, handhelds and multi-location functionality within the same ecosystem.

See Toast's current UK restaurant platform

Oracle's Simphony platform similarly connects hotel and restaurant POS environments, mobile ordering and payment functions, including the ability for hotel F&B charges to post through to OPERA Cloud.

See Oracle Simphony for hotel and restaurant POS

For an operator, tight integration can be extremely useful.

But it raises an important strategic question:

How much freedom do we retain over the underlying payment provider?

Before changing EPOS — or before accepting an EPOS renewal — a hospitality group should understand whether the platform:

• requires its own payment-processing product;

• supports selected third-party providers;

• allows different acquirers;

• charges additional fees for external integrations;

• ties hardware to one payment service;

• supports token portability; and

• allows the payment relationship to change without replacing the operational software.

A cheaper EPOS proposal can be significantly less attractive if it also commits the group to payment economics that become expensive at scale.

Equally, a theoretically cheaper PSP is no use if integrating it creates operational problems across 40 restaurants.

EPOS procurement and payments procurement should therefore speak to each other.

Find Your New Processor

The £20 Million Question Is Not “What Rate Can We Get?”

Suppose a hospitality group processes £20 million annually.

A difference of:

0.10 percentage points

across £20 million of volume is:

£20,000 per year.

At £50 million:

£50,000 per year.

That makes pricing important.

But this is where payment reviews can go wrong.

The headline rate is only one part of the effective cost.

A hospitality group's payment costs may include:

• interchange;

• card-scheme fees;

• acquirer or processor margin;

• gateway fees;

• terminal costs;

• authorisation fees;

• premium or commercial cards;

• international cards;

• card-not-present pricing;

• MOTO;

• chargebacks;

• refunds;

• PCI-related charges;

• platform charges; and

• integration costs.

A group should therefore establish its true effective payment cost before deciding whether a provider is expensive.

Our guide to how high-turnover businesses audit payment fees explains how to break those costs down.

For groups reviewing pricing structure itself, see when high-turnover merchants should consider IC+ or IC++.

Use the Group's Volume - But Don't Assume Every Site Needs One Merchant Account

This distinction matters.

A hospitality group may want to negotiate commercially using its total processing estate.

But that does not necessarily mean every venue should process under one merchant account or receive funds into one bank account.

A group may contain:

• several legal entities;

• different trading companies;

• franchises;

• managed properties;

• joint ventures;

• hotels with separate F&B entities; or

• businesses in different countries.

The payments structure needs to reflect who is actually selling the goods or services.

At the same time, the group should understand whether its aggregate scale is being recognised when commercial terms are agreed.

A sensible group-level review therefore separates two questions:

What is our combined negotiating position?

from:

How should settlement and merchant accounts actually be structured?

They are related, but they are not the same thing.

The MAS Hospitality Payments Estate Map

For a multi-site operator, we would first map the estate before comparing providers.

The exercise is deliberately operational.

The estate

How many:

• sites;

• brands;

• legal entities;

• countries;

• merchant accounts;

• bank accounts; and

• payment providers

are involved?

The channels

Where can the guest pay?

For example:

table → bar → website → app → booking → event → delivery → hotel room → spa

The technology

Which systems touch the transaction?

For example:

EPOS → booking platform → terminals → gateway → acquiring → finance → payroll/tronc

The economics

For each major channel:

volume → card mix → pricing model → effective cost → settlement

The failure points

Where does manual intervention still happen?

For example:

• rekeying a payment;

• matching deposits;

• reconciling delivery orders;

• posting room charges;

• tracking refunds;

• allocating tips;

• combining site reporting; or

• resolving mismatched settlement.

MAS View

A payment review should look for friction and leakage as well as fees.

Saving £30,000 in processing costs can be attractive.

Saving £30,000 while creating another £50,000 of operational complexity is not.

Find Your New Processor

Table-Side Payments Are an Operational Decision, Not Just a Hardware Choice

Hospitality has moved far beyond the fixed till.

Customers can now pay through:

• handheld terminals;

• phones;

• QR codes;

• kiosks;

• payment links;

• apps; and

• conventional countertop terminals.

Modern restaurant systems increasingly combine ordering and payment on the same handheld device.

Toast's UK POS, for example, currently allows staff to take both orders and payments at the table, while its platform also supports online, collection and delivery transactions through the same broader restaurant environment.

See Toast's current tableside and restaurant POS functionality

For a larger operator, the important question is not whether tableside payment is available.

It is whether it improves:

• table turnover;

• payment accuracy;

• staff workflows;

• guest experience;

• tip capture;

• reporting; and

• reconciliation

without creating an overly restrictive payment relationship.

Friday at 8pm Is Part of Your Payment Strategy

For a high-volume ecommerce business, a payment outage is serious.

For a hospitality group in the middle of Saturday-night service, it is operationally immediate.

Queues form.

Tables cannot close.

Staff start looking for manual workarounds.

Guests become frustrated.

The payment review should therefore include:

What happens when the internet goes down?

What happens when a terminal fails?

What happens when the PSP is unavailable?

Can transactions continue offline?

How quickly can replacement hardware be deployed?

What support is available during evenings and weekends?

Some hospitality POS systems specifically support offline workflows because service continuity matters so much in this environment.

Resilience may therefore justify a higher cost than an apparently cheaper arrangement that creates more operational risk.

For very large estates, this can also lead to the question of whether relying on one payment route across every venue is appropriate.

Restaurant Bookings Have Become a Payments Channel

A restaurant reservation used to represent a name, date and time.

Increasingly, it can also represent a payment event.

Booking platforms can now support:

• deposits;

• prepayment;

• card guarantees;

• cancellation policies;

• no-show fees; and

• paid experiences.

OpenTable's current UK restaurant guidance, for example, promotes deposits, card holds and prepayment as tools restaurants can use around reservations and large-party dining.

See OpenTable's 2026 restaurant booking trends

That means the hospitality group's payment architecture needs to connect:

booking → payment → EPOS → guest visit → final bill → refund if required

Where booking payments sit in a completely separate payment environment, finance and operations may end up manually reconciling reservation deposits against restaurant bills.

For a deeper review of these flows, see our Payment Providers for Booking Systems guide.

Private Dining, Events and Large Parties Create Another Payment Journey

Restaurant groups increasingly have revenue streams that sit somewhere between ordinary table bookings and corporate invoicing.

Examples include:

• private dining rooms;

• weddings;

• Christmas parties;

• corporate events;

• large group bookings;

• venue hire; and

• tasting experiences.

Payments may be taken as:

initial deposit → staged payment → final balance → extras

rather than one restaurant bill.

That creates requirements around:

• payment links;

• card-not-present transactions;

• deposit tracking;

• partial refunds;

• invoice reconciliation;

• stored credentials; and

• final settlement.

The payment system should ideally connect those transactions to the relevant event or booking rather than leaving finance to identify them manually.

Tips and Service Charges Are Now a Payments-Data Issue

For hospitality groups, tipping legislation makes accurate payment and EPOS reporting particularly important.

The UK's statutory Code of Practice on the fair and transparent distribution of tips came into effect on 1 October 2024.

Where qualifying tips, gratuities and service charges fall within the legislation, employers must allocate them fairly and transparently and maintain relevant records.

Importantly for multi-site groups, the existing statutory code deals with tips according to the place of business to which they are attributable.

Read the current statutory tipping code

The legislation is also explicit that the total qualifying amount is intended to be available for workers; deductions such as card-processing or administrative charges cannot simply be taken out of the qualifying tip pool.

Read the explanatory notes to the Employment (Allocation of Tips) Act 2023

For a hospitality group, that means systems should be able to distinguish clearly between:

food/drink sale

mandatory service charge

discretionary service charge

customer gratuity

and attribute relevant amounts to the right location.

A restaurant group processing tips through terminals but unable to report them cleanly by venue has a systems problem as well as an HR/payroll problem.

Tipping Rules Are Still Developing in 2026

This is an area hospitality groups should keep under review.

As of 24 August 2026, the Government has an open consultation on a revised statutory tipping code following changes introduced through the Employment Rights Act 2025.

The proposed changes include additional requirements around consulting workers when developing or revising written tipping policies.

The consultation opened on 19 August 2026.

The Government has stated that businesses should continue following the existing statutory code while this process continues.

Read the August 2026 tipping-code consultation

MAS is not an employment-law or tax adviser, but these developments matter to payment strategy because EPOS and payment reporting are often the source data from which hospitality groups calculate and reconcile card-paid tips and service charges.

Find Your New Processor

Restaurant Payments Inside a Hotel Group Need to Work Differently

A restaurant operating inside a hotel creates another layer of complexity.

The diner might:

pay at the table

or:

charge dinner to Room 512.

Those two journeys can ultimately settle through different payment processes.

Oracle's current Simphony hotel POS architecture, for example, can integrate with OPERA Cloud so food-and-beverage charges can be posted directly to a guest room and consolidated into the hotel bill.

See Oracle's hotel restaurant POS architecture

That ability is operationally important.

The restaurant system needs to know:

which guest → which room → which property → which folio

before the guest pays later through the hotel payment flow.

Hotel groups with restaurants, bars and spas therefore need to review those systems together.

See our Hotel Group Payment Strategy guide for the wider multi-property architecture.

Don't Ignore Online Ordering Because It Isn't the Main Revenue Channel

For some hospitality groups, digital ordering remains a relatively small percentage of turnover.

That does not mean it should sit outside the payments review.

Online transactions can arrive through:

• the group's own website;

• branded app;

• click and collect;

• QR ordering;

• delivery marketplace;

• event booking;

• gift-card purchase; or

• mobile table ordering.

The economics can differ considerably from in-venue card-present payments.

They may involve:

• different payment pricing;

• different fraud exposure;

• alternative payment methods;

• digital wallets;

• separate settlement; and

• a different customer-data relationship.

A group should therefore analyse channel economics, not just overall payment volume.

If you operate a multi-location retail business rather than restaurants or hospitality venues, see our Multi-Location Retail Merchant Services guide.

Delivery Platforms Should Not Be Confused With Your Own Payments Estate

Third-party delivery platforms can make reporting particularly confusing.

Where a marketplace collects payment from the customer and later settles money to the restaurant, that payment may not operate through the restaurant group's own acquiring arrangement at all.

Finance therefore needs to separate:

payment volume processed directly by the group

from:

revenue settled by marketplace or delivery partners.

This distinction matters when:

• calculating total card-processing volume;

• negotiating PSP rates;

• reconciling revenue;

• analysing payment fees; and

• deciding whether direct ordering should be expanded.

A £30 million hospitality business may therefore have considerably less than £30 million of directly addressable card-processing volume.

Understanding that number should come before negotiating with acquirers.

Should Every Site Use the Same Payment Provider?

For many hospitality groups, standardisation has obvious appeal.

One provider can mean:

• common terminals;

• common integrations;

• consolidated reporting;

• one commercial agreement;

• consistent support;

• easier deployment to new sites; and

• stronger volume leverage.

But standardisation should not be confused with dependency.

The group should still understand:

• whether the EPOS can support another provider;

• whether tokens are portable;

• whether merchant accounts can move;

• whether international expansion changes the requirement;

• whether specialist business units need something different; and

• how difficult it would be to introduce resilience later.

For large estates, the relevant question may become:

“Should we have one preferred payment architecture but retain the ability to use more than one acquirer?”

Our guide to acquirer-agnostic payment gateways and multiple acquirers explains that structure in more detail.

Can Better Authorisation Rates Matter to Hospitality Groups?

Yes, particularly where a group has substantial:

• online bookings;

• international customers;

• digital ordering;

• events;

• card-on-file payments; or

• card-not-present transactions.

A cheaper transaction rate does not compensate for legitimate transactions being unnecessarily declined.

Larger hospitality businesses should consider analysing authorisation by:

• channel;

• card geography;

• card type;

• property;

• transaction type; and

• payment provider.

A single group-wide authorisation rate can hide meaningful differences.

For more detail, see How Enterprise Merchants Improve Payment Authorisation Rates.

What Should a Hospitality CFO Actually Ask for?

A payment tender or review should provide more than a price per transaction.

A CFO should be able to see:

Processing economics

What is the effective cost across the group's actual card mix?

Site economics

Are particular venues or channels disproportionately expensive?

Integration cost

What needs to change in EPOS, booking systems or terminals?

Settlement

Can settlement be structured correctly by site and legal entity?

Reporting

Can finance see group-level information while retaining site-level detail?

Resilience

What happens if payments fail during peak service?

Portability

How difficult would another provider change be in future?

Growth

Can the architecture support another 20 venues without starting again?

The lowest transaction quote does not necessarily provide the best answer to those questions.

Before Switching Provider, Map Every Payment Dependency

For hospitality groups, switching payment provider can affect far more than the terminal estate.

Map:

EPOS

handhelds

fixed terminals

booking systems

online ordering

gift cards

loyalty

payment links

stored cards

hotel PMS

spa systems

event software

tips/service-charge reporting

refunds

finance

bank settlement

A payment provider switch becomes risky when one of these dependencies is discovered too late.

This is why larger groups should ideally start reviewing the payment estate well before a contract renewal or EPOS migration deadline.

How Merchant Advice Service Looks at Hospitality Payments

Merchant Advice Service does not approach a multi-site hospitality group by immediately producing a list of payment providers.

We first need to understand how the estate works.

That means looking at:

where payments happen

which systems are involved

how much volume sits in each channel

where the money settles

what the current arrangement costs

and

what the group intends to change over the next few years.

A restaurant group opening five sites annually needs a different answer from a mature 60-site estate trying to consolidate suppliers.

A hotel group operating restaurants and spas has different requirements from a pure restaurant chain.

A hospitality SaaS platform has a different opportunity again because it may be able to monetise payments across its customer portfolio.

The potential outcome of a review could therefore be:

keep the existing provider

renegotiate group pricing

change pricing structure

consolidate fragmented merchant arrangements

change EPOS/payment architecture

introduce another acquirer

or

switch payment provider.

The provider should follow the requirement, rather than determine it.

You can read more about How Merchant Advice Service Works, How MAS Researches and Compares Payment Providers and the wider Payments Strategy Library.

Sources & Further Reading

This guide has been informed by current UK legislation and guidance, hospitality technology documentation and Merchant Advice Service research into enterprise payment infrastructure.

UK Government — Statutory Code of Practice on Tips

The current statutory code came into effect on 1 October 2024 and sets out requirements around fair and transparent allocation of qualifying tips, gratuities and service charges, including record-keeping and place-of-business considerations.

Read the statutory code

Employment (Allocation of Tips) Act 2023

The legislation requires qualifying tips to be allocated fairly and includes provisions intended to ensure the full qualifying amount is available to workers rather than reduced by items such as bank or administrative charges.

Read the legislation and explanatory notes

HMRC — Tips, Gratuities, Service Charges and Troncs

HMRC guidance covers the tax and National Insurance treatment of different forms of tips and service charges.

Read HMRC guidance

UK Government — Revised Tipping Code Consultation 2026

A new consultation opened on 19 August 2026 covering proposed revisions to the statutory tipping code, including further worker-consultation requirements.

Read the 2026 consultation

Oracle Hospitality — Simphony Hotel and Restaurant POS

Oracle's current hospitality architecture demonstrates integration between food-and-beverage POS, mobile ordering, payments and OPERA Cloud room accounts.

Read about Oracle Hospitality Simphony

Toast — UK Restaurant POS and Multi-Location Payments

Toast's current UK restaurant platform provides an example of integrated POS, handheld payments, online ordering, reporting and multi-location hospitality management.

View Toast's UK restaurant POS

OpenTable — Restaurant Booking Payments

OpenTable's current 2026 restaurant materials demonstrate booking models involving prepayment, deposits and card holds for reservations and large groups.

View OpenTable's 2026 restaurant insights

Related Merchant Advice Service Guidance

• Payments Strategy Library

• High-Volume Merchant Processing

• How High-Turnover Businesses Audit Payment Fees

• When High-Turnover Businesses Should Consider IC+ or IC++

• How Enterprise Merchants Improve Payment Authorisation Rates

• Payment Providers for Booking Systems

• Hotel Group Payment Strategy

• Acquirer-Agnostic Payment Gateways

• Embedded Payments for SaaS and Platforms

Find Your New Processor

Editorial and Commercial Disclosure

Merchant Advice Service is an independent payments information, comparison and provider-matching service.

MAS may receive commission or a referral fee from some payment providers where a business chooses to proceed following an introduction. This does not determine the factual information or provider capabilities included in this guide.

Providers and hospitality-software companies have not paid for inclusion in this article unless explicitly stated.

Providers, EPOS platforms, booking systems and hospitality technology companies named within this article are examples used to illustrate payment and integration requirements. They do not represent a complete whole-of-market list, ranking or recommendation.

Payment functionality including EPOS integrations, booking deposits, card guarantees, offline processing, tokenisation, table-side payments, room charging, multi-acquirer support and site-level settlement varies between providers and software configurations.

Hospitality-software and payment integrations can change. Compatibility should always be confirmed against the specific software version, hardware, location, integration and payment provider before a contractual decision is made.

The information relating to tips, gratuities and service charges is general payments information and does not constitute employment, payroll or tax advice.

Merchant Advice Service does not make underwriting decisions or guarantee merchant-account acceptance.

Payment-provider capabilities, hospitality-software integrations, employment requirements, card-network rules, pricing and underwriting criteria can change. This guide provides general information and should not be treated as legal, tax, employment, regulatory or financial advice.