Hotel POS System and Payment Gateway: the Complete Guide

A hotel processes payments across channels that most merchants never touch: pre-authorized deposits at check-in, extra charges during the stay, charges from a property management system (PMS), payment links sent before arrival, and a physical reception terminal. This guide explains how a hotel payment setup works end to end, which PMS integrations matter, what pre-auth and 3DS2 rules apply, and how pricing models compare.

Hotel POS Systems and Payment Gateway: Full 2026 Guide

Why Hotels Need a Payment Setup Unlike Any Other

Pre-authorization (pre-auth): at check-in the hotel blocks an amount on the guest card to cover extras such as minibar, room service or damages. The card schemes set the limit: Visa allows pre-auth for up to 31 days, Mastercard up to 30 days.

Card on file and tokenization: returning guests are charged with a card token, not the raw card data. Storing tokens needs a PCI DSS compliant infrastructure.

PMS integration: the Property Management System is the core of the hotel: reservations, folios, charges and settlement run on it. The POS or gateway must sync with it.

Multi-channel payments: payment links by email or SMS before arrival, online check-in with a card, a terminal at reception and payment in the hotel app: all channels must reconcile in the PMS.

Refund flows: cancellations, no-shows and partial refunds need full and partial refund support with automatic reconciliation in the PMS.

PMS Integrations: the Most Common Systems

Opera (Oracle Hospitality): the standard for 4-5 star hotel chains. Integration runs on RESTful APIs and typically takes 1-2 working days with the hotel IT team.

Mews: the cloud-native PMS preferred by boutique and urban design hotels. Native payments integration.

Cloudbeds: widely used by B&Bs, hostels and independent properties.

Protel: common among business hotels and resorts in Europe.

Little Hotelier: built for small properties such as B&Bs. A payment link or terminal setup is usually enough for these structures.

Pre-Authorization Step by Step

1. Check-in: the terminal or the integrated gateway blocks the chosen amount (for example 200 euro for a business stay).
2. During the stay: the block stays active while the guest uses the services of the hotel.
3. Check-out: the system executes a capture for the final amount (stay + extras). The difference versus the original pre-auth is released by the issuing bank within 3-5 days.

For no-show bookings, the capture of the pre-authorized amount follows the cancellation policy the guest accepted. If no pre-auth exists, charging the card relies on the stored credentials or a retry of the [payment link](/en/resources/pos-costs-fees-commissions-hidden-charges).

3DS2 and What PSD2 Means for Hotels

3D Secure 2 is mandatory for online payments under PSD2. For hotels the rules split into three cases:

- Direct online bookings: 3DS2 applies to the cardholder-initiated transaction.
- Later charges on a stored card: these follow-on charges should be flagged as Merchant Initiated Transactions (MIT) which are exempt from a new 3DS2 challenge because the cardholder is not actively involved during the stay.
- Payments at reception: face-to-face terminal transactions are outside the scope of 3DS2.

An optimized 3DS2 flow reduces false declines: direct bookings abandoned because of a challenge are revenue lost to the OTA channels.

Costs: Flat Rate vs IC++ for Hotels

Hotels carry a card mix with a high share of international and business cards (Visa Corporate, Mastercard Business, Amex), and business cards are outside the IFR interchange caps. That is why per-card pricing matters:

Flat rate 1.5%, 150,000 euro per month: 2,250 euro per month in fees.

RoxPay IC++: €0.15 + 0.35% to 0.85% (IC++).

With a seasonal leisure resort at 250,000 euro per month, a flat 1.4% bank contract means 3,500 euro per month, while IC++ follows the real cost of every card used.


Frequently Asked Questions

How does the payment system integrate with Opera PMS?

Integration runs through a RESTful API module and typically takes 1-2 working days with the hotel IT team and the provider support. Once live, charges, refunds and settlement post directly into the guest folio.

How long does a hotel pre-authorization last?

Visa allows pre-auth for up to 31 days and Mastercard up to 30 days. For longer stays the gateway must run a renewed pre-auth, otherwise the block expires and the funds return to the guest.

Can foreign guests pay in their own currency?

Yes, with Dynamic Currency Conversion (DCC) the guest pays in their home currency at the reception terminal or in the online checkout. Contract terms for DCC margins depend on the acquirer agreement.

How are no-show charges handled?

If the booking was guaranteed with a pre-auth, the gateway captures the agreed no-show fee. If only card data was stored without a pre-auth, the charge runs as an MIT transaction on the token and depends on the issuing bank.

What does a hotel POS system cost per month?

There is no single number: the per-transaction cost depends on the card mix. With interchange caps of 0.20% on EU consumer debit and 0.30% on EU consumer credit (IFR Regulation), a transparent IC++ contract prices a mostly-debit hotel card mix near the lower end of the range.

Get started today

Optimize your payments today

Integrate RoxPay with your hotel PMS and accept payments directly from the property management system. Talk to an expert on /en/contact.

✓ No monthly fixed costs · ✓ Activation in 24 hours · ✓ Dedicated technical support