9F16
Merchant IdentifierMerchant Identifier is the fixed 15-character string that names, to the acquirer, which merchant this specific transaction belongs to - a business-layer identifier that sits well above anything card- or cryptogram-related, closer in spirit to the Terminal Identification (9F1C) it's related to than to any of the card's own data elements. Where 9F1C answers which terminal in the acquirer's records, 9F16 answers which merchant in the acquirer's records - a single merchant can operate many terminals sharing one 9F16, while each of those terminals still carries its own distinct 9F1C. This field is what lets an acquirer route settlement, apply merchant-specific fee schedules, and attribute chargebacks correctly, none of which depends on anything the card itself contributed to the transaction. A terminal misconfigured with the wrong 9F16 - a common error after a merchant relocation, a POS fleet reassignment, or a franchise-to-franchise terminal transfer - will process transactions that are otherwise perfectly valid but settle, and get disputed, against the wrong merchant entirely. 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): MERCHANT0000001
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 4D45524348414E5430303030303031
Properties
| Tag | 9F16 |
|---|---|
| Name | Merchant Identifier |
| Format | Alphanumeric (special) |
| Length | 15 bytes |
| Source | Terminal |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F16?
- Merchant Identifier is the fixed 15-character string that names, to the acquirer, which merchant this specific transaction belongs to - a business-layer identifier that sits well above anything card- or cryptogram-related, closer in spirit to the Terminal Identification (9F1C) it's related to than to any of the card's own data elements. Where 9F1C answers which terminal in the acquirer's records, 9F16 answers which merchant in the acquirer's records - a single merchant can operate many terminals sharing one 9F16, while each of those terminals still carries its own distinct 9F1C. This field is what lets an acquirer route settlement, apply merchant-specific fee schedules, and attribute chargebacks correctly, none of which depends on anything the card itself contributed to the transaction. A terminal misconfigured with the wrong 9F16 - a common error after a merchant relocation, a POS fleet reassignment, or a franchise-to-franchise terminal transfer - will process transactions that are otherwise perfectly valid but settle, and get disputed, against the wrong merchant entirely. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F16 use?
- Tag 9F16 uses the Alphanumeric (special) format and is normally 15 bytes long.
- Is tag 9F16 provided by the card or the terminal?
- Tag 9F16 (Merchant Identifier) 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.