A sales pitch that says “fully encrypted from the card reader to the processor” sounds like a PCI answer. It might be. It might also be a perfectly good security design that earns you no reduction in PCI scope at all. The label that matters is whether the solution is a validated, PCI-listed P2PE solution. This is general information, not advice for your situation.
Two terms, two meanings
End-to-end encryption (E2EE) is a general description. Data is encrypted at one end and decrypted at the other, and anyone who owns an endpoint can manage the keys. It carries no PCI validation by itself.
Point-to-point encryption (P2PE), in the PCI sense, is a defined program. PCI SSC describes a listed P2PE solution as a combination of secure devices, applications and processes that encrypts card data from a PCI-approved point-of-interaction device until it reaches a secure decryption environment. The solution is assessed by an approved P2PE assessor and published on the PCI Council’s list of validated solutions.
Every listed P2PE solution is end-to-end encrypted. Most end-to-end encrypted systems are not listed P2PE solutions.
Why the listing is the whole point
A merchant that takes cards only through a validated, listed P2PE solution may be eligible for one of the shortest self-assessment forms, SAQ P2PE. Eligibility depends on having no clear-text card data on its own systems, and the form does not apply to e-commerce or to service providers. The reduction in effort comes from the solution provider carrying the heavy lifting: key management and the decryption environment sit with them, not you.
A solution that is not listed does not qualify, however strong its cryptography. A merchant that runs its own encryption design, with its own keys and decryption, takes on the solution provider’s job. PCI SSC treats that as a merchant-managed solution, and merchant-managed solutions are not eligible for listing.
Check before you buy
1. Is the exact solution on the current PCI list of validated P2PE solutions, including the specific devices and applications you plan to use?
2. Has the listing expired? A solution on the expired list no longer counts as validated, so ask your acquirer before relying on SAQ P2PE.
3. Does any part of your payment flow, such as a keyed-in order or a web checkout, sit outside the P2PE solution? Those channels carry their own requirements.
4. Who holds the keys, and what happens to your scope if you change provider?
5. What does your acquirer say? Acquirers decide what reporting they accept.
Do not overlook the rest
P2PE shrinks the problem; it does not erase it. Devices still need to be inventoried, inspected for tampering and kept out of the wrong hands. Staff still need to know what to do when a terminal goes missing. And the current standard, PCI DSS v4.0.1, with v4.0 retired on 31 December 2024, still applies to everything that stays in scope.
If the pitch does not name a listing, treat the claim as an encryption feature to evaluate, not a PCI shortcut.
See how we help with incident response and security services.
Sources
- PCI SSC blog: Just Published, PCI DSS v4.0.1
- PCI SSC blog: Just Published, PCI DSS v4.0.1
- PCI SSC blog: Just Published, PCI DSS v4.0.1
Related
Discover more from Core-Infosec
Subscribe to get the latest posts sent to your email.