61
Application TemplateApplication Template is the constructed record inside the PPSE (or a legacy directory) that bundles everything a terminal needs to know about one selectable application before actually selecting it: the AID it should send in SELECT (4F), the human-readable label to show the cardholder (50), and the priority ranking against other candidates (87), all three already covered individually elsewhere in this dictionary. Tag 61 is what groups them as a single unit per application, inside template 70's outer record structure, so a multi-application card's directory is really a sequence of these templates, one per application, rather than a flat list of loose tags a terminal would otherwise have to reassemble itself. A terminal that mis-parses the boundary between one Application Template and the next will scramble which label or priority belongs to which AID - a card with two applications can end up showing the wrong name attached to the wrong AID in the candidate list, a selection-stage bug that's easy to misdiagnose as a data problem on the card rather than a parsing problem in the terminal's directory-reading code. 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.
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Properties
| Tag | 61 |
|---|---|
| Name | Application Template |
| Format | Binary |
| Length | variable |
| Source | Card (ICC) |
| Templates | 70 |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 61?
- Application Template is the constructed record inside the PPSE (or a legacy directory) that bundles everything a terminal needs to know about one selectable application before actually selecting it: the AID it should send in SELECT (4F), the human-readable label to show the cardholder (50), and the priority ranking against other candidates (87), all three already covered individually elsewhere in this dictionary. Tag 61 is what groups them as a single unit per application, inside template 70's outer record structure, so a multi-application card's directory is really a sequence of these templates, one per application, rather than a flat list of loose tags a terminal would otherwise have to reassemble itself. A terminal that mis-parses the boundary between one Application Template and the next will scramble which label or priority belongs to which AID - a card with two applications can end up showing the wrong name attached to the wrong AID in the candidate list, a selection-stage bug that's easy to misdiagnose as a data problem on the card rather than a parsing problem in the terminal's directory-reading code. See EMV 4.4 Book 3.
- What format and length does EMV tag 61 use?
- Tag 61 uses the Binary format and is normally variable long.
- Is tag 61 provided by the card or the terminal?
- Tag 61 (Application Template) 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.