9F24

Payment Account Reference (PAR)

Payment Account Reference is a deliberately non-financial identifier that links every token generated for one underlying account - a mobile wallet token, an e-commerce token, the original physical card - back to each other, without itself being usable to initiate a payment and without exposing the PAN (5A, referenced alongside it) those tokens actually protect. It exists because tokenization solved one problem, never exposing the real PAN across multiple digital channels, while creating another: a merchant or issuer that needs to recognise this is the same underlying account as that other transaction for loyalty, fraud analysis, or dispute purposes previously had no safe way to do that once the PAN itself was hidden behind different tokens in different channels - 9F24 is exactly that safe cross-reference. Related to the Token Requestor ID (9F19) that identifies which entity requested a given token in the first place, PAR is specifically designed so that even a system holding it cannot reverse it back into a PAN, which is the property that makes it usable in contexts (analytics, loyalty programs, some dispute workflows) where the actual PAN would be too sensitive to circulate. 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.

Text (ASCII): TESTPAR0000000000000000000000

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

Decoded example

Example value: 5445535450415230303030303030303030303030303030303030303030

Related tags

Properties

Tag9F24
NamePayment Account Reference (PAR)
FormatAlphanumeric
Length29 bytes
SourceCard (ICC)
Templates70, 77
BooksEMV 4.4 Book 3

Frequently asked questions

What is EMV tag 9F24?
Payment Account Reference is a deliberately non-financial identifier that links every token generated for one underlying account - a mobile wallet token, an e-commerce token, the original physical card - back to each other, without itself being usable to initiate a payment and without exposing the PAN (5A, referenced alongside it) those tokens actually protect. It exists because tokenization solved one problem, never exposing the real PAN across multiple digital channels, while creating another: a merchant or issuer that needs to recognise this is the same underlying account as that other transaction for loyalty, fraud analysis, or dispute purposes previously had no safe way to do that once the PAN itself was hidden behind different tokens in different channels - 9F24 is exactly that safe cross-reference. Related to the Token Requestor ID (9F19) that identifies which entity requested a given token in the first place, PAR is specifically designed so that even a system holding it cannot reverse it back into a PAN, which is the property that makes it usable in contexts (analytics, loyalty programs, some dispute workflows) where the actual PAN would be too sensitive to circulate. See EMV 4.4 Book 3.
What format and length does EMV tag 9F24 use?
Tag 9F24 uses the Alphanumeric format and is normally 29 bytes long.
Is tag 9F24 provided by the card or the terminal?
Tag 9F24 (Payment Account Reference (PAR)) is provided by the Card (ICC).

Sources

  • EMV_v4.4_Book_3_Application_Specification, p. 153

Receive site updates

Subscribe to receive site updates directly to your email

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