EMV CVM Result Related

Contact EMV

For the contact EMV, Most of Vendor build one EMV kernel for all scheme(L2), so the CVM result is also identified with CVM result(9F34), and can easily find what should be done from L3 app side based on the CVM result.

So the actual CVM result is based on like Terminal Cap(9F33), CardHolder verification Method(CVM) list（8E from card）

 

Contactless EMV

For the Contactless EMV, normally, the Ctls L2 EMV structure is diff like contact, the structure is one Entry point Kernel + (Diff scheme kernel).

So every scheme will have a separte kernel to handle the subsequent EMV flow after do pre-processing with Entry point kernel.

Every kernel may used diff tag to define a CVM limit to handle CVM processing logic.

Visa -- DF01，Reader CL CVM limit, TTQ(9F66), and get result based on CTQ(9F6C)

MasterCard -- DF8126, PP Terminal Risk Management(9F1D), get result based on CVM result(9F34)

CUP(UPI) -- DF01, simlilar like Visa, but got own regulation, and need to based on AID(credit Card and Quasi Credit) and CVM limit do some special handling.

JCB -- DF01, Tag 9F53(TIP) from terminal and Tag 9F50 from card to decide CVM, card result may overwrite the terminal Requested CVM result

AMEX -- DF53

 

TODO: may add more infor later when got free.