9F18
Issuer Script IdentifierIssuer Script Identifier is a 4-byte value the issuer attaches to a specific Issuer Script Template (71 or 72, both covered earlier) so that when the terminal reports back on the transaction, the issuer's own systems can match that report against the specific script they sent - a correlation ID for post-issuance messaging, essentially, in a subsystem that otherwise has no built-in way to answer which of my many scripts did this particular result belong to. Without it, an issuer processing large volumes of post-issuance scripts across many cards and transactions would have no reliable way to reconcile script-execution outcomes back to the specific script instance that produced them, especially when a single card receives multiple scripts across its lifetime. A terminal's role with 9F18 is purely custodial - receive it alongside the script, and if the transaction protocol calls for reporting script results, include it unchanged in that report, since the identifier's meaning is entirely internal to the issuer's own script-management system. 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 (4): 0000A1B2
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 0000A1B2
Properties
| Tag | 9F18 |
|---|---|
| Name | Issuer Script Identifier |
| Format | Binary |
| Length | 4 bytes |
| Source | Issuer |
| Templates | 71, 72 |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F18?
- Issuer Script Identifier is a 4-byte value the issuer attaches to a specific Issuer Script Template (71 or 72, both covered earlier) so that when the terminal reports back on the transaction, the issuer's own systems can match that report against the specific script they sent - a correlation ID for post-issuance messaging, essentially, in a subsystem that otherwise has no built-in way to answer which of my many scripts did this particular result belong to. Without it, an issuer processing large volumes of post-issuance scripts across many cards and transactions would have no reliable way to reconcile script-execution outcomes back to the specific script instance that produced them, especially when a single card receives multiple scripts across its lifetime. A terminal's role with 9F18 is purely custodial - receive it alongside the script, and if the transaction protocol calls for reporting script results, include it unchanged in that report, since the identifier's meaning is entirely internal to the issuer's own script-management system. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F18 use?
- Tag 9F18 uses the Binary format and is normally 4 bytes long.
- Is tag 9F18 provided by the card or the terminal?
- Tag 9F18 (Issuer Script Identifier) 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.