Guide Compliance PCI DSS

PCI DSS Compliance for UK Businesses: A Practical Guide to v4.0.1

Any UK business that accepts card payments has to comply with the Payment Card Industry Data Security Standard (PCI DSS) through its merchant agreement. Version 4.0.1 has been the only active version since 1 January 2025. This guide covers what v4 requires, how merchant levels and SAQs work, the difference between merchants and service providers, how to reduce scope safely, and a seven-phase route to compliance.

13 August 2026
13 min read
Updated 9 November 2026
Key takeaways
  • PCI DSS is not UK law. Your merchant agreement with your acquirer and the card brand rules make it binding
  • PCI DSS v4.0.1 has been the only active version since 1 January 2025, and new assessments use it
  • Merchant levels and validation routes are set by each card brand and your acquirer, so confirm yours with them rather than relying on a generic table
  • A hosted payment page can make you eligible for SAQ A, but only if you meet every eligibility criterion for every payment channel in scope
  • Hosted pages, segmentation and tokenisation reduce scope; they do not remove your responsibility for the systems and providers that remain
  • Non-compliance can bring fees and penalties under your acquirer contract, and a breach can add investigation costs, card brand assessments and the loss of card acceptance

What Is PCI DSS and Who Enforces It?

PCI DSS is a private information security standard managed by the PCI Security Standards Council (PCI SSC), a body founded in 2006 by Visa, Mastercard, American Express, Discover and JCB. It is not a law, and no government agency fines you for failing it. The obligation comes from your contract with your acquirer, which in turn follows the card brands' rules.

When you sign up with an acquirer or payment provider to accept cards, you agree to comply with PCI DSS as a condition of that agreement. UK examples include Barclaycard, Worldpay, Lloyds Cardnet, Stripe, Square and SumUp. Each one runs its own compliance programme: how often you report, which form of validation it accepts, whether it wants ASV scan reports, and what it does when a merchant falls behind.

Merchant levels are defined by each card brand, not by the PCI SSC, and your acquirer tells you which level and validation route applies. The table below uses Visa's thresholds as an example. Mastercard's are similar, while other brands, such as American Express, set their own.

  • Level 1: More than 6 million transactions a year, or a merchant the brand has assigned to Level 1, for example after a compromise. Usually validated with a Report on Compliance (ROC) by a Qualified Security Assessor (QSA), or by an internal assessor where the brand allows it, plus quarterly ASV scans.
  • Level 2: 1 million to 6 million transactions a year. Usually an annual Self-Assessment Questionnaire (SAQ) and quarterly ASV scans where the SAQ requires them.
  • Level 3: 20,000 to 1 million e-commerce transactions a year. Usually an annual SAQ and ASV scans where required.
  • Level 4: Fewer than 20,000 e-commerce transactions, or up to 1 million transactions in total. Validation requirements are set by the acquirer.

Most UK SMEs sit at Level 3 or Level 4. Counting rules and requirements vary by brand and acquirer, so treat your acquirer's written instructions as the source of truth.

Non-compliance and breach consequences

Card brands can levy penalties on acquirers, and acquirers often pass these on to merchants as non-compliance fees under the merchant agreement. The amounts depend on the contract and the brand's rules, which are not fully public. After a suspected compromise, the brand or acquirer may require a forensic investigation, and you may face investigation costs, card brand assessments for fraud and card reissuance, higher fees, closer monitoring or termination of card acceptance. The total depends on the facts of the case and your contract. Separately, cardholder data is personal data under UK GDPR: if a breach is reportable, you must tell the ICO within 72 hours of becoming aware of it. FCA-regulated firms also have operational resilience and incident reporting duties.

The 12 PCI DSS Requirements at a Glance

The standard is built around 12 principal requirements, each broken down into sub-requirements. Which sub-requirements apply depends on your environment, your role (merchant or service provider) and the validation route your acquirer accepts. If you use an SAQ, the questionnaire lists only the requirements relevant to that payment setup.

