9F01

Acquirer Identifier

Acquirer Identifier names the acquirer within the broader payment system - a business-layer identifier structurally similar to the Merchant Identifier (9F16, covered earlier) but one level up the hierarchy: 9F16 says which merchant, 9F01 says which acquirer that merchant's transactions ultimately route through. It matters for the same category of downstream, non-cryptographic reasons the other business-context tags in this dictionary matter: settlement routing, scheme-level reporting, and acquirer-specific risk or fee logic all key on this field, none of which the card's own transaction logic reads or depends on. A terminal misconfigured with the wrong 9F01 - most plausibly after an acquirer relationship changes or a terminal is migrated between processors - produces transactions that are otherwise completely valid but that route to, and get reported against, the wrong acquiring relationship entirely, a business-layer error invisible from anything the EMV protocol itself checks. See EMV Contactless Book C-2.

Interactive decoder

Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.

Note: this tag is normally 6 bytes; you entered 3.

Numeric (BCD): 000456

This tag is not a bitmap; the decoder shows a format-based interpretation.

Decoded example

Example value: 000456

Related tags

Properties

Tag9F01
NameAcquirer Identifier
FormatNumeric (BCD)
Length6 bytes
SourceCard (ICC)
Templates
BooksEMV Contactless Book C-2

Frequently asked questions

What is EMV tag 9F01?
Acquirer Identifier names the acquirer within the broader payment system - a business-layer identifier structurally similar to the Merchant Identifier (9F16, covered earlier) but one level up the hierarchy: 9F16 says which merchant, 9F01 says which acquirer that merchant's transactions ultimately route through. It matters for the same category of downstream, non-cryptographic reasons the other business-context tags in this dictionary matter: settlement routing, scheme-level reporting, and acquirer-specific risk or fee logic all key on this field, none of which the card's own transaction logic reads or depends on. A terminal misconfigured with the wrong 9F01 - most plausibly after an acquirer relationship changes or a terminal is migrated between processors - produces transactions that are otherwise completely valid but that route to, and get reported against, the wrong acquiring relationship entirely, a business-layer error invisible from anything the EMV protocol itself checks. See EMV Contactless Book C-2.
What format and length does EMV tag 9F01 use?
Tag 9F01 uses the Numeric (BCD) format and is normally 6 bytes long.
Is tag 9F01 provided by the card or the terminal?
Tag 9F01 (Acquirer Identifier) is provided by the Card (ICC).

Sources

  • C-2-Kernel-2-V2.11-Final-June-2023, p. 355

Receive site updates

Subscribe to receive site updates directly to your email

We won't send spam. You can unsubscribe at any time.