Skip to content
EMV Tools

Tools

Every tool runs in your browser. Nothing you paste is sent to a server, stored, or logged.

How an EMV transaction flows

The main steps between a chip card and a terminal, in order. Each step links to the tags and tools that explain its data.

  1. SELECT

    The terminal chooses the payment application by its AID. The card answers with the PDOL, the list of terminal data it needs next.

  2. GET PROCESSING OPTIONS

    The terminal sends the PDOL data. The card returns the AIP, the functions it supports, and the AFL, the records to read.

  3. READ RECORD

    The terminal reads each record that the AFL lists: the PAN, the expiry date, the CVM List, the CDOL1, and the certificates.

  4. Offline data authentication

    The terminal checks the signed card data with SDA, DDA, or CDA, as the AIP allows. A failure sets a bit in the TVR.

  5. Cardholder verification

    The terminal walks the CVM List to choose how to verify the cardholder, such as a PIN or a signature, and stores the outcome in the CVM Results.

  6. Terminal risk management

    The terminal checks the floor limit, random selection, and velocity, and sets the matching bits in the TVR and the TSI.

  7. GENERATE AC

    The terminal asks the card for a cryptogram. The CID says what the card returned: a TC to approve offline, an ARQC to go online, or an AAC to decline. The IAD carries issuer data.

  8. Online authorization

    The ARQC and the chip data travel to the issuer in DE 55 of an ISO 8583 message. The issuer answers with a response code and can add issuer authentication data.