# Requirement What It Means in Practice
1 Install and maintain network security controls Firewall and other network security control rules defined and reviewed; segmentation between the cardholder data environment and other networks where you rely on it to limit scope
2 Apply secure configurations to all system components Vendor default passwords changed or disabled; configuration standards applied to in-scope systems
3 Protect stored account data Do not keep sensitive authentication data, such as the card verification code, after authorisation; render stored PANs unreadable; keep account data only as long as there is a documented need
4 Protect cardholder data with strong cryptography during transmission over open, public networks Strong cryptography and secure protocols, such as current TLS configurations, when PAN crosses open, public networks; never send PANs by end-user messaging such as email or chat without protection
5 Protect all systems and networks from malicious software Anti-malware on systems commonly affected by malware; periodic evaluation of systems you judge not at risk; anti-phishing mechanisms
6 Develop and maintain secure systems and software Patching based on risk ranking; secure development for bespoke and custom software; protection of public-facing web applications; payment page script controls where applicable
7 Restrict access to system components and cardholder data by business need to know Least privilege; access assigned by role; periodic review of user accounts and privileges
8 Identify users and authenticate access to system components Unique user IDs; MFA for all non-console access into the cardholder data environment (Req. 8.4.2) and for remote network access
9 Restrict physical access to cardholder data Physical controls where in-scope systems or media sit; inspection of card-reading devices at the point of interaction; secure media destruction
10 Log and monitor all access to system components and cardholder data Audit logs retained for at least 12 months, with the most recent 3 months immediately available; log reviews and detection of failures in critical security controls
11 Test security of systems and networks regularly Internal and external vulnerability scans (external by an ASV) where applicable; penetration testing where required; change and tamper detection
12 Support information security with organisational policies and programs Information security policy; targeted risk analyses where the standard calls for them; incident response plan; security awareness; management of third-party service providers

New in PCI DSS v4

PCI DSS v4.0 was published in March 2022, and version 3.2.1 was retired on 31 March 2024. In June 2024 the PCI SSC published v4.0.1, a limited revision that clarifies wording and adds no new requirements. It retired v4.0 on 31 December 2024, so new assessments use v4.0.1.

Version 4 introduced 64 new requirements. Thirteen took effect immediately; the other 51 were best practices until 31 March 2025 and are now mandatory. In an assessment today, every new requirement that applies to your environment must be in place. Some apply only to service providers and some only to certain payment setups, so the number that affects you is usually smaller than 64.

The changes most merchants notice are:

  • Customised approach: Alongside the defined approach, v4 lets an entity meet a requirement's stated objective with its own controls. It requires a targeted risk analysis and controls matrix for each requirement, is validated by a QSA, and is not available in SAQs. Most UK SMEs will stay with the defined approach.
  • MFA expanded: Requirement 8.4.2 requires multi-factor authentication for all non-console access into the cardholder data environment, for ordinary users as well as administrators. Version 3.2.1 required it for administrative non-console access and for remote access only.
  • E-commerce script security (Requirements 6.4.3 and 11.6.1): These target the Magecart attack pattern, where criminals inject scripts into payment pages to capture card data as customers type it. You need an inventory of scripts on payment pages, a justification and authorisation for each, a way to confirm their integrity, and a mechanism that detects unauthorised changes to the page and its HTTP headers. They apply under SAQ A-EP and SAQ D. The January 2025 revision of SAQ A removed both requirements from that questionnaire and added an eligibility criterion: the merchant confirms its site is not susceptible to script attacks that could affect its e-commerce systems.
  • Password length: Where passwords are used as an authentication factor, the minimum length rose from 7 to 12 characters. If a system does not support 12, the minimum is 8.
  • Targeted risk analysis: For specified requirements that allow you to set the frequency, such as some periodic reviews, you document a targeted risk analysis to justify the interval you choose. Requirements with a fixed frequency, such as quarterly vulnerability scans, keep it.
Already assessed against v4?

If you completed a v4 assessment before 31 March 2025, the 51 future-dated requirements may have been reported as best practices rather than tested. Your next assessment will include those that apply to your environment. Check which of them your assessor did not test and confirm you have them in place before your next submission.

Which SAQ Applies to Your Business?

First establish your role. A merchant accepts cards as payment for its own goods or services. A service provider stores, processes or transmits account data on behalf of others, or manages systems that can affect the security of that data, for example a hosting company or a managed service provider. If you are a service provider and eligible to self-assess, SAQ D for Service Providers is the only SAQ available to you. Some businesses are both, and validate each role separately.

