What format and length does EMV tag 9F5C use?

Tag 9F5C uses the Binary format and is normally 8 bytes long.

Is tag 9F5C provided by the card or the terminal?

Tag 9F5C (Data Storage (DS) Requested Operator ID) is provided by the Terminal.

9F5C

Data Storage (DS) Requested Operator ID

Data Storage Requested Operator ID is an 8-byte, terminal-set identifier that names which data-storage operator - the scheme, program, or issuer service actually running the Kernel 2 data-storage feature - the terminal is requesting to interact with, sent to the card in GET PROCESSING OPTIONS. It's related to the Data Storage Data Object List (9F5B, covered alongside it here), which is what the card returns to specify what data it actually wants in exchange once it recognises the operator ID as one it supports. Because a single card can, in principle, participate in more than one data-storage program, 9F5C is what disambiguates which specific program this particular transaction's data exchange applies to - a terminal that supplies the wrong operator ID gets no meaningful data-storage exchange at all, not an error, since the card simply won't recognise the request as belonging to any program it runs. 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.

Binary (8): 0001020304050607

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

Decoded example

Example value: 0001020304050607

Related tags

9F5B

Properties

Tag	9F5C
Name	Data Storage (DS) Requested Operator ID
Format	Binary
Length	8 bytes
Source	Terminal
Templates	—
Books	EMV Contactless Book C-2

Frequently asked questions

What is EMV tag 9F5C?: Data Storage Requested Operator ID is an 8-byte, terminal-set identifier that names which data-storage operator - the scheme, program, or issuer service actually running the Kernel 2 data-storage feature - the terminal is requesting to interact with, sent to the card in GET PROCESSING OPTIONS. It's related to the Data Storage Data Object List (9F5B, covered alongside it here), which is what the card returns to specify what data it actually wants in exchange once it recognises the operator ID as one it supports. Because a single card can, in principle, participate in more than one data-storage program, 9F5C is what disambiguates which specific program this particular transaction's data exchange applies to - a terminal that supplies the wrong operator ID gets no meaningful data-storage exchange at all, not an error, since the card simply won't recognise the request as belonging to any program it runs. See EMV Contactless Book C-2.
What format and length does EMV tag 9F5C use?: Tag 9F5C uses the Binary format and is normally 8 bytes long.
Is tag 9F5C provided by the card or the terminal?: Tag 9F5C (Data Storage (DS) Requested Operator ID) is provided by the Terminal.

Sources

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

AID Parameter Table parser Public Key Table parser

All EMV tags

Receive site updates

Subscribe to receive site updates directly to your email

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