9F5B
Data Storage Data Object List (DSDOL)Data Storage Data Object List is the card's own tag-and-length request list, in the same request-list family as the PDOL and CDOLs already covered throughout this dictionary, specifically for what data the kernel must pass in GENERATE AC to support Kernel 2's data-storage feature - it only appears once the card has recognised the Data Storage Requested Operator ID (9F5C, covered alongside it here) as one it participates in. Related to CDOL1 (8C, covered earlier) as a parallel mechanism operating alongside it in the same GENERATE AC step, 9F5B extends what the terminal supplies specifically for the data-storage exchange, layered on top of the ordinary cryptogram-request data CDOL1 already defines. A terminal implementation that handles CDOL1 correctly but doesn't also honour 9F5B when present will complete a technically valid cryptogram exchange while silently failing to participate in whatever data-storage program the card was expecting, which surfaces as a missing feature rather than a transaction error. 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 (6): 9F02069F1A02
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 9F02069F1A02
Properties
| Tag | 9F5B |
|---|---|
| Name | Data Storage Data Object List (DSDOL) |
| Format | Binary |
| Length | variable |
| Source | Card (ICC) |
| Templates | 70 |
| Books | EMV Contactless Book C-2 |
Frequently asked questions
- What is EMV tag 9F5B?
- Data Storage Data Object List is the card's own tag-and-length request list, in the same request-list family as the PDOL and CDOLs already covered throughout this dictionary, specifically for what data the kernel must pass in GENERATE AC to support Kernel 2's data-storage feature - it only appears once the card has recognised the Data Storage Requested Operator ID (9F5C, covered alongside it here) as one it participates in. Related to CDOL1 (8C, covered earlier) as a parallel mechanism operating alongside it in the same GENERATE AC step, 9F5B extends what the terminal supplies specifically for the data-storage exchange, layered on top of the ordinary cryptogram-request data CDOL1 already defines. A terminal implementation that handles CDOL1 correctly but doesn't also honour 9F5B when present will complete a technically valid cryptogram exchange while silently failing to participate in whatever data-storage program the card was expecting, which surfaces as a missing feature rather than a transaction error. See EMV Contactless Book C-2.
- What format and length does EMV tag 9F5B use?
- Tag 9F5B uses the Binary format and is normally variable long.
- Is tag 9F5B provided by the card or the terminal?
- Tag 9F5B (Data Storage Data Object List (DSDOL)) is provided by the Card (ICC).
Sources
- C-2-Kernel-2-V2.11-Final-June-2023, p. 375
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.