Bottom Line Up Front
If you’ve just had an email from your payment processor asking you to “complete your PCI compliance,” take a breath. The honest answer to is PCI compliance a legal requirement in the UK is: not in the sense that there’s an Act of Parliament called the PCI Act. There isn’t. PCI DSS is a contractual obligation that comes with your merchant agreement — the contract that lets you accept card payments in the first place.
But that distinction matters less than you’d hope. Breaking a contract with your acquirer has real consequences, and separately, UK GDPR and the Data Protection Act 2018 do legally require you to protect personal data with appropriate security measures — and card data is personal data. Regulators and courts look at recognised industry standards when judging whether your security was “appropriate.” PCI DSS is the recognised industry standard for card data.
So: not a statute, but not optional either. The better news is that for the vast majority of small UK merchants, validating compliance means filling in a short self-assessment questionnaire once a year and running an automated scan every quarter. That’s it. Let’s walk through it.
What Is PCI Compliance (In Plain English)
PCI DSS stands for the Payment Card Industry Data Security Standard. It’s a set of security rules designed to stop card data being stolen from the businesses that handle it.
It was created by the major card brands — Visa, Mastercard, American Express, Discover and JCB — who formed the PCI Security Standards Council (PCI SSC) to maintain it. The Council writes the standard. It does not enforce it.
Enforcement runs down the payment chain. The card brands require your acquirer (your merchant bank or payment processor — Worldpay, Barclaycard, Elavon, Stripe, SumUp and so on) to make sure their merchants comply. Your acquirer passes that obligation to you through your merchant agreement, which is why they’re the ones chasing you for a questionnaire, not the government.
What the standard actually covers
The current standard is organised into six control objectives spanning 12 requirements:
| Goal | Covers |
|---|---|
| Build and maintain a secure network and systems | Firewalls, no vendor-default passwords |
| Protect account data | Don’t store what you don’t need; encrypt what you do |
| Maintain a vulnerability management program | Anti-malware, patching, secure software |
| Implement strong access control measures | Need-to-know access, unique IDs, physical security |
| Regularly monitor and test networks | Logging, vulnerability scans, penetration testing |
| Maintain an information security policy | Written policies, staff awareness, incident response |
If you outsource most of your card handling, large chunks of those 12 requirements simply don’t apply to you. More on that shortly.
What happens if you ignore it
Three things, roughly in order of likelihood:
1. Non-compliance fees from your processor. Many acquirers apply a monthly charge to merchants who haven’t validated. It’s quietly added to your statement and it adds up.
2. Liability after a breach. If card data is compromised and you weren’t compliant, you can be held responsible for forensic investigation costs (a PFI engagement), card reissuance, fraud losses and brand fines passed down through your acquirer. Separately, the ICO may investigate under UK GDPR.
3. Losing the ability to take cards. The nuclear option, but it happens — acquirers can and do terminate merchant accounts.
Do You Need to Be PCI Compliant?
If you accept credit or debit cards in any form, yes. Card-present, card-not-present, online, over the phone, by post, through a third-party booking platform — it all counts. There is no minimum transaction volume below which PCI stops applying.
What does change with volume is how you prove it.
Your merchant level
The card brands assign merchants to Levels 1 through 4 based on annual transaction volume and risk history. Level 1 is the largest and requires a formal Report on Compliance (ROC) produced by a Qualified Security Assessor (QSA) or an internal ISA. Levels 2–4 can usually self-assess.
The overwhelming majority of UK small businesses are Level 4. But thresholds vary by card brand and can be revised, so don’t guess — ask your acquirer to confirm your level in writing. One email, and you’ll know exactly what’s expected.
The questionnaire they sent you
That form is a Self-Assessment Questionnaire (SAQ). Your acquirer sent it because their agreement with the card brands obliges them to collect evidence of compliance from every merchant, annually. Alongside the SAQ you’ll sign an Attestation of Compliance (AOC) — a short signed declaration that the answers are true.
They’re not accusing you of anything. It’s a routine annual request, the same one every merchant on their books receives.
Which SAQ Do You Need?
This is the single most important decision you’ll make, because picking the right SAQ can be the difference between a short questionnaire and a very long one. The determining factor is how much contact your systems have with card data.
| Your payment setup | Likely SAQ | Effort |
|---|---|---|
| Fully hosted checkout — Shopify Payments, Stripe Checkout, PayPal redirect; your site never touches card data | A | Lowest |
| Your own site delivers the payment page, with card fields direct-posted or created by script (check eligibility criteria — some iframe setups still qualify for SAQ A) | A-EP | High |
| Standalone dial-out card terminal or imprint machine, no electronic storage | B | Low |
| Standalone IP-connected terminal (most modern countertop/portable PDQs) | B-IP | Low–moderate |
| Phone/mail orders keyed into a web-based virtual terminal on an isolated PC | C-VT | Moderate |
| Till or payment application connected to the internet, no electronic storage | C | Moderate–high |
| Validated P2PE solution with listed devices | P2PE | Lowest of the terminal options |
| You store card numbers electronically, or nothing above fits | D | Highest |
A few practical notes:
Card machines from Square, SumUp, Zettle or Clover often land you in B-IP territory — your terminal talks to the acquirer over the internet, but you never store anything. Confirm the correct SAQ with your provider, as it depends on the exact device and how it connects. If your provider’s solution appears on the PCI SSC’s list of validated P2PE solutions, you may qualify for the P2PE SAQ instead, which is shorter still.
E-commerce is where people get caught out. The gap between SAQ A and SAQ A-EP is enormous. If your checkout page is served entirely by your provider and the customer’s browser connects directly to them, you’re likely SAQ A. If your server delivers the page that collects the card details, you may well fall into A-EP, which brings in requirements around secure development, change control and scanning — check the eligibility criteria set out for each SAQ by the PCI Security Standards Council. Ask your developer exactly how your checkout is implemented before you tick anything.
Phone payments are typically C-VT if staff key cards into a browser-based virtual terminal on a dedicated machine. Critical point: if you record calls, you must never retain the card security code (CVV2/CVC2) in the recording. Pause-and-resume recording or DTMF masking solves this.
If you store card numbers in a spreadsheet, CRM, email inbox or paper diary — please stop. That drops you into SAQ D, the full standard, and it’s the single most expensive decision a small merchant can make. Tokenisation through your gateway gives you the same repeat-billing capability without the data.
Not sure which one is yours? PCICompliance.com’s free SAQ Wizard asks a handful of questions about how you take payments and tells you exactly which questionnaire applies — in a couple of minutes, with no guesswork.
How to Complete Your SAQ
What it looks like
A spreadsheet or online form of yes/no questions, each tied to a numbered requirement. The shortest SAQs are genuinely short — an organised small merchant can finish SAQ A or B in an afternoon. SAQ D is a multi-day exercise. (Question counts change between revisions of the standard, so don’t anchor on a number you’ve read somewhere.)
What “yes” actually means
Answering Yes means the control is in place today and you could evidence it if asked. Answering No doesn’t fail you outright — it triggers a remediation plan with a target date. Answering Yes when it isn’t true is the one genuinely dangerous option, because the AOC is a signed attestation and it’s the first document a forensic investigator reads after a breach.
What to gather first
- A simple network diagram showing how card data flows from customer to acquirer
- A list of your payment devices with make, model and serial number
- Your third-party service providers and their current AOCs (ask your gateway and hosting provider — they should supply these on request)
- Your written policies: information security, acceptable use, incident response
- Evidence of staff security awareness training
- Your most recent passing ASV scan, if applicable
The quarterly ASV scan
If any part of your environment is reachable from the internet — a web server, a virtual terminal PC, an IP-connected terminal on a routable network — the standard requires an external vulnerability scan every quarter, performed by an Approved Scanning Vendor (ASV).
It’s automated. The ASV scans your public IP addresses and website for known vulnerabilities and issues a report. If it fails, you remediate and rescan until it passes. Four passing scans a year is the target. Our ASV scanning service handles scheduling, remediation guidance and the rescans, so nothing lapses between quarters.
Submitting
Send the completed SAQ and signed AOC to your acquirer through whatever portal or email address they specified. Keep copies — you’ll want last year’s to hand when next year’s request arrives.
What It Costs
I won’t quote figures that will be wrong by the time you read them, but here’s the shape of the spend:
| Item | Relative cost | Who needs it |
|---|---|---|
| Self-service SAQ platform | Low annual cost | Every self-assessing merchant |
| Quarterly ASV scanning | Low annual cost, often bundled | Anyone with internet-facing systems |
| Remediation (patching, config, MFA) | Variable — often staff time only | Most merchants |
| Penetration testing | Moderate to high | Where your SAQ, your acquirer or your segmentation approach requires it |
| QSA-led ROC | Professional services engagement | Level 1, or where your acquirer requires it |
For a Level 4 merchant on SAQ A or B, annual compliance is typically one of the smaller line items in your operating budget.
Compare that to non-compliance: monthly fees from your acquirer that recur indefinitely, and, if you’re breached while non-compliant, forensic investigation costs, card reissuance, chargebacks and a possible ICO investigation. Nobody can promise you’ll never be breached — no control set eliminates risk — but compliance meaningfully reduces both the likelihood and your exposure if it happens.
Staying Compliant Year-Round
PCI compliance is point-in-time validation of an ongoing obligation. Signing an AOC in March doesn’t mean you’re secure in September; it means you were compliant in March. The standard expects the controls to run continuously.
Practically, that means:
- Annual SAQ and AOC renewal
- Quarterly ASV scans (and after significant network changes)
- Periodic firewall rule reviews, log reviews and access reviews
- Annual staff security awareness training and policy review
- Penetration testing at the cadence the standard requires, where applicable
Changes that trigger a fresh look
Switching payment providers. Launching a new website or redesigning checkout. Adding phone orders. Opening a second site. Moving to cloud hosting. Any of these can change your SAQ type — and merchants who skip this step often discover at renewal that they’ve been self-assessing against the wrong questionnaire all year.
Our compliance dashboard tracks your renewal date, scan schedule, open remediation items and policy review deadlines in one place, so the annual request from your acquirer stops being a surprise.
FAQ
Is PCI compliance a legal requirement in the UK?
PCI DSS is not UK statute — it’s a contractual requirement in your merchant agreement with your acquirer. However, UK GDPR and the Data Protection Act 2018 legally require appropriate security for personal data, and card data qualifies, so failing PCI DSS can contribute to a data protection breach. Take legal advice on your specific obligations.
Can the ICO fine me for failing PCI DSS?
The ICO enforces data protection law, not PCI DSS directly. But when assessing whether your security measures were appropriate following a personal data breach, regulators commonly look to recognised industry standards — and for card data, that’s PCI DSS.
I only take a handful of card payments a month. Does this still apply?
Yes. There’s no volume floor for PCI DSS. The good news is that very low-volume merchants are almost always Level 4 and eligible for the simplest SAQs, so the actual work is modest.
My card terminal provider says they’re PCI compliant. Am I covered?
No. Their compliance covers their platform and devices; yours covers how you deploy and operate them, protect receipts, control staff access and respond to incidents. Do ask them for their AOC — you’ll need it as evidence of third-party due diligence.
What’s the difference between PCI DSS and Strong Customer Authentication?
SCA (typically delivered via 3DS) is a regulatory requirement under the UK’s onshored payment services rules, enforced by the FCA and implemented largely by your gateway. PCI DSS is a contractual security standard covering how you handle card data. They’re separate obligations and you need both.
How long does a small merchant SAQ actually take?
For SAQ A or B with your documents gathered in advance, an afternoon is realistic. The time sink is usually chasing service provider AOCs and writing policies for the first time — year two is much faster.
What if I answer “No” to some questions?
You document a remediation plan with owners and target dates, fix the gaps, then re-attest. Partial compliance with an honest plan is far better than a falsely signed AOC, which can void your position entirely after an incident.
Do I need a QSA?
Most Level 4 merchants don’t. You’d typically engage a QSA if your acquirer requires a ROC, if you’re Level 1, or if you have a complex segmented environment and want expert validation of scope.
The Takeaway
So, is PCI compliance a legal requirement in the UK? Not as an Act of Parliament — but as a contractual condition of accepting cards, and as strong evidence of the “appropriate security” that data protection law genuinely does require of you. Treating it as optional is a risk to your merchant account and your data protection position alike.
For most small UK merchants, the reality is far gentler than the reputation: identify the right SAQ, answer honestly, run your quarterly scan, keep the paperwork tidy, and repeat annually. The businesses that struggle are almost always the ones that stored card numbers they didn’t need or guessed at their SAQ type.
PCICompliance.com is an end-to-end platform built for exactly this — we support thousands of merchants and service providers, from single-till retailers to multi-site enterprises, with SAQ guidance, ASV scanning, remediation support and year-round tracking in one place. Start with the free SAQ Wizard to confirm which questionnaire applies to you, or talk to our compliance team if you’d rather have someone walk you through it. Either way, that email from your processor is a tick-box exercise waiting to happen — not the crisis it feels like today.