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.
