Document Comparison
PCI-P2PE-v3.x-Technical-FAQs-10Dec2025.pdf
→
PCI-P2PE-v3.x-Technical-FAQs-29Jan2026.pdf
94% similar
22 → 24
Pages
6867 → 7405
Words
4
Content Changes
Content Changes
4 content changes. 10 administrative changes (dates, page numbers) hidden.
Added
p. 14
Q16: Jan 2026 - The current v3.x P2PE Standard and Program accounts for ‘Remote Key Distribution using Asymmetric Techniques’; however, does it account for remote key distribution using symmetric techniques? A The current v3.x P2PE Standard and Program do not explicitly account for remote key distribution using symmetric techniques; however, it is not prohibited from being supported in a P2PE Solution or from being included in the scope of a P2PE assessment. There is not a Listing attribute tag to denote alternative remote key distribution methods supported by the P2PE Product.
Entities interested in key distribution methods of P2PE Solution Providers are encouraged to contact those Providers to discuss the key distribution methods they support, and if they included those methods in the scope of their P2PE assessment.
Entities interested in key distribution methods of P2PE Solution Providers are encouraged to contact those Providers to discuss the key distribution methods they support, and if they included those methods in the scope of their P2PE assessment.
Added
p. 19
Q7: Jan 2026• What are the options available for a P2PE Application Vendor when performing a P2PE Application Reassessment with regard to the P2PE Application listing that is being replaced or superseded? A There are two options for a Vendor regarding an eligible P2PE Application Reassessment where the listing for the new P2PE Application (“P2PE_App_New”) will replace or supersede the existing P2PE Application listing (“P2PE_App_Previous”). The P2PE Application Assessor will be required to select the Vendor-chosen option in the Portal upon submission of the P2PE Application Reassessment:
Option 1: Leave P2PE_App_Previous on the Validated list and let it expire as per the P2PE Program (upon 180 days after the Reassessment Date), at which time it will move to the Expired List. This may result in both P2PE_App_Previous and P2PE_App_New coexisting on the Validated list until such time as P2PE_App_Previous moves to the Expired list. However, they are unique [separate] listings with …
Option 1: Leave P2PE_App_Previous on the Validated list and let it expire as per the P2PE Program (upon 180 days after the Reassessment Date), at which time it will move to the Expired List. This may result in both P2PE_App_Previous and P2PE_App_New coexisting on the Validated list until such time as P2PE_App_Previous moves to the Expired list. However, they are unique [separate] listings with …
Modified
p. 1
Payment Card Industry (PCI) Point-to-Point Encryption (P2PE)® Technical FAQs for use with PCI P2PE v3.x December 10, 2025
Payment Card Industry (PCI) Point-to-Point Encryption (P2PE)® Technical FAQs for use with PCI P2PE v3.x January 29, 2026
Modified
p. 3
Updated Technical FAQs: General: Q2, Q3, Q4, Q7, Q8, Q9 Domain 2: Q2 New Technical FAQ(s): Domain 2, Q4 October 31 2024 New Technical FAQ: General: Q13 December 04 2024 New Technical FAQ(s): General: Q14 Domain 2: Q5 June 30 2025 Updated Technical FAQs: General: Q2 (changed to v3.2), Q9 (extended POI v6 dates) New Technical FAQ(s): General: Q15 (v3.1 to v3.2 transition) Domain 2: Q6 (use of P2PE Application version wildcards) December 10, 2025 Updated Technical FAQs: General: Q9 …
Updated Technical FAQs: General: Q2, Q3, Q4, Q7, Q8, Q9 Domain 2: Q2 New Technical FAQ(s): Domain 2, Q4 October 31 2024 New Technical FAQ: General: Q13 December 04 2024 New Technical FAQ(s): General: Q14 Domain 2: Q5 June 30 2025 Updated Technical FAQs: General: Q2 (changed to v3.2), Q9 (extended POI v6 dates) New Technical FAQ(s): General: Q15 (v3.1 to v3.2 transition) Domain 2: Q6 (use of P2PE Application version wildcards) December 10, 2025 Updated Technical FAQs: General: Q9 …