83
Command TemplateCommand Template is the wrapper around the data the terminal sends in GET PROCESSING OPTIONS - the terminal-side counterpart to the card's own PDOL (9F38, referenced alongside it) that told the terminal what to include in the first place. Where 9F38 is the card's request list, 83 is the terminal's actual delivery: the concatenated values, in the exact order the PDOL specified, wrapped in this single constructed tag rather than sent as loose individual fields. Because GPO is a fixed-format command with no room for the terminal to explain what it sent or why, any mismatch between what the PDOL asked for and what 83 actually contains - a wrong length, a missing entry, values out of order - produces a card response that can range from an outright error to a transaction that proceeds on subtly wrong assumptions, since the card has no way to independently verify that 83's contents genuinely correspond one-to-one with its own PDOL beyond checking the overall length. 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): 0076
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0076
Related tags
Properties
| Tag | 83 |
|---|---|
| Name | Command Template |
| Format | Binary |
| Length | variable |
| Source | Terminal |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 83?
- Command Template is the wrapper around the data the terminal sends in GET PROCESSING OPTIONS - the terminal-side counterpart to the card's own PDOL (9F38, referenced alongside it) that told the terminal what to include in the first place. Where 9F38 is the card's request list, 83 is the terminal's actual delivery: the concatenated values, in the exact order the PDOL specified, wrapped in this single constructed tag rather than sent as loose individual fields. Because GPO is a fixed-format command with no room for the terminal to explain what it sent or why, any mismatch between what the PDOL asked for and what 83 actually contains - a wrong length, a missing entry, values out of order - produces a card response that can range from an outright error to a transaction that proceeds on subtly wrong assumptions, since the card has no way to independently verify that 83's contents genuinely correspond one-to-one with its own PDOL beyond checking the overall length. See EMV 4.4 Book 3.
- What format and length does EMV tag 83 use?
- Tag 83 uses the Binary format and is normally variable long.
- Is tag 83 provided by the card or the terminal?
- Tag 83 (Command Template) is provided by the Terminal.
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 144
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.