EU Cyber Resilience Act Guide for Point-of-Sale & Payment Terminal Vendors
Critical for a physical payment terminal with a tamper-protected security box (Annex IV, point 1). Default class for POS software, SoftPOS applications, tills without a security box and kiosks, including a kiosk that integrates a payment terminal
Point-of-sale system and payment terminal vendors placing connected card readers, POS terminals, mobile payment devices, and integrated POS software on the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. A physical payment terminal with a tamper-protected security box is a critical product (Annex IV, point 1). POS software, tills without such a security box and kiosks are default-class products. All of these products must satisfy CRA obligations in parallel with the PCI DSS and PCI PTS requirements that the payment industry already sets.
Last updated 26 October 2026
CRA Scope and Classification for Payment Products
Payment terminals, card readers, integrated point-of-sale systems, mobile point-of-sale (mPOS) devices, self-service kiosks with payment functionality, and POS software with network connectivity are all products with digital elements within CRA scope. Classification follows core functionality (Article 7(1)). Annex IV, point 1 lists hardware devices with security boxes. Commission Implementing Regulation (EU) 2025/2392 describes this category as hardware that securely stores, processes or manages sensitive data or performs cryptographic operations. The hardware has multiple discrete components inside a physical envelope that gives tamper evidence, tamper resistance or tamper response against physical attacks. The Regulation names physical payment terminals as an example. A countertop terminal, a PIN pad or an mPOS card reader that meets this description is therefore a critical product. POS software, SoftPOS applications, tills without such a security box and self-service kiosks match no Annex III or Annex IV category and are default class. A kiosk that integrates a payment terminal stays default class, because integrating a critical component does not by itself make the host product critical (Commission Implementing Regulation (EU) 2025/2392). The integrated terminal is a critical product in its own right. Cardholder data, payment network connections and transaction records do not change the class of any of these products. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address.
Vendors should note that POS system complexity varies significantly: a standalone countertop payment terminal with a direct payment network connection is a simpler product than an integrated POS system combining payment processing, inventory management, loyalty programme integration, and customer analytics. Both are within CRA scope. The more complex system has a larger attack surface for the Article 13(2) risk assessment to address. The class still follows core functionality. A standalone terminal with a security box is critical, and an integrated POS system whose core functionality is retail management is default class. Vendors must scope each product line independently.
Annex I Technical Requirements for Payment Products
Payment terminal vendors are already subject to stringent security requirements under PCI PTS (Point-to-Point Terminals Standards) and PCI DSS. CRA Annex I adds to - but largely aligns with - these existing requirements:
- Encryption of cardholder data: Point-to-point encryption (P2PE) is best practice under PCI DSS and directly satisfies CRA Annex I data confidentiality requirements.
- Authenticated firmware updates: PCI PTS requires firmware signing; this directly aligns with CRA's authenticated update requirements. Vendors must verify that update mechanisms meet CRA standards even if PCI PTS approval is current.
- Tamper detection and response: Physical tamper detection is a PCI PTS requirement; logical tamper detection (integrity monitoring of the running software environment) is additionally required under CRA.
- Minimal attack surface: POS terminals must not run unnecessary services. Management interfaces must be protected with strong authentication.
- SBOM maintenance: POS systems frequently integrate complex software stacks including payment kernels, OS components, and application software. A complete SBOM for each firmware/software version must be maintained.
CVD Policy and Article 13 for POS Vendors
Payment terminal vulnerabilities are among the most commercially sensitive in the technology sector - a publicly disclosed payment terminal vulnerability can trigger immediate fraudulent exploitation and cause significant reputational damage to the vendor and their retail customers. Article 13's CVD policy requirement does not require immediate public disclosure; it requires a formal coordinated disclosure process.
- Provide a secure submission channel accessible to security researchers and payment industry bodies (e.g., PCI SSC security research programme)
- Define embargo periods that allow patch development and payment scheme notification before public disclosure - typically 90 days or longer for complex payment terminal vulnerabilities
- Coordinate with payment card scheme security teams (Visa, Mastercard) who have independent notification requirements under their scheme rules
- Publish CSAF advisories for resolved vulnerabilities in a format that enables automated processing by retail customers' vulnerability management tools
Article 14 Incident Reporting for Payment Products
Active exploitation of a payment terminal vulnerability - for example, a skimming attack exploiting firmware vulnerability or a network-level attack on POS terminals - triggers Article 14's 24-hour ENISA notification requirement. Payment terminal exploitation is a financially motivated attack that typically occurs at scale, making rapid notification and response critical.
- ENISA (CRA Article 14 - 24 hours)
- Payment card schemes (Visa, Mastercard incident notification requirements under scheme rules - typically within hours for active fraud-enabling compromises)
- PCI SSC for PCI-approved products - compromised PCI certifications must be reported
- Retail customers - particularly large retailers who may be experiencing active fraud as a result of terminal compromise
Vendors should pre-establish communication protocols with payment scheme security contacts and major retail customers to enable the parallel notification required within the Article 14 timeframe.
Conformity Assessment and PCI Alignment
A payment terminal that is a critical product needs a European cybersecurity certification scheme where a delegated act under Article 8(1) requires one. No such delegated act is adopted yet. Until then, the terminal uses the Class II procedures (Article 32(4)). These are EU-type examination (Module B plus Module C), full quality assurance (Module H) or a European cybersecurity certification scheme specified under Article 27(9) at assurance level substantial or higher, for the requirements it covers (Article 32(3)). Module A is not open to a critical product. Default-class POS software, tills and kiosks can use Module A internal control (Article 32(1)). Vendors should leverage existing PCI PTS approvals and PCI PA-DSS/MPoC certifications as supporting evidence for CRA assessment - the security controls evaluated under PCI schemes overlap substantially with CRA Annex I requirements.
- PCI PTS approval demonstrates physical and logical security of the payment terminal hardware - directly relevant to Annex I device security requirements
- PCI PA-DSS certification (or successor standards) demonstrates application security for payment software
- PCI P2PE validation supports CRA Annex I data confidentiality requirements
However, PCI certifications do not substitute for CRA conformity assessment - they provide supporting evidence. The CRA assessment must additionally verify the CVD policy, SBOM, and lifecycle vulnerability management process, which are outside PCI's scope. Notified bodies conducting CRA assessments for payment terminal vendors will likely have significant familiarity with PCI frameworks, facilitating efficient assessment processes.
Work through the CRA for each product in one workspace.
Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Does PCI DSS compliance satisfy CRA requirements for payment terminals?+
PCI DSS and PCI PTS compliance provide strong technical security foundations that overlap significantly with CRA Annex I requirements - particularly for encryption, access control, firmware integrity, and physical security. However, they do not cover the other CRA obligations. These are a publicly accessible CVD policy (Article 13), ENISA reporting of actively exploited vulnerabilities (Article 14), SBOM maintenance, a declared support period and a CRA conformity assessment. A physical payment terminal that is a critical product (Annex IV, point 1) needs a notified body or a European cybersecurity certification scheme required under Article 8(1) or specified under Article 27(9) for that assessment (Article 32(4)). Payment terminal vendors should treat PCI compliance as a foundation and implement the CRA-specific additions on top of their existing PCI programme.
Are SoftPOS (software-only payment apps on commercial smartphones) subject to the CRA?+
SoftPOS applications that turn commercial off-the-shelf (COTS) smartphones and tablets into payment acceptance terminals are products with digital elements within CRA scope when distributed as commercial software on the EU market. The underlying smartphone hardware is subject to the hardware manufacturer's CRA obligations; the payment application software is the SoftPOS vendor's product with digital elements. CRA Annex I security requirements apply to the software's design, update mechanisms, and data protection. PCI MPoC (Mobile Payments on COTS) certification requirements overlap substantially with CRA Annex I for SoftPOS applications.
How do self-service kiosk vendors with integrated payment handle CRA compliance?+
Self-service kiosks with integrated payment terminals - ticketing machines, self-checkout stations, fuel dispensers with payment - are complex products that may have multiple digital elements within CRA scope: the payment terminal component, the kiosk operating system, the application software, and any network management interfaces. The kiosk vendor placing the complete system on the EU market is responsible for CRA conformity of the entire integrated product. The kiosk itself is default class. An integrated physical payment terminal that meets the Annex IV, point 1 description is a critical product in its own right, and its manufacturer carries out the conformity assessment for it. Integration does not make the kiosk a critical product. The kiosk vendor must still ensure the integration does not compromise the overall system's security.
Key CRA articles for Point-of-Sale & Payment Terminal Vendors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Need a CVD policy template for Point-of-Sale & Payment Terminal Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.