72
Issuer Script Template 2Issuer Script Template 2 is the mirror image of Issuer Script Template 1 (71) in every way except timing: it carries the identical kind of post-issuance command content, but scheduled to run after the second GENERATE AC rather than before it - a distinction that matters because some issuer actions are only safe or meaningful once the transaction's outcome is already finalized (adjusting an offline counter based on a transaction that's now confirmed to have gone through, for instance), while others need to happen before the card commits to its final decision. Related to 71 and to the same Issuer Script Command (86) structure both templates wrap, the choice between the two is entirely the issuer host's to make when building the script, not something the terminal decides - the terminal's job is simply to deliver whichever template the host sends, in the timing slot that template specifies, without needing to understand what the script actually does. A terminal that runs a Template 2 script before the second GENERATE AC, or vice versa, has broken the one guarantee the two-template design exists to provide. 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.
Nested TLV objects
- 86primitive · 3 bytes
040506
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 8603040506
Nested TLV objects
- 86primitive · 3 bytes
040506
Properties
| Tag | 72 |
|---|---|
| Name | Issuer Script Template 2 |
| Format | Binary |
| Length | variable |
| Source | Issuer |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 72?
- Issuer Script Template 2 is the mirror image of Issuer Script Template 1 (71) in every way except timing: it carries the identical kind of post-issuance command content, but scheduled to run after the second GENERATE AC rather than before it - a distinction that matters because some issuer actions are only safe or meaningful once the transaction's outcome is already finalized (adjusting an offline counter based on a transaction that's now confirmed to have gone through, for instance), while others need to happen before the card commits to its final decision. Related to 71 and to the same Issuer Script Command (86) structure both templates wrap, the choice between the two is entirely the issuer host's to make when building the script, not something the terminal decides - the terminal's job is simply to deliver whichever template the host sends, in the timing slot that template specifies, without needing to understand what the script actually does. A terminal that runs a Template 2 script before the second GENERATE AC, or vice versa, has broken the one guarantee the two-template design exists to provide. See EMV 4.4 Book 3.
- What format and length does EMV tag 72 use?
- Tag 72 uses the Binary format and is normally variable long.
- Is tag 72 provided by the card or the terminal?
- Tag 72 (Issuer Script Template 2) is provided by the Issuer.
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 150
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.