Payment Gateway

A payment gateway is the technology service that securely transmits card and other payment data between a hotel's booking engine, PMS or OTA checkout and the payment processor or acquiring bank. It captures the customer's details, encrypts or tokenises them, requests authorisation and returns an approved or declined result in seconds.

How it works

1. The guest enters payment details on the booking page.
2. The gateway encrypts the data and passes it to the processor and card network.
3. The issuing bank approves or declines, often triggering Strong Customer Authentication (SCA) such as 3-D Secure in Europe.
4. The gateway returns the result and stores a token so the hotel can later charge deposits, balances or no-show fees without holding raw card numbers.

Gateway vs processor

A gateway is not the same as a payment service provider (PSP) or acquirer. The gateway is the connection layer; the processor moves the money. Many providers bundle both, but hotels sometimes use a separate gateway to route payments to several acquirers.

Example

A direct booking of €480 requires a 30% deposit. The gateway authorises €144 at booking, stores a token, and charges the €336 balance at check-in, with no card data stored in the hotel's own systems.

Why it matters

A reliable gateway raises conversion rate by reducing failed payments and supports local payment methods. It also limits compliance exposure, since tokenisation helps hotels meet PCI DSS. For OTAs operating under the Merchant Model, gateway performance affects chargebacks and fraud losses.

Related

• PCI DSS and SCA set security requirements.
• Chargeback and VCC (Virtual Credit Card) cover payment disputes and OTA-to-hotel settlement.
• Booking Engine and IBE embed the gateway in the checkout flow.