67% found this document useful (3 votes)
3K views3 pages

EMV Transaction Result Analysis

The document provides suggestions for analyzing EMV transactions, including checking for mandatory and optional tags, referring to EMVCo specifications, and looking for specific tags and behaviors that indicate details like whether a transaction was approved online or offline, whether it involved chip reversal or cardholder verification methods. It also notes additional tags and fields to check for scenarios like fallback to magstripe, issuer scripts, and issuer script results.

Uploaded by

m_ramesh31
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
67% found this document useful (3 votes)
3K views3 pages

EMV Transaction Result Analysis

The document provides suggestions for analyzing EMV transactions, including checking for mandatory and optional tags, referring to EMVCo specifications, and looking for specific tags and behaviors that indicate details like whether a transaction was approved online or offline, whether it involved chip reversal or cardholder verification methods. It also notes additional tags and fields to check for scenarios like fallback to magstripe, issuer scripts, and issuer script results.

Uploaded by

m_ramesh31
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Some suggestions for analyzing EMV transactions and results

 Check Mandatory Tags are present in the Transaction request as suggested by the Host
specification (Vantiv/FirstData…etc). Please thoroughly refer to the specific EMV sections in
these documents as the information is scattered across and you will need to collate it.

 Check Optional Tags are present in the Transaction request as suggested by the Host
specification (Vantiv/FirstData…etc). You may have to refer to Local Journal for cross
verification. Please thoroughly refer to the specific EMV sections in these documents as the
information is scattered across and you will need to collate it.

 Always, Refer to EMVCo Book 3 and Book 4 for any more/additional information.

Transactions/Conditions EMV Tags and other Additional Comments


behaviors to Look / Check / FYI
Transaction is Sent for Online Authorization Value of 9F27 = 80 (ARQC) The Chip and POS
OR Check that 9F26 exists have MUTUALLY
Online (Authorization) Request (Application Cryptogram) decided to go to the
Host (issuer) to decide
9F27 is called Cryptogram the outcome of the
Information Data (CID) transaction.

This is sometimes
referred to as Online
Mutual
Authentication.
Transaction is Declined ONLINE by HOST Value of 9F27 = 00 (AAC) 8A (Authorization
Value of 8A is not “00” Response Code) is
(3030) sent back in the Host
response
Transaction is Offline Approved Value of 9F27 = 40 (TC) The transaction has
OR been locally approved
Offline Approval/Authorization Value of 8A = Y1 (or Y3, if between the POS and
terminal is unable to go the Chip card (without
online) ever going to the
host…)
Transaction is Approved ONLINE by HOST Value of 9F27 = 00 The POS and Chip
Value of 8A = “00” (3030) have decided to go to
the host (issuer) to
decide the outcome.
The host has
approved the
transaction. 8A
(Authorization
Response Code) is
sent back in the Host
response
Transaction is Offline Declined Value of 9F27 = 00 The transaction has
OR been locally declined
Offline Declined Value of 8A = Z1 (or Z3, if between the POS and
terminal is unable to go the Chip card (without
online) ever going to the
host…).
No meaning to go to
host for its decision.

Cardholder Verification Methods (CVMs) 1) Check and Interpret TVR Refer EMVco Books 3
Bytes/Bits and 4 for
>Offline PIN 2) Check and Interpret for interpretation.
>Online PIN 9F34 CVM Results
>Signature 3) Online PINs contain PIN
BLOCK/PIN DATA in Request
4) Offline PINs do not have
such data in Request

Fallback Scenario Chip transaction fails and It is good to Check for


you are prompted to Swipe (POS) Entry Mode
the card field to indicate that
Magstripe was used as
the Entry mode (check
for the exact values
of EMs with the team)
Chip Reversal 9F27=00 (AAC/Decline, most Chip will REVERSE the
common scenario of Chip outcome of the
reversal) Transaction. For
example, if Host says
9F27 = 40 (TC/Approval, approved, Chip will
technically possible, rarely reverse it and say it
happens) declines (and vice
versa).

Usually a Chip reversal


means a DECLINE
(9F27 = 00) by the
Chip
Issuer Scripts 71, 72 Issuer Scripts are sent
by the Host to the POS
in the Response
message. These are
optionally sent and
may not be present
for all transactions
(which is the most
usual scenario).

These are sent for


example, to block a
card, to unblock a PIN,
to unblock an
application etc.
Issuer Script Results (ISRs) 9F5B - Refer to Host spec This EMV tag captures
document for this tag. the Results or the
outcome of the Issuer
scripts that were
executed.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy