FF81
Data RecordData Record is the constructed template Kernel 2 emits at the very end of its own processing, gathering the transaction data the kernel decided the reader needs to carry forward - the functional counterpart, within Kernel 2's own proprietary tag range (the FF-prefixed private-use space), to what template 77 does for the standard GENERATE AC response in contact and other contactless kernels. Because it's a Kernel 2-specific packaging of data rather than a new data element in its own right, debugging an FF81 problem is really debugging whatever specific field inside it looks wrong, in exactly the way a problem in template 70 is really a problem with one of the fields 70 happens to contain rather than with the template wrapper itself. Scoped to Mastercard PayPass (Kernel 2), a terminal or acquirer host expecting a different kernel's output format won't recognise FF81 at all, which is a kernel-mismatch configuration problem rather than a malformed-data one if it ever shows up unexpectedly in a log. 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 (5): 9F3602004A
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 9F3602004A
Related tags
Properties
| Tag | FF81 |
|---|---|
| Name | Data Record |
| Format | Binary |
| Length | variable |
| Source | Card (ICC) |
| Templates | — |
| Books | EMV Contactless Book C-2 |
Frequently asked questions
- What is EMV tag FF81?
- Data Record is the constructed template Kernel 2 emits at the very end of its own processing, gathering the transaction data the kernel decided the reader needs to carry forward - the functional counterpart, within Kernel 2's own proprietary tag range (the FF-prefixed private-use space), to what template 77 does for the standard GENERATE AC response in contact and other contactless kernels. Because it's a Kernel 2-specific packaging of data rather than a new data element in its own right, debugging an FF81 problem is really debugging whatever specific field inside it looks wrong, in exactly the way a problem in template 70 is really a problem with one of the fields 70 happens to contain rather than with the template wrapper itself. Scoped to Mastercard PayPass (Kernel 2), a terminal or acquirer host expecting a different kernel's output format won't recognise FF81 at all, which is a kernel-mismatch configuration problem rather than a malformed-data one if it ever shows up unexpectedly in a log. See EMV Contactless Book C-2.
- What format and length does EMV tag FF81 use?
- Tag FF81 uses the Binary format and is normally variable long.
- Is tag FF81 provided by the card or the terminal?
- Tag FF81 (Data Record) is provided by the Card (ICC).
Sources
- C-2-Kernel-2-V2.11-Final-June-2023, p. 371
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.