Hotel Payment Gateway

A payment gateway is the service that collects a guest's card, digital wallet or bank details at booking, confirms the charge and sends the booking through. The PCI Security Standards Council files the term under payment processor, together with payment service provider (PSP) (Stripe: Hospitality payment processing) (PCI SSC Glossary: Payment Processor).

Last updated: November 2026

How a payment gateway works in a hotel

When a guest books on the hotel's website or booking engine, the gateway encrypts the card data and passes it to the payment processor (Stripe: Hospitality payment processing). The card data it carries is, at a minimum, the full card number, plus the cardholder name, expiry date or service code when present (PCI SSC Glossary).

From there the request follows the card network's path. The hotel's acquirer asks the network, Mastercard for example, to get an authorization from the guest's issuing bank, which approves or declines the transaction and routes the response back to the merchant. Later, the issuing bank routes the payment to the acquirer, which deposits it into the merchant's account (Mastercard: How Credit Card Transactions Work).

Card data can also be tokenized. Tokenization removes the card number, the data most valuable to a fraudster, and replaces it with a unique alternative value, a payment token, that should not be usable beyond a specific merchant, device or payment scenario (EMVCo: EMV Payment Tokenisation).

Hotels often authorize a payment in full before the guest arrives, then capture the money when the guest checks out, a split sometimes called manual capture (Stripe Docs: Place a hold on a payment method). For how long a hold can last and when it should be released, see pre-authorization hold.

Why the payment gateway matters for hotel distribution

Booking.com offers properties three payment models: Payments by Booking.com, where Booking.com handles the payment and pays the property out; payment at the property, where the property collects; and Smart pay at property, where the guest pays at the property and Booking.com charges the guest and pays the property for no-shows and cancellations (Booking.com Connectivity Docs: Managing payment and payout details). Under Payments by Booking.com, the hotel's own gateway only has to charge the payout, which can arrive as a virtual credit card. When the property's PMS or channel manager has Booking.com's Virtual Credit Card Payments Clarity Package integrated, that system shows the card's activation date, current balance and expiry date. If the hotel's point-of-sale system cannot charge such a card online, Booking.com points the hotel to its payment service provider, which may be able to offer one that can (Booking.com for Partners: Guide on using virtual credit cards effectively).

For bookings the hotel collects itself, card payments can also run through the property management system. In Oracle's OPERA Cloud PMS, for example, the Oracle Payment Interface sits between OPERA Cloud and the payment service providers that issue and manage card tokens, and gives users a single interface for card acceptance. At a tokenized property, staff see only masked digits, such as the last four. When a guest makes a payment after check-in at the front desk by chip and PIN, a successful transaction returns a token, the card type, the expiry date and the last four digits to OPERA Cloud, and the payment applies to the guest folio. A property that does not use tokenization has no such connection to a payment service provider and keeps card data, typically masked, in OPERA Cloud's own card fields (Oracle Hospitality Payment Interface Cloud Service User Guide, Release 25.3). For the wider split between OTA-collected and hotel-collected payments, see merchant model vs agency model.

Payment gateway compared with processor, acquirer and virtual card

 What it isWhere it sits in a hotel payment
Payment gatewayThe service that takes the guest's card details and sends them to the processorConnected to the hotel's website, booking engine or PMS
Payment processor or payment service provider (PSP)An entity a merchant engages to handle card transactions on its behalfReceives card data from the gateway
Acquirer (merchant bank)The financial institution that processes card transactions for merchantsBound by the card brands' rules on merchant compliance
Virtual credit card (VCC)A temporary digital Mastercard that Booking.com uses as a payout method on Payments by Booking.comCharged like a regular credit card through the hotel's own point-of-sale system

Gateway row: as the definition above. Processor row: PCI SSC Glossary: Payment Processor. Acquirer row: PCI SSC Glossary. Virtual card row: Booking.com for Partners: Guide on using virtual credit cards effectively.

Frequently asked questions

What is a payment gateway?
For a hotel, it is the link between the website, booking engine or PMS where a guest pays and the hotel's acquirer, or merchant bank. The guest does not always type card details into the hotel's own page. In Oracle's OPERA Cloud PMS, for example, staff can send a reservation's deposit request to the payment service provider as a pay-by-link request, email the guest the payment link and check the payment status at check-in.
How do you choose a payment gateway for a hotel?
Check three things. First, that it plugs into the property management system and booking engine the hotel already runs. Second, that it can charge OTA virtual cards; Booking.com asks properties not to pre-authorize them. Third, that the hotel's merchant account is registered as an accommodation provider. Without that registration, a Booking.com virtual card cannot be charged.
Does PCI DSS apply to a hotel that uses a payment gateway?
PCI DSS, the security standard from the PCI Security Standards Council, applies to any entity that stores, processes or transmits cardholder data or sensitive authentication data. That covers the gateway and any booking page, phone line or front desk at the hotel that takes a card number and passes it on.
How do guests feel about giving card details by phone?
26% of travelers said they would not book with a hotel again if it asked for their card details over the phone, yet 47% of hotels still took card payments by phone, according to an Adyen survey reported in January 2025. The same survey found that one in 10 hotel guests had been a victim of payment fraud when booking a hotel or as a consequence of staying there, and those who were lost GBP 564.08 on average in 2024.

Where Jetstream fits

The bookings a gateway charges come from the hotel's own website and from each OTA it sells on. Jetstream builds an AI channel manager that connects a property's systems to the channels where guests book, and keeps rooms, rates and availability accurate on each one, managed from one place.