71
Issuer Script Template 1Issuer Script Template 1 is the delivery vehicle for post-issuance commands the issuer wants the card to execute before the transaction's second GENERATE AC - the mechanism that lets an issuer reach into a card that's already out in the field and change something (unblock a PIN, update a risk parameter, block the card entirely) using the current online transaction as the carrier, since there's no other channel to talk to an offline chip card directly. It's related to its sibling, Issuer Script Template 2 (72), which carries the same kind of content but timed for after the second GENERATE AC instead of before, and to the Issuer Script Command (86) that actually names what to do - 71 itself is just the timing wrapper, not the instruction. Because script processing happens inside the transaction itself, a script that fails partway through is exactly the condition the related Issuer Action Codes (9F0D/9F0E/9F0F) can flag via their own script-failure bits, tying an entire post-issuance-messaging subsystem back into the same risk-management framework the rest of the transaction already uses. 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
010203
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 8603010203
Nested TLV objects
- 86primitive · 3 bytes
010203
Properties
| Tag | 71 |
|---|---|
| Name | Issuer Script Template 1 |
| Format | Binary |
| Length | variable |
| Source | Issuer |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 71?
- Issuer Script Template 1 is the delivery vehicle for post-issuance commands the issuer wants the card to execute before the transaction's second GENERATE AC - the mechanism that lets an issuer reach into a card that's already out in the field and change something (unblock a PIN, update a risk parameter, block the card entirely) using the current online transaction as the carrier, since there's no other channel to talk to an offline chip card directly. It's related to its sibling, Issuer Script Template 2 (72), which carries the same kind of content but timed for after the second GENERATE AC instead of before, and to the Issuer Script Command (86) that actually names what to do - 71 itself is just the timing wrapper, not the instruction. Because script processing happens inside the transaction itself, a script that fails partway through is exactly the condition the related Issuer Action Codes (9F0D/9F0E/9F0F) can flag via their own script-failure bits, tying an entire post-issuance-messaging subsystem back into the same risk-management framework the rest of the transaction already uses. See EMV 4.4 Book 3.
- What format and length does EMV tag 71 use?
- Tag 71 uses the Binary format and is normally variable long.
- Is tag 71 provided by the card or the terminal?
- Tag 71 (Issuer Script Template 1) 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.