What tag 95 contains, its format and length, an example value and where it goes wrong in testing.
Tag 95 is the Terminal Verification Results. It is a 5-byte bit field in which the terminal records what went wrong, or what needed attention, during the transaction, such as failed offline data authentication, an expired card or a transaction above the floor limit.
Tag 95 is the Terminal Verification Results. It is a 5-byte bit field in which the terminal records what went wrong, or what needed attention, during the transaction, such as failed offline data authentication, an expired card or a transaction above the floor limit.
Each of the 40 bits is a flag. The terminal sets bits as it runs offline data authentication, processing restrictions, cardholder verification and terminal risk management. It then compares the result with the Terminal Action Codes and the card's Issuer Action Codes to decide whether to go online, approve offline or decline.
The TVR is also sent to the issuer in the online request, so it is one of the first things to check when a transaction behaves unexpectedly. Use the decoder below to read any TVR.
| Property | Value |
|---|---|
| Tag | 95 |
| Name | Terminal Verification Results |
| Abbreviation | TVR |
| Format | Binary |
| Length | 5 bytes |
| Source | Terminal |
95 8000000000
0x80 in the first byte means bit 8 is set: offline data authentication was not performed. All other bits are clear.
Enter the value in hex. The decoder runs in your browser and nothing is sent anywhere.
For worked examples, read Reading an EMV Log: What Tags 9F26, 9F27, 95 and 82 Tell You. Paste a full EMV data string into the TLV parser to see every tag decoded together, or search all tags in the EMV tag lookup. See the full tag list.
If your payment app has to pass EMV Level 3, see our certification services and Foundry.
We have taken 133 payment applications through EMV Level 3 across many regions. Tell us about your project.
Talk to us Book a meeting with a founder