9F0B
Cardholder Name ExtendedCardholder Name Extended exists for exactly the cardholders whose full name doesn't fit in the standard Cardholder Name field (5F20, covered earlier, capped at 26 characters): a longer variant, 27 to 45 characters, that a terminal should prefer displaying when present, since its whole reason for existing is that 5F20 alone would have truncated the name. Related to 5F20, the two fields are meant to be complementary rather than contradictory - a card populating 9F0B is expected to also populate 5F20 with a compatible, likely truncated, version for terminals that don't know to look for the extended field, so a terminal implementing only 5F20 support still gets a usable, if shorter, name rather than nothing. The same non-cryptographic failure mode already described for Cardholder Name applies here too: a wrong or garbled 9F0B doesn't break the transaction technically, it just undermines the human-verification and receipt-quality purpose the field exists to serve. 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): TEST CARDHOLDER EXTENDED NAME
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 544553542043415244484F4C44455220455854454E444544204E414D45
Related tags
Properties
| Tag | 9F0B |
|---|---|
| Name | Cardholder Name Extended |
| Format | Alphanumeric (special) |
| Length | 27–45 bytes |
| Source | Card (ICC) |
| Templates | 70, 77 |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F0B?
- Cardholder Name Extended exists for exactly the cardholders whose full name doesn't fit in the standard Cardholder Name field (5F20, covered earlier, capped at 26 characters): a longer variant, 27 to 45 characters, that a terminal should prefer displaying when present, since its whole reason for existing is that 5F20 alone would have truncated the name. Related to 5F20, the two fields are meant to be complementary rather than contradictory - a card populating 9F0B is expected to also populate 5F20 with a compatible, likely truncated, version for terminals that don't know to look for the extended field, so a terminal implementing only 5F20 support still gets a usable, if shorter, name rather than nothing. The same non-cryptographic failure mode already described for Cardholder Name applies here too: a wrong or garbled 9F0B doesn't break the transaction technically, it just undermines the human-verification and receipt-quality purpose the field exists to serve. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F0B use?
- Tag 9F0B uses the Alphanumeric (special) format and is normally 27–45 bytes long.
- Is tag 9F0B provided by the card or the terminal?
- Tag 9F0B (Cardholder Name Extended) is provided by the Card (ICC).
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 143
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.