BF0C

File Control Information (FCI) Issuer Discretionary Data

FCI Issuer Discretionary Data is a constructed template nested inside the FCI Proprietary Template (A5, covered earlier) that bundles whatever issuer-defined data objects the issuer chose to expose during selection - commonly the Log Entry (9F4D, covered earlier) pointing to the card's onboard transaction log, and the Application Capabilities Information (9F5D, not covered in this batch but referenced by name) describing what the application can do. Unlike A5 itself, which has a broadly standardised set of expected contents across issuers (the PDOL, labels, language preference), BF0C's actual contents are genuinely issuer-discretionary, in the same spirit as Application Discretionary Data (9F05, covered earlier) but scoped specifically to what's exposed at selection time rather than general application data. A terminal parsing SELECT responses across multiple issuers needs to treat BF0C's contents as variable by design, extracting only the specific sub-tags it actually knows how to use, like 9F4D, if it implements log-reading, rather than assuming a fixed structure. See EMV Contactless Book C-8.

Interactive decoder

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

Nested TLV objects

  • 9F4Dprimitive · 2 bytes

    0203

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

Decoded example

Example value: 9F4D020203

Nested TLV objects

  • 9F4Dprimitive · 2 bytes

    0203

Related tags

Properties

TagBF0C
NameFile Control Information (FCI) Issuer Discretionary Data
FormatBinary
Lengthvariable
SourceCard (ICC)
Templates
BooksEMV Contactless Book C-8

Frequently asked questions

What is EMV tag BF0C?
FCI Issuer Discretionary Data is a constructed template nested inside the FCI Proprietary Template (A5, covered earlier) that bundles whatever issuer-defined data objects the issuer chose to expose during selection - commonly the Log Entry (9F4D, covered earlier) pointing to the card's onboard transaction log, and the Application Capabilities Information (9F5D, not covered in this batch but referenced by name) describing what the application can do. Unlike A5 itself, which has a broadly standardised set of expected contents across issuers (the PDOL, labels, language preference), BF0C's actual contents are genuinely issuer-discretionary, in the same spirit as Application Discretionary Data (9F05, covered earlier) but scoped specifically to what's exposed at selection time rather than general application data. A terminal parsing SELECT responses across multiple issuers needs to treat BF0C's contents as variable by design, extracting only the specific sub-tags it actually knows how to use, like 9F4D, if it implements log-reading, rather than assuming a fixed structure. See EMV Contactless Book C-8.
What format and length does EMV tag BF0C use?
Tag BF0C uses the Binary format and is normally variable long.
Is tag BF0C provided by the card or the terminal?
Tag BF0C (File Control Information (FCI) Issuer Discretionary Data) is provided by the Card (ICC).

Sources

  • C-8_Kernel_8_v1.1, p. 257

Receive site updates

Subscribe to receive site updates directly to your email

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