Free readiness checklists for NIS2, DORA, ISO 27001, PCI DSS, POPIA, JS2 and Southern Africa.Get a checklist →

Checklist

PCI DSS 4.x and P2PE: A Practical Payment Security Readiness Checklist

Payment environments need more than an annual audit rush. Effective readiness makes scope, ownership, operational controls and evidence visible throughout the year.

Where PCI DSS stands

PCI DSS v4.0.1 is the current version of the standard. The future-dated requirements introduced in v4.0 have been mandatory since 31 March 2025, so assessments now test all of them. The PCI Security Standards Council opened a request for comments on the standard in June 2026, but v4.0.1 remains the version to assess against until a new version and effective date are announced.

Readiness checklist

Scope and ownership

  • Map the cardholder data environment, payment flows, service providers and encryption boundaries, and confirm them with data discovery
  • Document and confirm scope at least annually (every six months for service providers)
  • Maintain a responsibility matrix for every third-party service provider
  • Assign accountable owners for each requirement, shared control and compensating control

Requirements most often missed

  • Payment-page script inventory, authorisation and integrity (6.4.3), plus change and tamper detection (11.6.1)
  • Multi-factor authentication for all access into the CDE (8.4.2)
  • Minimum 12-character passwords where passwords are used (8.3.6)
  • Targeted risk analyses that justify control frequencies (12.3.1)
  • Automated audit log review (10.4.1.1)
  • Anti-phishing controls and phishing-aware security training (5.4.1, 12.6.3.1)
  • Authenticated internal vulnerability scans and managing all vulnerabilities (11.3.1.1, 11.3.1.2)
  • User account and access privilege reviews at least every six months (7.2.4)

Testing and scanning cadence

Evidence and operations

  • Collect evidence while controls operate, not only before the assessment
  • Exercise incident response, including supplier escalation and card-brand notification
  • Track remediation to verified closure, with dates and owners

Using P2PE to reduce scope

A validated PCI Point-to-Point Encryption (P2PE) solution encrypts card data inside the payment terminal, using keys the merchant cannot access, until it reaches the solution provider's secure decryption environment. Because cleartext card data never enters the merchant's systems, P2PE can significantly reduce PCI DSS scope, and eligible merchants may validate using the much shorter SAQ P2PE.

To benefit, merchants should:

  • Confirm the solution is listed as validated on the PCI SSC website, not just "P2PE-ready" or "end-to-end encrypted"
  • Follow the solution provider's P2PE Instruction Manual (PIM), including device inspection and tamper checks
  • Keep an inventory of devices and their locations, and check them regularly for tampering or substitution
  • Make sure no other channels, such as manual key entry, e-commerce or MOTO, reintroduce card data into scope

Common mistakes to avoid

  • Relying on network diagrams instead of data discovery to define scope
  • Treating 6.4.3 and 11.6.1 as one-off projects rather than ongoing controls
  • Assuming an "end-to-end encrypted" terminal provides P2PE scope reduction
  • Collecting evidence only in the weeks before the assessment
  • Forgetting that service providers face more frequent scope and segmentation checks

Frequently asked questions

Do requirements 6.4.3 and 11.6.1 apply to us?

They apply to entities with payment pages in scope. For merchants that fully outsource e-commerce payment pages and validate using SAQ A, check the current SAQ A eligibility criteria, which the PCI SSC revised in early 2025.

What is the difference between a ROC and an SAQ?

A Report on Compliance (ROC) is a detailed assessment performed by a QSA. A Self-Assessment Questionnaire (SAQ) is completed by the organisation itself. Which you need depends on your merchant or service-provider level and acquirer requirements.

How do we know if a P2PE solution is validated?

Check the list of validated P2PE solutions on the PCI SSC website. Solutions described as "P2PE-ready" or "end-to-end encrypted" are not necessarily validated, and may not deliver the same scope reduction.

Can SecuriCentrix both prepare us and assess us?

As a QSA Company, we can provide readiness and the formal assessment, with clear independence safeguards between advisory and assessment roles. We will explain those safeguards at scoping.

Readiness means being able to show that controls work, gaps are owned and risk decisions are documented, at any point in the year.

As a PCI SSC-accredited QSA Company, SecuriCentrix can take you from scoping and gap assessment through testing to your Report on Compliance.

Free readiness checklists

Work through the checks with your team, then talk to us about any gaps.

Related reading

Sources

This article is general guidance, not legal advice.

Free checklist

PCI DSS v4.0.1 readiness checklist

A practical QSA-built checklist covering scope, v4.x requirements, testing cadence and evidence.