0
When we speak about EMV and Level 2 kernels, contact and contactless, the assumption has always been that they live inside the POS terminal.
Embedded in the hardware, certified for that specific device, tied to that specific OS. That has been the standard model for decades.
The times have changed with the introduction of cloud kernels. And the change is substantial enough that terminal vendors, acquirers, and payment solution providers need to understand what it means for their certification strategies, go-to-market timelines, and long-term infrastructure costs.
The cloud kernel moves the EMV L2 kernel from the terminal to the cloud.
The terminal communicates with the kernel over the network during a transaction, rather than processing the EMV logic locally. It sounds like an architectural shift, but the downstream implications for certification, maintenance, scalability, and cost are anything but impactful.
The most immediate benefit of the cloud kernel model is the reduction in EMV Level 2 certification cost and effort. Under the traditional embedded kernel model, when a terminal vendor wants to bring a new terminal to market, they must certify the entire device, the hardware, the OS platform, and the kernel together. Any change to the hardware or OS triggers the certification process again, from scratch.
With a cloud kernel, the L2 certification applies to the kernel running in the cloud, not to any specific terminal hardware. Once that cloud kernel holds its L2 certification, terminal vendors integrating with it need only certify the L3 application. The full L2 certification process does not need to be repeated for each new terminal. That is a real saving in both time and cost, particularly for vendors managing multiple terminal models across markets.
Cloud kernels have been around long enough to have proven their value, yet adoption has been slower than the advantages might suggest. The hesitation is not irrational. There are legitimate considerations that terminal vendors and acquirers need to work through before committing to a cloud kernel architecture.
Latency is the most frequently cited concern.
If the L3 application and the cloud kernel are connected through a reliable internet connection, transactions complete quickly. But in environments where connectivity is limited to 2G, 3G, or 4G networks, or where connectivity is intermittent, the data trip to the cloud introduces potential delays that can affect transaction speed and customer experience.
Security is the second consideration. Moving card and cardholder data to the cloud requires more than EMV's built-in secure protocols. PCI DSS certification is required to ensure that data in transit is handled correctly. A manageable requirement, but one that adds a step that embedded kernel deployments do not face in the same way.
The availability of L2 certification was a barrier when cloud kernels were first introduced. The number of kernel vendors holding cloud kernel L2 certification was small, limiting options for terminal vendors looking to adopt the model. Availability has improved considerably as payment networks and EMVCo have updated the L2 certification process to support kernels running across different platforms. Still, it remains a factor worth checking early in any project.
Internet dependency is a basic constraint.
A cloud kernel cannot function without connectivity. For deployment environments that require offline transaction capability, the cloud kernel model needs careful evaluation.
Contactless kernel certification adds another layer of complexity.
Payment brands have historically been cautious about issuing L2 certificates to cloud-based contactless kernels where the EMV kernel is not demonstrably performing at the expected transaction speeds. The certification landscape in the area continues to evolve, and vendors should verify current payment brand requirements before proceeding.
Setting these considerations aside, which are manageable in most deployment contexts, the advantages of cloud kernels are worth examining.
Reduced hardware dependency is one of the most practical benefits.
In the traditional embedded model, an L2 kernel certified for one OS platform must undergo the full L2 testing and certification process again when ported to a different OS. With a cloud kernel, the kernel is not tied to any specific hardware or OS. The same certified kernel can be accessed by terminals running on different platforms without triggering a new certification cycle.
Easy patching of configuration files removes one of the more operationally demanding aspects of embedded kernel management.
When a kernel configuration file needs to be updated in an embedded deployment, the update must be pushed individually to each terminal, preceded by regression testing to confirm the patch does not introduce unexpected behavior.
With a cloud kernel, configuration updates are applied once in the cloud and take effect immediately across all connected terminals. Rolling back a patch is equally straightforward.
Easier troubleshooting is a benefit that becomes clear once a deployment is live.
Embedded kernels face storage limitations that constrain how much transaction log data can be retained on the terminal. Cloud kernels have no such restrictions.
Full transaction logs are available in the cloud, making it considerably easier to diagnose and resolve transaction errors without the constraints of terminal-side storage.
No memory limitations remove another common hardware constraint.
In embedded deployments, L2 kernels run in the terminal's L1 memory. If a terminal vendor wants to add a second kernel to an existing terminal and the available memory is insufficient, the L1 hardware itself may need to be upgraded or replaced. Cloud kernels carry no memory restrictions. Adding kernel support does not require any hardware change.
For teams concerned about the learning curve of cloud kernel certification, the test tools and test scenarios used for embedded kernel certification apply equally to cloud kernel certification. No need to invest in new tooling or rebuild test expertise from scratch.
With the continued advancement of cloud technologies and the growing adoption of cloud POS in the payments ecosystem, the cloud kernel model has matured into a credible and proven system. Payment networks and EMVCo have responded by evolving the L2 certification framework to more explicitly support it.
The cloud kernel will be a serious place in the conversation if you are:
The real question is whether your team has assessed cloud kernels properly against your deployment context.
.png)