For merchants, a Self-Assessment Questionnaire (SAQ) lets an eligible business assess its own compliance without a full QSA assessment. Each SAQ has eligibility criteria, and you must meet all of them for every payment channel the SAQ covers. If you take payments in more than one way, you may need more than one SAQ, or SAQ D. Choosing an SAQ you are not eligible for leaves your attestation invalid.

The SAQ types UK merchants meet most often are:

  • SAQ A: For card-not-present merchants that have fully outsourced all account data functions to PCI DSS-compliant third parties, with no electronic storage, processing or transmission of account data on their own systems or premises. Payment pages must come entirely from the third party, through a redirect or an embedded iframe. A hosted checkout such as Stripe Checkout or PayPal's hosted checkout can support SAQ A eligibility, but using one is not enough on its own: you must meet every criterion, including the one on script attacks, and SAQ A still includes some requirements for your own website, such as ASV scans of the page that contains the redirect or iframe.
  • SAQ A-EP: For e-commerce merchants that outsource payment processing but whose website controls how account data reaches the processor, or where any element of the payment page originates from the merchant's website. A direct post form or a payment form built with JavaScript from your own site are common examples. Because your site can affect the security of the transaction, the script requirements 6.4.3 and 11.6.1 apply, as do more requirements than in SAQ A.
  • SAQ B: For merchants using imprint machines or standalone dial-out terminals with no electronic storage of account data.
  • SAQ B-IP: For merchants using only standalone, PCI-approved payment terminals with an IP connection to the processor and no electronic storage of account data.
  • SAQ C-VT: For merchants that key card details into a provider's virtual terminal through a web browser on an isolated computer, with no electronic storage.
  • SAQ C: For merchants with a payment application connected to the internet, such as some POS setups, and no electronic storage of account data.
  • SAQ P2PE: For merchants using only hardware terminals from a PCI-listed point-to-point encryption (P2PE) solution.
  • SAQ D for Merchants: For any merchant not eligible for another SAQ. It covers every PCI DSS requirement that applies to the environment.

"If your setup allows it, a fully hosted payment page that meets every SAQ A criterion is usually the biggest scope reduction available to a UK e-commerce business."

Your acquirer confirms which SAQ and validation route it accepts. If you are unsure, ask before you complete anything. An SAQ that does not match how you actually take payments creates exposure rather than reducing it.

Scoping: How to Reduce What You Have to Protect

The cardholder data environment (CDE) is made up of the people, processes and technology that store, process or transmit cardholder data or sensitive authentication data. PCI DSS scope is wider than the CDE: it also covers system components that are connected to the CDE, or that could affect its security, such as directory services, jump hosts, logging servers or systems that manage the payment page. Everything in scope needs controls, documentation and evidence, so a smaller scope means less to manage.

SAQ A
the shortest questionnaire, if you meet every eligibility criterion
SAQ D
every applicable requirement, for merchants not eligible for another SAQ
11.3.2
ASV scans can still apply under SAQ A, to the site that redirects or embeds the payment page

Four strategies reduce scope:

  • Hosted payment pages: When customers enter card data on a page served entirely by a compliant provider, the data does not pass through your servers. Your CDE can become very small, but your website remains in scope for the controls that protect the redirect or iframe, and you remain responsible for managing the provider and confirming its compliance.
  • Network segmentation: If some systems must handle card data, isolate them with properly configured network security controls. Systems that cannot connect to the CDE and cannot affect its security can be out of scope, but only if segmentation is documented and tested; penetration testing must confirm it works. Without effective segmentation, the whole network is in scope.
  • Tokenisation: For recurring billing, replace stored card numbers with tokens issued by your payment provider. The provider's tokenisation and vault systems stay in scope under its own assessment. Your systems that use only tokens may drop out of scope, provided they cannot obtain the PAN through detokenisation and do not affect the security of the CDE.
  • Do not keep what you do not need: Store account data only where a documented business need exists. Never store sensitive authentication data, such as the card verification code (CVV2 or CVC2), after authorisation, even if encrypted. Unneeded card data widens your scope and your liability.
Confirm scope at least once a year

PCI DSS v4 requires you to confirm and document scope at least every 12 months and after significant changes to the in-scope environment (Req. 12.5.2). New integrations, marketing tags on payment pages, a hosting change or a new payment channel can all change your scope.

A Compliance Roadmap

PCI DSS v4.0.1 has been the only active version since 1 January 2025, and the 51 future-dated requirements became mandatory on 31 March 2025. No other transition dates were pending when this guide was updated. If you are behind on compliance or have a deadline from your acquirer, work through these phases in order:

