Payment terminals are often certified, sold and installed – then quietly treated as if the security job is done. That “set and forget” mindset is becoming harder to defend. Many devices remain in use for years, especially across cafés, restaurants, convenience stores and other smaller merchants. During that time, software changes, vulnerabilities emerge and attackers find new ways to exploit weaknesses.
The problem is not that merchants are ignoring a responsibility they should own. Most do not have the knowledge, tools or capacity to monitor vulnerabilities in the payment devices they use every day. Manufacturers build those devices. PSPs, acquirers and payment providers often distribute or support them as part of a merchant service. Yet responsibility for monitoring exploitation, communicating risk and managing updates can still fall between the organisations involved.
The EU Cyber Resilience Act (CRA) brings that gap into sharper focus. Since11 September 2026, OEMs and manufacturers selling into the EU now need to report actively exploited vulnerabilities and severe security incidents. With an early warning within 24 hours and a fuller notification within 72 hours. But those obligations may collide with the reality that many device manufacturers are not currently required to monitor how criminals target vulnerabilities in their products. And may lack the intelligence capabilities needed to detect exploitation quickly.
For PSPs and acquirers, this matters because they are often closest to the merchant relationship. They may not manufacture the terminal or carry the manufacturer’s CRA obligations, but merchants will still expect them to explain what is happening. Also to pass on updates and help decide whether a device needs to be patched, replaced or retired. That is why a manufacturer-led regulatory obligation quickly becomes a payments ecosystem issue.
The challenge starts after certification
When a payment device is first deployed, the industry standard, PCI PTS compliance confirms that it has passed industry driven testing required to operate within the payment system. That gives buyers confidence that the device met recognised security requirements at the point of approval and had gone through a rigorous approval process.
But certification cannot account for every attack technique or vulnerability that emerges afterwards. A device may have been compliant when purchased, but that does not mean it remains secure for years. The longer it stays in the field without lifecycle assurance, the harder it becomes to know whether it is still protected.
Large merchants such as supermarket chains often have fleet management systems that support device lifecycle management. Smaller merchants rarely have the same visibility over the terminals they use day to day. The risk is that they may be exposed if patching, updates, incident notifications or end-of-life support are not clearly communicated by the providers they rely on.
The “set and forget” challenge
The payments industry has built strong foundations for device security. The challenge now is ensuring those devices remain secure long after they enter service. That requires more than paperwork: periodic testing, real-world attack simulation and evidence that payment devices can withstand threats outside the certification lab.
Attackers are also able to identify and exploit vulnerabilities faster than before, and AI is accelerating that shift. Modern tools can scan large volumes of code and help surface high-severity weaknesses at speed. A vulnerability in a retailer’s card terminal that might once have gone unnoticed could now be discovered, shared and exploited far more quickly.
Second-hand and decommissioned payment terminals create another risk. Once a device leaves a merchant’s control, visibility over its contents, software history and configuration often disappears. Buying one can be like buying a locked safe. Few people know what is inside, but skilled researchers and attackers are motivated to find out.
For payment providers, this creates an opportunity to build stronger merchant propositions around lifecycle assurance. Clearer device inventories, update notifications, end-of-life planning and support models can help merchants know when action is needed. Making security part of the payments service experience rather than an afterthought once a terminal has been installed. This also gives providers a clearer way to differentiate beyond price. By showing merchants that resilience, continuity and practical support are built into the service from the outset.
Why PSPs will play an increasingly important role
Smaller merchants need practical, timely information from the PSPs, acquirers and payment providers they already depend on. They need to know whether a device is still supported, whether an update is needed, and what action to take if a vulnerability or incident affects them.
Ongoing testing can help OEMs, manufacturers and payment providers understand whether devices remain secure as the conditions and context of the environments devices are deployed in change with time. It can surface issues after deployment, from physical tampering and insecure administration to outdated firmware, weak update processes or vulnerabilities in embedded components. The ecosystem needs a clearer model for identifying and communicating risk before merchants and customer data are exposed.
For PSPs and acquirers, the action is clear. They need processes for receiving manufacturer updates, assessing which merchants may be affected, escalating incidents quickly and explaining when a terminal should be patched, replaced or retired. That does not make them responsible for the manufacturer’s CRA obligations. But it does make lifecycle communication part of the merchant service they provide.
Recognising the opportunity
For the payments industry, this is the opportunity. They can turn manufacturer-led lifecycle obligations into a practical assurance model for merchants that drives up the overall resilience of the industry’. Providers that combine clear accountability with independent security testing, timely communication and long-term support will be better placed to compete on trust, resilience and service quality.
The CRA should be seen as a reset rather than new requirements to adjust to. Compliance to PCI SSC standards will continue to matter. But it should be treated as the starting point, not the finish line. In a payments market defined by speed, resilience and trust, the real test is no longer simply whether a terminal was secure when it was certified. It is whether the industry can prove it remains secure in the field, every day it is used.
Learn more at pcacybersecurity.com
- Cybersecurity in FinTech
- Digital Payments










































































































