Home Contents | # v4kf:chipIdentify | V4kf | Core4 Lua Event System

## SYNOPSIS

rdrhandle:chipIdentify(flags)

## DESCRIPTION

DEPRECATED - Please use v4kf:chipActivate() for new projects.

Enable a SmartCard chip using T=0 or T=1 protocol (auto-detected). Read public identification data from EMV compatible chips and EF_ID from german "EC-Karte mit Chip".

This command can only be used if the reader is in the Locked state, which secures the chip card against removal during operation.

While this state processes, the reader is in the Processing state and v4kf:isProcessing() returns true. The reader returns to the Locked state on completion.

The command returns immediately. Actual execution of any reader operation is done within the event loop.

The processing result is provided with the v4kf.processingComplete() callback. The data passed to the callback contains the information that was read from the chip. It is encoded using the ISO7816/EMV Tag-Length-Value method.
If an EF_ID could be read, the EF_ID data is tagged using 0xCF, which lies in the private range as of ISO7816-4. This allows returning EMV and EF_ID in one block.

The optional flags parameter contains the following modifier bits:

flag | Description
--- | ---
1 | For EMV, stop reading data from the card as soon as the tag 0x57 (Track 2 Equivalent Data) has been found. This speeds up the access considerably, and returns enough data to safely identify the card.
2 | Normally, the systems tries to read EMV data and EF_ID, as some cards contain both. This flag causes reading to skip the EF_ID read if Track2 Equivalent Data has already been acquired.

## NOTES

The tagged data can be decoded using v4kf.emvDecode() and v4kf.emvLookup().

## SEE ALSO

v4kf:chipDisable, v4kf:chipEnable, v4kf:chipRead, v4kf:chipWrite, v4kf:chipActivate, v4kf:state, v4kf.emvDecode(), v4kf.emvLookup()