- PCI DSS is not UK law. The PCI Security Standards Council publishes the standard, and the card brands and your acquirer decide how it is enforced through their programmes and your merchant agreement
- PCI DSS v4.0.1 is the only active version. It replaced v4.0, which retired on 31 December 2024, and its future-dated requirements became effective on 31 March 2025
- Scope follows card data, not the number of tills. What counts is which systems store, process or transmit card data, and which systems connect to them or can affect their security
- Each SAQ has its own eligibility criteria. A hotel with several payment channels may be able to use more than one SAQ, but only where each channel qualifies and your acquirer accepts it
- Outsourcing, tokenisation and segmentation can cut scope a long way, but none of them removes your PCI DSS responsibilities, and the reduction has to be shown and validated
PCI DSS is not UK law, but it is contractually mandatory
The Payment Card Industry Data Security Standard is not an Act of Parliament and no UK regulator enforces it directly. It is an industry standard published by the PCI Security Standards Council, whose founding members are the major card brands. You are bound by it through the agreement you sign with your acquiring bank or payment provider, and each card brand runs its own compliance programme on top.
That is also why there is no single fine schedule. The PCI Security Standards Council does not set penalties; the card brands and acquirers do, under their own rules and contracts. Depending on the programme that applies to you, non-compliance can lead to remediation demands, contractual penalties or extra fees, and in serious cases, particularly after a confirmed card data breach, restrictions on accepting cards or termination of the merchant agreement. For a hotel, losing card acceptance is a far bigger problem than any fee. A card data breach can also trigger separate legal duties under UK GDPR, including reporting to the ICO.
PCI DSS v4.0.1, published in June 2024, is the version that applies today. Version 3.2.1 retired on 31 March 2024, v4.0 retired on 31 December 2024, and the requirements that v4 introduced as future-dated became effective on 31 March 2025. Your acquirer and any assessor will look at your hotel against v4.0.1.
Why scope is more complex in a hotel than a typical retailer
A high street shop usually takes cards at one till. A hotel takes them through several channels, and each one may be built differently:
- Booking engine. Your website or a third-party booking platform takes card details at the point of reservation, sometimes to guarantee against no-shows.
- Front desk. Card-present payments at check-in and check-out, plus card details keyed in for walk-in bookings.
- Restaurant, bar and spa. Each outlet may have its own till, terminal or payment provider.
- Telephone reservations. Staff take card numbers over the phone and enter them into a system, which can bring call recordings and staff screens into scope.
- OTAs and channel managers. Staff may retrieve virtual card details from an online travel agency portal and charge them through the PMS.
- Pre-authorisations and no-show charges. Holding card details for incidentals, deposits or later charges keeps card data in your systems for longer.
PCI DSS scope depends on where card data actually flows: the systems that store, process or transmit it, plus the systems connected to them or able to affect their security. Having many outlets does not by itself put the whole hotel network in scope. A booking engine fully hosted by the payment provider and a standalone terminal in the restaurant may never share an environment. On the other hand, a back-office system that looks unrelated can still be in scope if it can reach the payment environment. Segmentation helps limit scope only when it really isolates the relevant systems, and you have to be able to show that it does.
Before you pick an SAQ, map each channel. These questions cover the usual gaps in a hotel:
| Payment channel | Question to answer |
|---|---|
| Website and booking engine | Do you host the payment form, redirect to the provider, or embed the provider's form in your page? |
| PMS | Does it receive full card numbers, store tokens, show masked cards, or allow manual card entry? |
| Front desk terminals | Are terminals standalone, integrated with the PMS, or managed through another system? |
| Telephone reservations | Where are card details entered, and are calls or screens recorded? |
| Restaurant and spa | Are their payment systems isolated from the hotel network? |
| OTAs and channel manager | Does any system receive or pass on card details or virtual card data? |
| No-shows and pre-authorisations | Who stores the card details, and who authorises the later charge? |
| Refunds and back office | Which systems and users can start or manage payments? |
Merchant levels and which SAQ applies to your hotel
Each card brand sets merchant levels, mainly by annual transaction volume, and your acquirer tells you which level you are and how you must validate. Many independent hotels are Level 4 and can validate with a Self-Assessment Questionnaire (SAQ). Larger hotels and groups may need a Report on Compliance from a Qualified Security Assessor instead.
Each SAQ has eligibility criteria, and you must meet all of them before you can use it. The table shows the usual routes for hotel payment setups. It points to possible SAQs; it does not decide which one applies to you. Confirm the choice with your acquirer.
| Payment setup | Possible SAQ | Main condition |
|---|---|---|
| Online payments fully outsourced to a provider's hosted page or redirect | SAQ A | All eligibility criteria met, including the script-attack criterion added in 2025 |
| Your website does not receive card data but controls how the payment page or its elements are delivered | SAQ A-EP | Depends on who provides and controls each part of the payment page |
| Standalone, PTS-approved terminals connected to the processor over IP | SAQ B-IP | Terminals isolated from other systems, which segmentation can achieve; no electronic storage of card data |
| Standalone dial-out terminals or imprint machines | SAQ B | No electronic storage of card data |
| Staff key card details into a provider's web-based virtual terminal | SAQ C-VT | One transaction at a time on an isolated device, no electronic storage |
| Internet-connected payment application, such as a POS system | SAQ C | Payment application isolated from all other systems; no electronic storage of card data |
| Terminals in a PCI-listed point-to-point encryption (P2PE) solution | SAQ P2PE | Only validated P2PE solutions and devices, used as listed |
| Mixed environment that does not meet a smaller SAQ's criteria | SAQ D, or a Report on Compliance where required | Validation route set by your acquirer and the card brand programme |
SAQ C is often misread. It is for payment application systems connected to the internet, and the payment system must be isolated from your other systems. A POS that also connects to the PMS, the back office or other hotel systems usually falls outside SAQ C. The same goes for SAQ B-IP: the terminals do not need a physically separate network, but they must be isolated from other systems, and a back-office server that manages them breaks eligibility.
A hotel with several channels can sometimes validate each one with a different SAQ, for example SAQ A for the booking engine and SAQ B-IP for the front desk. The PCI Security Standards Council allows this where each channel meets its own SAQ criteria, the channels are properly separated, and your acquirer or card brand accepts it. Where the channels cannot be separated, you may need one combined assessment, usually SAQ D.
The 12 PCI DSS requirements applied to hotel operations
The standard rests on 12 requirement areas, and which detailed requirements apply depends on your scope and SAQ. For a hotel, they cover: network security controls that separate payment systems from guest Wi-Fi and general hotel IT; no vendor default passwords on terminals or back-office systems; protecting any stored card data and never storing the card verification code (CVV/CVV2) after authorisation, a common failure when staff write it down for phone bookings; strong encryption when card data travels over open, public networks; patching, particularly on PMS and point-of-sale software that is often left on outdated versions; access to card data limited by job role; a unique login for every member of staff rather than shared front desk credentials; physical control of card readers, back-office servers and anywhere card data is handled; logging and monitoring of access to payment systems; regular security testing, including penetration testing where your SAQ requires it; and a documented information security policy that covers all staff, including the seasonal and agency workers common in hospitality.
What PCI DSS v4.0.1 requires of hotels
Requirement 8.4.2 extends multi-factor authentication to all non-console access into the cardholder data environment, not only administrative and remote access as before. Whether a front desk PMS login falls under it depends on your architecture. If the PMS sits in the card environment or gives access into it, the rule applies. If the PMS only holds tokens supplied by a payment provider and cannot reach card data, it may not. Check the PMS, POS, admin tools and payment integrations one by one rather than assuming every login is covered. MFA on front desk accounts is good practice either way, even where PCI DSS does not require it.
Requirement 8.3.6 sets a minimum password length of 12 characters for accounts in scope, or 8 characters where a system cannot support 12, with some exceptions set out in the applicability notes. Requirement 12.3.1 adds targeted risk analyses for the activities where the standard lets you set your own frequency. They do not replace the fixed minimum intervals the standard sets elsewhere, so a risk analysis is no reason to stretch every periodic control.
Requirements 6.4.3 and 11.6.1 deal with payment page scripts. They require an inventory and authorisation of every script that runs on the payment page and a way to detect unauthorised changes. They target Magecart-style skimming, where a compromised third-party script (a chat widget, an analytics tag, a booking engine plugin) captures card data as guests type it. The SAQ A revision of January 2025 removed these two requirements from SAQ A and replaced them with an eligibility criterion: the merchant must confirm that its site is not susceptible to attacks from scripts that could affect its e-commerce systems. This matters most where your page embeds the provider's payment form, for example in an iframe. A full redirect to the provider's page reduces the exposure further, but the page that sends the guest there still affects the payment flow and stays relevant to scope. For checkouts assessed under SAQ A-EP or SAQ D, 6.4.3 and 11.6.1 apply directly. If your booking engine runs on a third-party platform, ask the provider which of these controls it covers and which stay with you.
If your booking engine or website loads chat widgets, analytics tags or marketing pixels on the page where guests enter card details, each one is a possible skimming route. Depending on your SAQ, you either have to inventory and monitor those scripts or confirm that the page is protected against script attacks.
How to reduce your compliance scope
For most hotels, reducing scope does more than trying to secure a wide one. A hosted checkout, where the guest enters card details on your payment provider's page, can take your systems out of most of the scope for online bookings, but you still have to protect the website components that send guests to that page. Tokenisation lets the PMS work with a token instead of the full card number. Whether that takes the PMS out of scope depends on the token, on where the original card number is handled, and on whether anyone can get it back, so check with the provider and, where needed, a Qualified Security Assessor.
Network segmentation can isolate POS and payment systems from guest Wi-Fi and general hotel IT. You can use physical or logical controls such as VLANs and firewall rules. Document the permitted traffic flows and test that the segmentation works, as PCI DSS requires when you rely on it to reduce scope. For more on isolating guest networks, see our guide to guest Wi-Fi network segmentation for hotels. At the front desk, using a payment provider with evidence of PCI DSS compliance, rather than keying card numbers into the PMS, removes another large part of scope.
Outsourcing does not end your responsibilities. Under Requirement 12.8 you still keep a list of the service providers that handle card data or can affect its security, agree in writing what each one is responsible for, check their PCI DSS compliance status at least once a year, and know which requirements they cover and which remain yours. In practice, the hotel manages users, configuration and connected systems, and the provider secures the payment services it runs. Agree incident contacts in advance so a provider can reach you quickly. For the sector's wider threat picture, see our overview of cybersecurity risks in hospitality. The current standard and SAQs are in the PCI Security Standards Council document library.
This article provides general information and does not constitute legal, regulatory, or compliance advice. PCI DSS requirements and SAQ eligibility depend on your specific payment architecture and should be confirmed with your acquiring bank or a qualified security assessor.