9F4E
Merchant Name and LocationMerchant Name and Location is the human-readable string a terminal supplies naming the merchant and its address - content meant for receipts, dispute documentation, and cardholder-facing statements rather than for anything the transaction's own authorization or cryptogram logic reads. It's related to the Merchant Identifier (9F16, covered earlier), which is the machine-readable, structured counterpart to this free-text field: 9F16 is what systems match against programmatically, while 9F4E is what a human actually reads on a statement or receipt when trying to recognise a charge. Because the two carry the same underlying fact in genuinely different formats, a discrepancy between them - a 9F16 that resolves correctly in an acquirer's records but a 9F4E that displays a garbled or outdated merchant name - is a data-quality issue worth catching independently of whether the transaction itself processed correctly, since it's exactly the kind of mismatch that generates cardholder confusion and unnecessary dispute filings. See EMV 4.4 Book 3.
Interactive decoder
Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.
Text (ASCII): GSSTK TEST STORE
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 475353544B20544553542053544F5245
Related tags
Properties
| Tag | 9F4E |
|---|---|
| Name | Merchant Name and Location |
| Format | Alphanumeric (special) |
| Length | variable |
| Source | Terminal |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F4E?
- Merchant Name and Location is the human-readable string a terminal supplies naming the merchant and its address - content meant for receipts, dispute documentation, and cardholder-facing statements rather than for anything the transaction's own authorization or cryptogram logic reads. It's related to the Merchant Identifier (9F16, covered earlier), which is the machine-readable, structured counterpart to this free-text field: 9F16 is what systems match against programmatically, while 9F4E is what a human actually reads on a statement or receipt when trying to recognise a charge. Because the two carry the same underlying fact in genuinely different formats, a discrepancy between them - a 9F16 that resolves correctly in an acquirer's records but a 9F4E that displays a garbled or outdated merchant name - is a data-quality issue worth catching independently of whether the transaction itself processed correctly, since it's exactly the kind of mismatch that generates cardholder confusion and unnecessary dispute filings. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F4E use?
- Tag 9F4E uses the Alphanumeric (special) format and is normally variable long.
- Is tag 9F4E provided by the card or the terminal?
- Tag 9F4E (Merchant Name and Location) is provided by the Terminal.
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 152
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.