Extended TVR helps you to find out transaction issues in a short time for your POS terminals.
POS systems are getting more complicated each day. There are many EMV kernels, new use cases (i.e tap to phone) and new form factors (i.e tablets, card readers, and phones) contributing to this complexity. With all these advancements, there are more risk of errors or bad user experiences during transactions. Keeping payment transactions safe from transactional and UI errors will help acquiring customer satisfaction and trust.
At the core of a payment transaction, EMV L2 kernel runs to perform critical tasks such as card communication, offline and online authentication, cardholder verification and risk management. Traditionally, these kernel have run on embedded chips with limited logging ability. However, with Fairbit Cloud, now it runs on the cloud and gives enormous opportunity to get advanced logs in the real time.
Give the Comfort to Merchants by Fixing Transactional Issues in a Live Merchant Environment Very Quickly
It is quite often something unexpected to happen, and transactions not to completed successfully in a live merchant environment. With the embedded EMV kernel, it is quite difficult to know what is going on. There may be a negative user experience such as POS not asking for the signature or showing an error message even though transaction was approved. Merchant may be performing a transaction with debit card, but the device may not be asking for the PIN. Or POS may be giving an awkward user message when cardholder inserts the card and transaction is declined offline. When these issues happen, it is extremely important to get it fixed in very short time. Most of time, merchants call the call center, but nobody can figure out easily why all these are happening. With Fairbit cloud kernel’s advanced logging of transaction data, addressing these issues are much easier.
Shorten Your EMV L2, L3 Certifications by Figuring Out Issues in The Short Time
During EMV L2 and L3 certifications or internal regression tests, one of the most encountered issues are that something goes wrong in a test scenario. For example, for some reason contactless tests may be rejected for a brand and L3 tester doesn’t have an idea. Or card declines transaction offline while test case expects online approval. Or maybe an EMV parameter has a different value from what test case expects. What can be reason of these issues? Maybe a wrong configuration parameter. Or newly deployed POS operating system has a regression. Or missing public key? These issues are mostly sent to the POS or EMV kernel vendor it takes quite a bit of time as there is not enough log about the transaction. A simple configuration issue in the device may have caused weeks, even months of the delay in L3 certification. With Fairbit cloud kernel’s monitoring module for the APDUs, Extended TVR and, other transaction data EMV certifications will be significantly shortened.
Win The Customer with The Best User Experience
The best user experience helps winning customer. Knowing the root cause of transaction issues is essential to prevent transaction declines and negative use cases. Today, EMV kernels generally work in secure chips with limited resources, and they have limited logging abilities. And in most cases, these logs remain in terminals and can’t be monitored or easily accessed.
Among many features of Fairbit Cloud Kernel, one outstanding feature is the advanced transaction log parameter : Extended TVR.
TVR vs Extended TVR
TVR (Terminal Verification Results) is an EMV terminal parameter where you can find information about transaction, especially error cases. You can find more information about TVR in https://www.emvco.com. POS device sets results of certain operations in TVR bits. For example, if offline authentication fails, then corresponding TVR bit is set so that acquirers, issuers, and whoever has access to the Fairbit monitoring portal may know more about the transaction. However, TVR was developed more than 20 years ago with the initial version of EMV and it doesn’t include all required information about the transaction. Over the time since EMV standard was published, the payment market players have encountered with various critical situations not addressed by TVR. For example, although TVR informs that offline authentication failed, it doesn’t inform the reason if it. It may be because of missing Certificate Authority Public key, or something different.
Extended TVR is a Fairbit cloud kernel parameter with comprehensive information about transaction. TVR has 40 bits, but Extended TVR has more than 200 bits. Each bit represents result of an operation in the transaction.
Operators, developers or analysts can investigate Extended TVR bits and they will have all critical information to figure out the issue in the transaction. They will know what operation failed and what is the result of the failure.
Unlike embedded EMV kernels, Fairbit cloud kernel logs all transaction parameters except the ones not allowed by PCI in the online. Anybody who has access to Fairbit portal can see these logs in a few seconds following the transaction. Having all the information accessible, POS platform providers can take immediate actions to fix issues in the production or during EMV L2 and L3 certifications. Online monitoring portal has filtering and search features to facilitate accessing specific transactions. You can filter transactions with various parameters such as date and amount. When you select a transaction, you can see APDU commands, EMV terminal parameters, EMV tags, transaction result, Extended TVR and all other relevant parameters.
Fairbit Cloud kernel with advanced monitoring portal and Extended TVR will help you to get your EMV L2 and L3 certifications faster and get your merchants secure from transactional issues. You can find more information about Fairbit cloud kernel in this link : https://fairbit.com/emv-kernel-on-the-cloud/