What tag 57 contains, its format and length, an example value and where it goes wrong in testing.
Tag 57 is the Track 2 Equivalent Data. It holds the same information as the magnetic stripe Track 2 in a compressed form: the PAN, a separator, the expiry date, the service code and discretionary data.
Tag 57 is the Track 2 Equivalent Data. It holds the same information as the magnetic stripe Track 2 in a compressed form: the PAN, a separator, the expiry date, the service code and discretionary data.
It is sensitive authentication data. Payment standards do not allow it to be stored after authorization, even when encrypted, so logs and databases must never contain it.
In an online message, the terminal usually sends it in field 35, or inside the ICC data.
| Property | Value |
|---|---|
| Tag | 57 |
| Name | Track 2 Equivalent Data |
| Abbreviation | n/a |
| Format | Binary |
| Length | Up to 19 bytes |
| Source | Card (ICC) |
57 4111111111111111D2912201000000000000
PAN, then the D separator, then expiry 2912 (YYMM), service code 201 and discretionary data. This is a test value.
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