9F0A

Application Selection Registered Proprietary Data (ASRPD)

Application Selection Registered Proprietary Data is a mechanism for a card to signal, during application selection itself, support for proprietary features that go beyond what the standard selection tags, the AID in 4F and the label in 50, both covered earlier, communicate - a registered extension point specifically scoped to the selection phase of the transaction, before GPO or any acquisition tag exists yet. Because it's registered, meaning its use follows an EMVCo-administered registration process rather than being an arbitrary free-for-all, a terminal encountering 9F0A knows at least that the proprietary content follows some registered convention, even without necessarily knowing what that specific convention says - which is a meaningfully different situation from an entirely unregistered, issuer-arbitrary field like Application Discretionary Data (9F05, covered earlier). A terminal that doesn't recognise the specific registration a given 9F0A value refers to should simply ignore it rather than error out, since its entire design intent is additive, signalling extra capability without breaking terminals that don't understand it. 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.

Binary (2): AA01

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

Decoded example

Example value: AA01

Related tags

Properties

Tag9F0A
NameApplication Selection Registered Proprietary Data (ASRPD)
FormatBinary
Lengthvariable
SourceCard (ICC)
Templates
BooksEMV 4.4 Book 3

Frequently asked questions

What is EMV tag 9F0A?
Application Selection Registered Proprietary Data is a mechanism for a card to signal, during application selection itself, support for proprietary features that go beyond what the standard selection tags, the AID in 4F and the label in 50, both covered earlier, communicate - a registered extension point specifically scoped to the selection phase of the transaction, before GPO or any acquisition tag exists yet. Because it's registered, meaning its use follows an EMVCo-administered registration process rather than being an arbitrary free-for-all, a terminal encountering 9F0A knows at least that the proprietary content follows some registered convention, even without necessarily knowing what that specific convention says - which is a meaningfully different situation from an entirely unregistered, issuer-arbitrary field like Application Discretionary Data (9F05, covered earlier). A terminal that doesn't recognise the specific registration a given 9F0A value refers to should simply ignore it rather than error out, since its entire design intent is additive, signalling extra capability without breaking terminals that don't understand it. See EMV 4.4 Book 3.
What format and length does EMV tag 9F0A use?
Tag 9F0A uses the Binary format and is normally variable long.
Is tag 9F0A provided by the card or the terminal?
Tag 9F0A (Application Selection Registered Proprietary Data (ASRPD)) is provided by the Card (ICC).

Sources

  • EMV_v4.4_Book_3_Application_Specification, p. 139

Receive site updates

Subscribe to receive site updates directly to your email

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