loader

Operational efficiency by managing EMV parameters on the Cloud

When EMV L2 kernel runs on the device, it is very difficult to manage EMV parameters such as contactless CVM limits. Most of the time, EMV kernel parameters are maintained in an XML, JSON, or text file. For each update, regression tests are required before pushing to devices in the field and monitoring of transactions after pushing. Sometimes, the parameters can’t be pushed to some terminals due to hardware or network issues. If a parameter turns out to be wrongly personalized, all the devices in the field should be pushed again. Sometimes, the parameter update occurs just in the middle of an EMV transaction, which is a bad experience for the merchant and the customer.

There is no need to interrupt payment transaction during the parameter loading process

The EMVKernel-on-the-Cloud solution maintains all EMV parameters on the cloud, not on the device. There is no need for pushing them to devices when a parameter is updated. There is no need to interrupt the payment transactions during the parameter loading process. If there is any field issue after the update, it can be easily reverted back through web-based UIs. The impact of parameter update can be monitored with EMV Reporting Service and any problem can be easily identified.

 

The kernel on the device

The EMVKernel-on-the-Cloud

EMV parameters are managed in

The XML(JSON) file

The cloud

Updates take effect in

From 1 day to 1 month, requiring regression tests and pushing process to live devices

Immediately

Who may do the update

Only POS owner

Acquirers, Payfacs, Partners, ISOs, ISVs using Web APIs

User Interface to show EMV details

No user interface

Web user interfaces to show EMV tags, bits, descriptions

EMV parameters can be updated by

Only technical people with deep EMV knowledge

Anybody having basic EMV understanding

Human errors

Can’t be identified as XML(JSON) files can’t check the errors

Can be identified easily as Web APIs checks the update based on EMV rules

Deployment

All POS terminals need to be pushed in the field

No need for pushing to the POS terminals in the field

Revert back in case of wrong parameter settings

No chance to revert back immediately after pushing

It can be reverted back immediately if something is wrong

Interruption of payment transaction

It may happen if the merchant is making a transaction during the update

It never happens as the update is done on the cloud.