EMV Tag Reference
Tools/EMV Tag Reference/95
TerminalFormat: bLength: 5
95

Terminal Verification Results (TVR)

Tag ID
95
Format
b
Length (bytes)
5
Source
Terminal

What it is

The Terminal Verification Results (TVRTerminal Verification ResultsEMV tag 95 — a 5-byte bitfield recording the outcome of the terminal’s risk and verification checks.View in glossary →) is a 5-byte bitmap in which the terminal records everything that went wrong or was noteworthy during the transaction: offline authentication outcomes, application version/usage issues, CVMCardholder Verification MethodHow the cardholder is verified — for example offline PIN, online PIN, signature, or no CVM required.View in glossary → problems, risk-management triggers, and issuer/script results.

The TVRTerminal Verification ResultsEMV tag 95 — a 5-byte bitfield recording the outcome of the terminal’s risk and verification checks.View in glossary → is matched against the Issuer Action Codes (9F0D/0E/0F) and Terminal Action Codes to reach the offline/online/decline decision, and it is one of the inputs to the application cryptogram.

Where it appears

Built up by the terminal throughout processing; input to action-code analysis and GENERATE ACApplication CryptogramA cryptogram the card generates to approve or decline a transaction: TC (approve offline), ARQC (go online), or AAC (decline)..

Specification reference

Defined in: EMV 4.x Book 3 (Application Specification), Annex A — Data Element Dictionary

Bit-level definitions below follow: EMV 4.4 Book 3, Annex C5, Table 46 — Terminal Verification Results (5 bytes)

Bit & value breakdown

EMV 4.4 Book 3, Annex C5, Table 46 — Terminal Verification Results (5 bytes)
Byte 1 — Offline Data Authentication
b8 = 0x80Offline data authentication was not performed
b7 = 0x40SDAStatic Data AuthenticationOffline check where the terminal verifies a fixed issuer signature over static card data. It cannot prove the card is live, so it is vulnerable to cloning and replay.View in glossary → failed
b6 = 0x20ICCIntegrated Circuit CardThe chip embedded in the card — i.e. the EMV “chip” itself.View in glossary → data missing
b5 = 0x10Card appears on terminal exception file
b4 = 0x08DDADynamic Data AuthenticationOffline check where the card signs unique, per-transaction data with its own private key — proving the chip is genuine and not a clone.View in glossary → failed
b3 = 0x04CDACombined DDA / Application Cryptogram generationThe strongest offline authentication: the card signs the dynamic data and the transaction cryptogram together in one step, preventing tamper (“wedge”) attacks.View in glossary → failed
b2 = 0x02SDAStatic Data AuthenticationOffline check where the terminal verifies a fixed issuer signature over static card data. It cannot prove the card is live, so it is vulnerable to cloning and replay.View in glossary → selected
b1 = 0x01XDA selected (EMV 4.4)
Byte 2 — Application Version / Usage
b8 = 0x80ICCIntegrated Circuit CardThe chip embedded in the card — i.e. the EMV “chip” itself.View in glossary → and terminal have different application versions
b7 = 0x40Expired application
b6 = 0x20Application not yet effective
b5 = 0x10Requested service not allowed for card product
b4 = 0x08New card
b3 = 0x04RFUReserved for Future UseBits or bytes with no current meaning, reserved by the spec; they must be set to zero. — must be 0
b2 = 0x02Biometric performed and successful (EMV 4.4)
b1 = 0x01Biometric template format not supported (EMV 4.4)
Byte 3 — Cardholder Verification
b8 = 0x80Cardholder verification was not successful
b7 = 0x40Unrecognised CVMCardholder Verification MethodHow the cardholder is verified — for example offline PIN, online PIN, signature, or no CVM required.View in glossary →
b6 = 0x20PIN Try Limit exceeded
b5 = 0x10PIN entry required and PIN pad not present or not working
b4 = 0x08PIN entry required, PIN pad present, but PIN was not entered
b3 = 0x04Online CVMCardholder Verification MethodHow the cardholder is verified — for example offline PIN, online PIN, signature, or no CVM required.View in glossary → captured (“Online PIN entered” before EMV 4.4)
b2 = 0x02Biometric required but biometric capture device not working (EMV 4.4)
b1 = 0x01Biometric required, capture device present, but biometric subtype entry was bypassed (EMV 4.4)
Byte 4 — Terminal Risk Management
b8 = 0x80Transaction exceeds floor limit
b7 = 0x40Lower consecutive offline limit exceeded
b6 = 0x20Upper consecutive offline limit exceeded
b5 = 0x10Transaction selected randomly for online processing
b4 = 0x08Merchant forced transaction online
b3 = 0x04Biometric Try Limit exceeded (EMV 4.4)
b2 = 0x02A selected biometric type not supported (EMV 4.4)
b1 = 0x01XDA signature verification failed (EMV 4.4)
Byte 5 — Issuer / Script Processing
b8 = 0x80Default TDOLTransaction Certificate Data Object ListA card-supplied list telling the terminal which data to include when building the Transaction Certificate hash.View in glossary → used
b7 = 0x40Issuer authentication failed
b6 = 0x20Script processing failed before final GENERATE ACApplication CryptogramA cryptogram the card generates to approve or decline a transaction: TC (approve offline), ARQC (go online), or AAC (decline).
b5 = 0x10Script processing failed after final GENERATE ACApplication CryptogramA cryptogram the card generates to approve or decline a transaction: TC (approve offline), ARQC (go online), or AAC (decline).
b4 = 0x08Reserved for use by the EMV contactless specifications
b3 = 0x04CA ECC key missing (EMV 4.4)
b2 = 0x02ECC key recovery failed (EMV 4.4)
b1 = 0x01Reserved for use by the EMV contactless specifications

Example values

0000008000Only "transaction exceeds floor limit" set
8000000000Offline data authentication not performed

Decode & build this tag

🖥️TVR Decoder🔓EMV TLV Decoder

Related tags

9F0DIssuer Action Code — Default9F0EIssuer Action Code — Denial9F0FIssuer Action Code — Online9BTransaction Status Information (TSI)
← Previous94 Application File Locator (AFL)Next →97 Transaction Certificate DOL (TDOL)