If you searched for how to get PCI DSS certification, you are looking for a document that does not exist for most organisations. PCI DSS, the Payment Card Industry Data Security Standard, is validated in one of two ways: a Self-Assessment Questionnaire (SAQ) that a merchant or service provider completes itself, or a Report on Compliance (ROC) produced by a Qualified Security Assessor (QSA) and summarised in a signed Attestation of Compliance (AOC). Neither produces a wall certificate with a logo and an expiry date, the way ISO 27001 does. When a vendor's homepage says "PCI certified", the honest response is to ask which path they followed and request the AOC. This guide walks through the assessment paths, the exact document name to ask for, and where to check a claim before you accept it.
What PCI DSS actually validates
PCI DSS is maintained by the PCI Security Standards Council (PCI SSC) and applies to any entity that stores, processes or transmits cardholder data, or that could affect the security of that data. Which validation path applies depends on the entity's role, merchant or service provider, and its transaction volume, as set by the card brands rather than by PCI SSC itself. The PCI DSS registry page on this index lists vendors with evidence we could actually find, which is a smaller set than the number of vendors claiming the standard on their marketing pages.
The two validation paths: SAQ or ROC and AOC
| Path | Who completes it | Who signs it | Document produced |
|---|---|---|---|
| Self-Assessment Questionnaire (SAQ) | The merchant or service provider, internally | An officer of the entity | A completed SAQ and AOC |
| Report on Compliance (ROC) | A Qualified Security Assessor (QSA) | The QSA and the entity | A ROC summarised in a signed AOC |
The two routes to PCI DSS validation, as set out by PCI Security Standards Council guidance.
Smaller merchants with limited exposure to cardholder data typically self-assess against a shorter SAQ type. Larger merchants and most service providers, the category most B2B software vendors fall into, are usually required by their acquiring bank or the card brands to engage a QSA for a full ROC. Either way, the output a buyer should ask for is the same: a signed AOC, not a badge.
Steps to reach PCI DSS compliance
- 1
Scope the cardholder data environment
Identify every system that stores, processes or transmits card data, or that is connected to a system that does. Scope reduction, tokenisation and network segmentation shrink what needs assessing.
- 2
Confirm the applicable SAQ type or ROC requirement
Ask the acquiring bank or the card brand which path applies. Service providers handling card data on behalf of merchants are frequently pushed toward a ROC rather than self-assessment.
- 3
Remediate against the 12 requirements
Build and maintain a secure network, protect stored data, encrypt transmission, run vulnerability management, enforce access control, monitor and test systems regularly, and maintain an information security policy.
- 4
Complete the SAQ or engage a QSA for the ROC
A QSA tests controls in person or remotely, reviews evidence, and documents findings in the ROC.
- 5
Sign the Attestation of Compliance
The AOC states the SAQ type or confirms ROC completion, the assessor's name where applicable, the assessment period and a validity date.
- 6
Submit evidence to the acquiring bank or card brand
This is how the entity ends up listed in a card brand registry, which is the only place a buyer can check the claim independently.
- 7
Re-validate annually and scan quarterly
PCI DSS validation is a point-in-time attestation that expires. Quarterly Approved Scanning Vendor (ASV) scans and annual re-assessment keep the AOC current.
The document to request: the Attestation of Compliance
The AOC is typically a short, signed form, not the full ROC itself, which can run to over a hundred pages and is rarely shared outside the assessment relationship. A legitimate AOC states the entity's name, the SAQ type or ROC reference, the assessment date range, a validity period, and the assessor's name and QSA company if one was involved. If a vendor cannot produce this when asked, their claim has no supporting evidence, whatever the trust centre badge says. What Is PCI DSS Compliance? Reading the AOC Properly covers the fields to check line by line.
The Attestation of Compliance is a form that documents a PCI DSS assessment result, whether that assessment used a Self-Assessment Questionnaire or a Report on Compliance completed by a Qualified Security Assessor.
Where to verify the claim: the card brand registries
Visa and Mastercard each publish a registry of validated service providers. These are the only independent places a buyer can check a PCI DSS claim without asking the vendor directly for their AOC. The Visa PCI registry mirror on this index tracks these listings, and Where PCI DSS Evidence Actually Lives explains how the Visa and Mastercard lists differ and why a listing on one does not guarantee a listing on the other.
- 12
- Requirements in PCI DSS v4.0.1
- Organised under six control objectives, PCI Security Standards Council
- 4
- Merchant and service provider levels
- Each card brand sets its own thresholds for which level applies
- 75%
- of Visa registry listings are not a full PCI DSS validation
- in the CertReports index on 2026-11-07
That last figure matters for buyers. A name appearing in a card brand registry is not automatically proof of current validation, some listings cover related but distinct categories. Three Quarters of the Visa Registry Is Not a PCI DSS Validation breaks down what the other listing types actually mean, and why the validity date on the AOC is the detail that settles the question.
Reading a vendor's PCI DSS evidence in practice
Checkout.com's public record is a useful example of what a verified PCI DSS claim looks like next to the rest of a vendor's evidence. Rather than a badge, look at whether there is a listing in the Visa Global Registry of Service Providers, whether a validity window is shown against that listing, and how it sits alongside separately stated SOC 1 and SOC 2 Type II reports. The combination of a registry entry and named report types is what a QSA-backed claim actually looks like, compared with a logo on a homepage.

checkout · Trust report
Payments · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 1 verified, 6 vendor-stated.
3Documents and agreements
Legal and review documents checkout publishes or offers, as of 30 Sep 2026.
- Subprocessor list · Public
- Privacy policy · Public
- Public trust centre documents · Cyber Essentials+ 2026; Cyber Essentials+ 2025
3Subprocessors
Named on checkout's public subprocessor list, last seen 30 Sep 2026.
Claims that do not hold up
- A homepage badge reading "PCI certified" with no SAQ type, no ROC reference, and no validity date attached.
- A trust centre page that lists PCI DSS alongside other frameworks with no distinction between a self-assessment and a QSA-led ROC.
- A claim of Level 1 service provider status with no matching entry in either card brand registry.
- An AOC date range that has quietly lapsed, with no newer attestation published anywhere a buyer can find it.
- A vendor answering a questionnaire with "PCI DSS compliant" instead of naming the SAQ type or pointing to the ROC and AOC.
A buyer checklist before you accept the claim
Before you accept a PCI DSS claim
People also ask
How to get pci dss certification?
There is no certificate to apply for. Entities validate PCI DSS either by completing a Self-Assessment Questionnaire (SAQ) internally, or by engaging a Qualified Security Assessor (QSA) to produce a Report on Compliance (ROC). Both paths end in a signed Attestation of Compliance (AOC), which is the document a buyer should ask a vendor for, rather than accepting an unsupported claim of certification.
How to be pci dss compliant?
Scope the cardholder data environment, confirm which SAQ type or ROC path applies based on your role and volume, and implement the 12 requirements covering network security, data protection, vulnerability management, access control, monitoring and policy. Complete the assessment, sign the AOC, run quarterly ASV scans, and re-validate annually to keep the attestation current.
How to be pci dss certified?
The word "certified" is not accurate for PCI DSS. What an entity actually obtains is a signed Attestation of Compliance, based on either a Self-Assessment Questionnaire or a QSA-led Report on Compliance. If you want to describe your own status to buyers accurately, name the SAQ type or ROC path and share the AOC, rather than using certification language the standard does not support.
How many pci dss requirements are there?
PCI DSS v4.0.1 sets out 12 requirements, organised under six control objectives covering secure networks, cardholder data protection, vulnerability management, strong access control, regular monitoring and testing, and an information security policy. These 12 requirements are the baseline a SAQ or ROC assesses against, regardless of which validation path applies to the entity.
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
Where PCI DSS evidence actually lives: the Visa and Mastercard registries
CertReports Research · 3 Sep 2026 · 10 min read