PCI P2PE certification for solutions, components and applications

Take your P2PE product through PCI SSC validation

PCI P2PE validates solutions, components and applications that encrypt payment card data from the point of capture through to secure decryption. We define what is being validated, assess readiness, carry out the assessment and support you through PCI SSC review and listing - typically within 5-9 months.

400+ PCI certification audits
3 PCI P2PE assessors
60+ Countries where our clients operate
15+ Years of PCI assessment experience
WHO PCI P2PE IS FOR

Which P2PE validation route fits your product?

P2PE solution providers

You provide an end-to-end P2PE solution and need formal validation of the environment against the PCI P2PE standard.

  • You are preparing a P2PE solution for certification
  • POI devices, payment applications and decryption are part of the solution
  • The solution needs PCI SSC approval and listing

P2PE component providers

You provide a component used within P2PE solutions and need it assessed against the applicable PCI P2PE requirements.

  • Your component will form part of a P2PE solution
  • Its role and boundaries need to be defined for assessment
  • You need independent P2PE validation of the component

P2PE application providers

You provide a payment application used within P2PE solutions and need formal assessment under the PCI P2PE programme.

  • Your application is designed for use within P2PE solutions
  • The application needs assessment against P2PE requirements
  • You need formal validation for use within the P2PE ecosystem
OVERVIEW
What is PCI P2PE?

What is PCI P2PE?

PCI P2PE (Point-to-Point Encryption) is a PCI Security Standards Council standard for solutions that encrypt payment card data in a PCI-approved point-of-interaction (POI) device and decrypt it only in a secure environment using hardware security modules (HSMs). Validated P2PE solutions, components and applications are listed by PCI SSC. For merchants, a listed P2PE solution can significantly reduce PCI DSS scope. Patronusec provides P2PE assessments through qualified P2PE assessors.

PROCESS

How we will work with you

We guide you through the process from scope definition and readiness review to the certification audit, reporting and PCI SSC approval.

1

Scope definition

We define the scope of the solution or component, including relevant POI devices, payment applications, the decryption environment, HSM locations and cryptographic key management processes.

2

Gap analysis

Optional for organisations that want to check readiness before the certification audit. We simulate the assessment, identify non-conformities and recommend improvements.

3

Consulting

We support your team throughout preparation, answer questions on the standard and help resolve issues identified before the formal audit.

4

Certification audit

The audit combines remote and on-site activities, including interviews, configuration review, process and documentation review, observations and testing.

5

Remediation and evidence

You address identified issues and provide the documents and evidence required to complete the assessment.

6

Reporting

We prepare the compliance report, complete our internal quality assurance review and provide the Attestation of Compliance for signature.

7

PCI SSC review

We submit the documentation to PCI SSC for independent AQM review and support any clarification requests during the review process.

8

Completion

Once approved, you receive the countersigned validation documentation, your product is added to the PCI SSC list of validated P2PE products and Patronusec issues a certificate of compliance you can share with customers.

CASE STUDY

P2PE component listed by PCI SSC four months ahead of schedule

A global payment terminal manufacturer needed its US instance of a remote key injection platform validated and listed by PCI SSC as a P2PE component. Patronusec worked with the client's teams to develop the architecture and compliance model. The platform achieved its listing in 12 months, four months ahead of schedule.

Read the Case Study →
Industry Payment terminal manufacturing
Region United States
Scale Global terminal manufacturer · US remote key injection platform
Scope PCI P2PE · component role · high availability architecture · compliance-by-default · readiness review
Duration 12 months instead of 16 planned
Outcome PCI SSC component listing · 4 months ahead of schedule

"We treat the next assessment cycle as a normal working week, not a project."

Head of Infrastructure, global payment terminal manufacturer
OUR SPECIALISTS

The people who scope your project are the people who deliver it

Your certification is led by qualified P2PE assessors with deep technical knowledge of payment encryption and key management. No subcontractors, no rotation.

Christopher Ince

Christopher Ince

Principal Security Consultant · 12 years
PCI P2PE Assessor · PCI DSS QSA · ISO 27001

“A P2PE assessment works best when the scope and evidence are clear before the audit starts. I help teams understand exactly what they need to demonstrate.”

Mat Clarke

Mat Clarke

Principal Security Consultant · 10 years
PCI P2PE Assessor · PCI DSS QSA · PCI QPA

“P2PE has a strong technical element. Before becoming an assessor I worked in penetration testing, so I focus on how the controls actually work – not just on paper.”

Kris Olejniczak

Kris Olejniczak

Founder & CEO
PCI P2PE QSA · PCI SSF QSA · PCI QPA

“One of the first decisions in P2PE is what exactly you are validating: a solution, a component or an application. Getting that right early makes the whole certification clearer.”

We treat the next assessment cycle as a normal working week, not a project.
Head of Infrastructure global payment terminal manufacturer
FAQ

What to know before PCI P2PE certification

Yes for new submissions. Since 1 January 2026, all new P2PE product submissions, including reassessments of existing listed products, must use P2PE v3.2. Products previously validated to v3.0 or v3.1 can continue to be maintained under the applicable programme requirements.

Typically 5–9 months, depending on the complexity of the solution and how complete your evidence is. This includes the PCI SSC review period.

PCI P2PE validates products that protect payment data through encryption. PCI DSS applies to organisations and environments that store, process or transmit cardholder data. Using a listed P2PE solution can significantly reduce a merchant's PCI DSS scope.

The product must continue to meet the P2PE programme requirements. Annual revalidation is required in years one and two, followed by a full assessment every three years to renew the listing. Changes to the product may also need to be assessed under the programme rules.
START THE CONVERSATION

Find out which P2PE validation route fits your product

Tell us whether you are working with a P2PE solution, component or application and where you are in the process. We’ll use the call to clarify the likely scope and the right next step.

20-minute scoping call
No obligation
Speak directly with a specialist, not a salesperson
RESOURCES

Prepare for PCI P2PE certification

Practical guidance on P2PE architecture, validation routes and the impact of payment encryption on PCI DSS scope.

ARTICLE

P2PE (point-to-point encryption): how payment encryption reduces PCI DSS scope

Understand how point-to-point encryption protects payment data and why an eligible P2PE solution can significantly reduce the PCI DSS scope for merchants.

ARTICLE

P2PE vs E2EE vs NESA: three approaches to payment encryption and their impact on PCI DSS scope

Compare three approaches to payment encryption and understand how their security and validation models affect PCI DSS scope.

ARTICLE

P2PE component, solution or application: three validation routes for providers

Understand the three P2PE product types and identify which validation route best matches the product your organisation provides.