Tools

EMV Log Analyzer

Drop an EMV test log and get the points worth a look highlighted, exchange by exchange: status words other than 9000 first, then data lengths, the Mastercard TVR and the Visa TTQ, CTQ and cryptogram checked against each other. A help for your analysis, not a verdict.

Your log stays on your device. It is analysed in your browser and never uploaded. Use test cards only.
Drop a log here EVAL HTML log, KaNest text or XML log, or a list with one APDU per line No file loaded.
Or paste a log or APDUs

What it checks (version 1)

Status words first

Every response other than 9000, and every command the card never answered, is flagged and explained according to the command it answers: for example 6A82 on a SELECT, 6985 on GET PROCESSING OPTIONS, or 6A85 when the command data does not match what the card expects.

Data object lists

The data in GET PROCESSING OPTIONS and GENERATE AC is checked against the length requested by the card's PDOL, CDOL1 and CDOL2.

Mastercard (Kernel 2)

The TVR is read from the GENERATE AC data and decoded with the Kernel 2 layout, including the relay resistance bits. The tool also checks that the cryptogram returned is not stronger than the one requested, and that the AIP, the CDA request and the signed data in the response agree.

Visa (Kernel 3)

The TTQ is read from the GET PROCESSING OPTIONS data and checked for contradictions. The card's CTQ and CID are then checked against it: a TC when an online cryptogram was required, a CVM the reader does not support, or a CVM required without any CVM from the card.

Points to look at, not verdicts

Each finding points to where to look; whether it is a problem depends on the test case. The rules grow with each version; tell us through Support when a finding is wrong or something is missing.

Related articles