# Phase What you do
1 Discover payment channels List every way you take cards: website, phone, terminals, virtual terminals, apps, invoices and payment links
2 Map data flows Trace where account data enters, travels and is stored, including staff, third parties and systems that can affect the CDE
3 Determine role and scope Decide whether you act as a merchant, a service provider or both, and document what is in scope and why
4 Confirm the validation route Ask your acquirer for your merchant level, the SAQ or ROC it expects, its deadlines and its scan requirements
5 Assess controls Run a gap assessment against the applicable SAQ or the full standard and record the evidence you hold
6 Remediate and validate Fix the gaps, then obtain passing ASV scans and penetration test results where your SAQ or the standard requires them
7 Submit and maintain Submit the SAQ or ROC with the Attestation of Compliance (AOC), then keep controls running and recheck scope at least every 12 months

If you have not been assessed before, phases 1 to 3 usually take the most thought. Getting scope and role right first stops you answering the wrong questionnaire or testing systems you could have taken out of scope.

How Cyvra Supports PCI DSS Compliance

Cyvra works with UK merchants and service providers at every stage of PCI DSS compliance. You may come to us with a deadline from your acquirer, or be adding payment channels and want to know the PCI DSS impact before you build.

A typical engagement covers mapping your payment channels and data flows, confirming your role and the validation route with your acquirer, a gap assessment, a remediation plan, support with implementing controls, and preparing your SAQ and AOC.

If you are planning a change to your payment setup, for example moving from a custom payment form to a hosted checkout, we assess the scope impact before the project starts. Scope decisions made at the architecture stage cost far less than fixing gaps after systems are built.

If your acquirer has asked for compliance documentation, or you want to know where you stand before your next assessment, get in touch for a short conversation about your payment environment.

Frequently asked questions

Does PCI DSS apply if I use Stripe or PayPal?

Yes. Using a payment provider does not remove your PCI DSS obligation, although it can reduce your scope a great deal. If card details are entered only on a page served entirely by the provider, through a redirect or an iframe, and you meet every other SAQ A criterion, you may be able to use SAQ A. If your website builds the payment form, loads its own scripts into it or otherwise controls how card data reaches the provider, you are more likely to need SAQ A-EP or SAQ D. Your acquirer confirms which applies.

How often do I need to submit my SAQ?

Usually once a year. Your acquirer sets the schedule and the format, and some also ask for ASV scan reports or other evidence during the year. Programmes differ between providers such as Barclaycard, Worldpay and Stripe, so check your acquirer's compliance programme documents for the exact requirements.

What is an ASV scan and do I need one?

An ASV scan is an external vulnerability scan of your internet-facing systems, carried out by an Approved Scanning Vendor listed by the PCI SSC. Under PCI DSS v4.0.1, external ASV scans (Req. 11.3.2) appear in several SAQs, including SAQ A. For an SAQ A e-commerce merchant, the scans cover the website that contains the redirect or embeds the payment page iframe, because an attacker who compromises that page could send customers to a fake payment page. Check your SAQ and your acquirer's instructions for what applies to you.

Is PCI DSS a legal requirement in the UK?

No. PCI DSS is a contractual requirement, enforced through your merchant agreement, which follows the card brands' rules. Failing it is not a criminal or regulatory offence in itself. Separately, if cardholder data is breached you may have to notify the ICO under UK GDPR within 72 hours of becoming aware of a reportable breach, and FCA-regulated firms have their own operational resilience and incident reporting duties.

What happens if I have a card data breach?

Contact your acquirer straight away and follow its incident procedure. Depending on the case, the card brands or your acquirer may require a forensic investigation by a PCI Forensic Investigator (PFI), usually at your cost. Consequences depend on what the investigation finds and on your contract, and can include card brand assessments for fraud and card reissuance, non-compliance fees, stricter validation requirements and, in serious cases, the loss of card acceptance. You must also assess whether the breach has to be reported to the ICO under UK GDPR. Being compliant at the time does not rule out costs, but it can limit your exposure.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Ready to start?

Get a clear picture of your PCI DSS position

A gap assessment tells you which controls you currently fail, what the remediation effort looks like, and which SAQ type applies to your environment.

Request a gap assessment Our compliance services

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.