In our case, there is no verification failure, because there was no verification. Byte 2 bit 2 = 0 Offline PIN verification passed or not performed - in essence, it means that the offline PIN verification did not fail.Byte 2 bit 3 = 0 Offline PIN verification not performed.In essence, it means that the authentication of the issuer did not fail. Byte 2 bit 4 = 0 Issuer Authentication successful or not performed - the authentication of the issuer was either not performed or successful.Byte 2 bit 6-5 = 10 AC returned in 1st GENERATE AC: ARQC is the cryptogram resulting from the exchange - ARQC (Authorisation Request Cryptogram), i.e., the online request to the issuer.
Byte 3 bit 8 = 0 Issuer Update Processing not supported - the capability to transmit the issuer scripts to the card is not supported.Byte 2 bit 5 - 1 = 0 RFU - : bytes 5 to 1 are reserved for future use.Byte 2 bit 6 = 1 (Contact Chip) Offline PIN supported - «Offline PIN» CVM method for the contact chip is supported.In our case, the transaction amount is small (see below), which is why bit = 0. That bit is dynamic and to be introduced depending on the transaction amount and terminal limits. Byte 2 bit 7 = 0 CVM not required - cardholder verification is not required.Byte 2 bit 8 = 1 Online cryptogram required - online transaction cryptogram verification by the issuer is required.Byte 1 bit 1 = 0 Offline Data Authentication(ODA) for Online Authorizations not supported - ODA is not supported.Byte 1 bit 2 = 1 Signature supported - «Signature» CVM method is supported.Byte 1 bit 3 = 1 Online PIN supported - «Online PIN» CVM method is supported.Byte 1 bit 4 = 0 Reader is Online Capable - the device has the online authorization capability.This bit is needed for the card to be able to send the command to Switch Interface upon occurrence of certain events, i.e., to suggest the use of the contact chip (see below). Byte 1 bit 5 = 1 Contact VSDC supported - the interface of the contact chip is supported.Byte 1 bit 6 = 1 Contactless qVSDC supported - the contactless interface in the chip (qVSDC - Quick Visa Smart Debit Credit) emulation mode is supported.Byte 1 bit 7 = 0 RFU - reserved for future use.Byte 1 bit 8 = 0 Contactless magnetic stripe not supported - the contactless interface in the magnetic stripe emulation mode is not supported.SW1 and SW2 combined are the status word (SW). The response APDU has an optional body consisting of data and a mandatory trailer with two status bytes "SW1" and "SW2". The card will execute the command and send a response APDU back to the terminal.
If Le is 0x00, at maximum 256 bytes are expected. Number of data bytes expected in the response. You don't have to specify this parameter. With the Smart Card Shell the value of Lc will be calculated automatically. The value and meaning depends on the instruction code (INS). This command has a mandatory header and an optional body. The terminal sends a command APDU to the card. APDU - Application Protocol Data UnitĪfter the reset, the communication between terminal and card works with APDUs. Within an ADF youĬan select AEFs with the Short File Identifier (SFI). You can quickly select an ADF with the Application Identifier (AID). Inside of an ADF are Applicaton Elementary Files (AEF) that contain data. The MF has one or more Application Definition Files (ADF). The topmost file is the Master File (MF). The files on a smart card are organized in a tree structure.