Using a high-level-language SDK, write code (in C/C++, C#, Objective-C, Java, or Swift) that harnesses the appropriate ID TECH SDK library to issue the underlying firmware command(s).

Establish connectivity (typically using USB or RS-232) with the reader, and send firmware commands to it directly.

How do you send commands to the reader? There are two choices: The payment app developer will actually send commands to the reader and the reader will handle the necessary underlying interactions with the kernel, which (in turn) will interact with the card. In other words, it’s out of reach for the payment-app developer, who only needs to worry about issuing commands to the kernel (not to the card itself). Almost all of the card-reader logic for this is cordoned off in what’s known as an EMV Level 2 kernel. The major events of that flow can be summarized this way:Īt each stage of this process, the card reader talks to the chip on the smart card, using some very low-level protocols defined in ISO-7816. The first half of this 25-page white paper is a refresher on EMV event flow. Others are new to EMV itself.Īs a point of reference, we usually recommend to integrators that they take a look at ID TECH’s free white paper called EMV Transactions with the Universal SDK.

Some have worked with EMV before, but don’t know contactless EMV. Most customers know payment systems very well in the context of MSR (magstripe readers). But even so, there’s a lot of variation in the degree of EMV knowledge customers bring to a new project. Most new ID TECH customers are pretty technically savvy. ViVOpay VP8300 3-way card reader EMV: Where to Start?

Java emv card reader