> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/7-30-26-draft-version-scra-dynafamily-programmers-manual/7-30-26-draft-version-notifications/7-30-26-draft-version-0x0101-transaction-information-update.md). # (7/30/26 Draft version) 0x0101 - Transaction Information Update This notification reports information about progress and state changes that occur during a transaction. For this notification, Notification Detail described in Notification Message contains one byte each, to indicate: * The Payment Technology (PT) involved * The Reason (Rsn) for the notification * Detail (Det) about the notification that has different meanings depending on the Reason * An Extra field (Ext) that has different meanings depending on the Reason ### Notification Detail Codes - Manual Card Entry {% hint style="info" %} Payment Technology 0x07 Manual Card Entry (MCE) contains transaction notification detail codes involving manual card entry (MCE Only). Reasons: * 0x01 = Card Event; * 0x08 = Data Update; * 0x10 = State Update. {% endhint %}

PT	Rsn	Det	Ext	Meaning
0x07	0x01	0x01	0x00	Manual Card Entry, Card Event, Data Entered, Reserved (MCE Only)
0x07	0x08	0x02	0x02	Manual Card Entry, Data Update, ARQC Update (Quick Chip), Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (MCE Only).
0x07	0x08	0x03	0x02	Manual Card Entry, Data Update, Batch Data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (MCE Only).

### Notification Detail Codes - Magnetic Stripe Reader {% hint style="info" %} Payment Technology 0x08 Magnetic Stripe Reader (MSR) contains transaction notification detail codes involving magnetic stripe cards (MSR Only). Reasons: * 0x01 = Card Event; * 0x08 = Data Update; * 0x10 = State Update {% endhint %}

PT	Rsn	Det	Ext	Meaning
0x08	0x01	0x01	0x00	MSR, Card Event, Swiped, Reserved (MSR Only)
0x08	0x01	0x02	0x00	MSR, Card Event, Inserted, Reserved (MSR Only)
0x08	0x01	0x03	0x00	MSR, Card Event, Removed, Reserved (MSR Only)
0x08	0x01	0x04	0x00	MSR, Card Event, Detected, Reserved
0x08	0x08	0x02	0x02	MSR, Data Update, ARQC Update (Quick Chip), Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (MSR Only).
0x08	0x08	0x03	0x02	MSR, Data Update, Batch Data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (MSR Only).

### Notification Detail Codes - EMV Contact {% hint style="info" %} Payment Technology 0x10 EMV Contact contains transaction notification detail codes involving contact chip cards (EMV Contact Only). Reasons: * 0x01 = Card Event; * 0x02 = Online PIN Event; * 0x08 = Data Update; * 0x10 = State Update {% endhint %}

PT	Rsn	Det	Ext	Meaning
0x10	0x01	0x02	0x00	EMV Contact, Card Event, Inserted, Reserved (EMV Contact Only)
0x10	0x01	0x03	0x00	EMV Contact, Card Event, Removed, Reserved (EMV Contact Only)
0x10	0x01	0x04	0x00	EMV Contact, Card Event, Detected, Reserved (EMV Contact Only)
0x10	0x02	0x06	0x01	EMV Contact, Online PIN Event, PIN Entry, PIN Pad Error (EMV Contact Only)
0x10	0x02	0x06	0x02	EMV Contact, Online PIN Event, PIN Entry, PIN Block Encryption Error (EMV Contact Only)
0x10	0x08	0x02	0x02	EMV Contact, Data Update, ARQC Update (Quick Chip), Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contact Only).
0x10	0x08	0x03	0x02	EMV Contact, Data Update, Batch Data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contact Only).

### Notification Detail Codes - EMV Contactless {% hint style="info" %} Payment Technology 0x20 EMV Contactless contains transaction notification detail codes involving contactless cards and contactless payment devices. Reasons: * 0x01 = Card Event; * 0x02 = Online PIN Event; * 0x08 = Data Update; * 0x10 = State Update {% endhint %}

PT	Rsn	Det	Ext	Meaning
0x00	0x10	0x01	0x00	None, State Update, Transaction Started by Device, Legacy EMV Flow (Touch Only)
0x00	0x10	0x01	0x01	None, State Update, Transaction Started by Device, Quick Chip Flow (Touch Only)
0x00	0x10	0x02	0x00	None, State Update, Transaction Canceled, Reserved (Touch Only)
0x20	0x01	0x03	0x00	EMV Contactless, Card Event, Removed, Reserved (EMV Contactless Only)
0x20	0x01	0x04	0x00	EMV Contactless, Card Event, Detected, EMV (EMV Contactless Only)
0x20	0x01	0x04	0x01	EMV Contactless, Card Event, Detected, NFC/MIFARE Ultralight (EMV Contactless Only)
0x20	0x01	0x04	0x02	EMV Contactless, Card Event, Detected, MIFARE Classic 1K (EMV Contactless Only)
0x20	0x01	0x04	0x03	EMV Contactless, Card Event, Detected, MIFARE Classic 4K (EMV Contactless Only)
0x20	0x01	0x04	0x04	EMV Contactless, Card Event, Detected, MIFARE DESFire Light (EMV Contactless Only)
0x20	0x01	0x04	0x05	EMV Contactless, Card Event, Detected, MIFARE MINI® (EMV Contactless Only)
0x20	0x01	0x04	0x06	EMV Contactless, Card Event, Detected, MIFARE Plus EV1 (EMV Contactless Only)
0x20	0x01	0x04	0x07	EMV Contactless, Card Event, Detected, MIFARE Plus EV2 (EMV Contactless Only)
0x20	0x01	0x04	0x08	EMV Contactless, Card Event, Detected, MIFARE Plus SE (EMV Contactless Only)
0x20	0x01	0x04	0x09	EMV Contactless, Card Event, Detected, MIFARE Plus X (EMV Contactless Only)
0x20	0x01	0x04	0x0A	EMV Contactless, Card Event, Detected, MIFARE DESFire EV1 (EMV Contactless Only)
0x20	0x01	0x04	0x0B	EMV Contactless, Card Event, Detected, MIFARE DESFire EV2 (EMV Contactless Only)
0x20	0x01	0x04	0x0C	EMV Contactless, Card Event, Detected, MIFARE DESFire EV3 (EMV Contactless Only)
0x20	0x01	0x05	0x00	EMV Contactless, Card Event, Collision, Reserved (EMV Contactless Only)
0x20	0x01	0x10	0x02	EMV Contactless, Card Event, Apple VAS Error, Data Attached — device includes additional data defined in Table 317 – VAS Error Report in the Notification Payload portion of the Notification Message (Apple VAS Only).
0x20	0x01	0x20	0x02	EMV Contactless, Card Event, Google Smart Tap Error, Data Attached — device includes additional data defined in Table 317 – VAS Error Report in the Notification Payload portion of the Notification Message (Google Smart Tap Only).
0x20	0x02	0x06	0x01	EMV Contactless, Online PIN Event, PIN Entry, PIN Pad Error (EMV Contactless Only)
0x20	0x02	0x06	0x02	EMV Contactless, Online PIN Event, PIN Block Encryption Error (EMV Contactless Only)
0x20	0x08	0x02	0x02	EMV Contactless, Data Update, ARQC Update (Quick Chip), Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contactless Only).
0x20	0x08	0x03	0x02	EMV Contactless, Data Update, Batch Data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contactless Only).
0x20	0x08	0x04	0x02	EMV Contactless, Data Update, NFC UID data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contactless Only).
0x20	0x08	0x07	0x02	EMV Contactless, Data Update, GPO Response, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contactless Only).
0x20	0x08	0x08	0x02	EMV Contactless, Data Update, MIFARE Card Data, Data Attached — device includes additional data defined in Table 314 in the Notification Payload portion of the Notification Message (EMV Contactless Only).

### Notification Detail Codes - Barcode Reader {% hint style="info" %} Payment Technology 0x30 Barcode Reader contains transaction notification detail codes involving barcodes (BCR Only). Reason: 0x01 = Barcode Event. {% endhint %}

PT	Rsn	Det	Ext	Meaning
30	01	01	00	(BCR Only) Barcode Reader, Barcode Event, Read, Reserved
30	08	00	02	Barcode Reader, Barcode Update, Type, Data Attached Type 0x00 = Unknown Type 0x01 = MagTek Type 0x02 = EMV The barcode reader has successfully read a barcode. In this case, the device includes barcode data in the Notification Payload portion of the Notification Message. If the data is encrypted, the data is in the format described in Table 7.4‑5. Data that is not encrypted is in the format described in Table 7.4‑6 (BCR Only) Barcode Reader, Barcode Event, MagTek Blob Type, Data Attached In this case, the device includes additional data, defined in Table 7.1‑2, in the Notification Payload portion of the Notification Message

Rsn

Det

Ext

Meaning

(BCR Only) Barcode Reader, Barcode Event, Read, Reserved

Barcode Reader, Barcode Update, Type, Data Attached

Type 0x00 = Unknown
Type 0x01 = MagTek
Type 0x02 = EMV

The barcode reader has successfully read a barcode. In this case, the device includes barcode data in the Notification Payload portion of the Notification Message. If the data is encrypted, the data is in the format described in Table 7.4‑5. Data that is not encrypted is in the format described in Table 7.4‑6

(BCR Only)

Barcode Reader, Barcode Event, MagTek Blob Type, Data Attached

In this case, the device includes additional data, defined in Table 7.1‑2, in the Notification Payload portion of the Notification Message

### Notification Detail Codes - mDOC {% hint style="info" %} Payment Technology 0x40 Mobile Document (mDoc) contains transaction notification detail codes involving Mobile Document. · Reason 0x01 = Engagement Event · Reason 0x08 = Data Retrieval · Reason 0x09 = Subscription {% endhint %}


PT	Rsn	Det	Ext	Meaning
40	01	01	00	mDoc, Engagement Event, QR Code, Reserved
40	01	02	00	mDoc, Engagement Event, NFC, Reserved
40	08	01	02	mDoc, Data Retrieval, Type, Data Attached · Type 0x01 = SessionData · Type 0x02 = SessionData Failure
40	09	01	01	mDoc, Subscription, Expiration, Warning
40	09	01	02	mDoc, Subscription, Expiration, Expired

### mDOC Encrypted Notification - mDL/mPass


Tag	Len	Value / Description	Typ	Req	Default
2-byte MSB message length excluding padding and CBC-MAC
F9	var	Container for MAC structure and generic data	T	R
/DFDF54	var	MAC KSN	B	R
/DFDF55	01	MAC Encryption Type	B	R
/F8	var	Container for Encrypted Data	T	R
//DFDF59	var	Encrypted Data Primitive Decrypt the value of this TLV data object using the algorithm and variant specified in the Encrypted Data KSN parameter and the Encrypted Data Encryption Type parameter to read its contents.	B	R
//DFDF56	var	Encrypted Data KSN	B	R
//DFDF57	01	Encrypted Data Encryption Type	B	R
//DFDF58	01	Number of Padding Bytes Number of bytes added to DFDF59 value to force its length to a multiple of 16 bytes for AES.	B	R
Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 (for TDES) or 16 (for AES) bytes. It is a requirement of CMAC algorithm.
Four-byte CMAC. The host should calculate the CMAC and verify that it matches.

### mDL DFDF59 Decrypted Contents


Tag	Len	Value / Description	Typ	Req	Default
FF43	var	Decrypted/Raw Data Container Inside this container, the device inserts TLV data objects of response data of various nameSpaces defines in ISO-18013 and ISO-23220.	T	R
/DFB001 to /DFB04	var	Response data of nameSpace “org.iso.18013.5.1”.	B	O
/DFB041 to /DFB060	var	Response data of nameSpace “org.iso.18013.5.1.aamva”.	B	O
/DFB061 to /DFB07F	var	Response data of nameSpace “org.iso.23220.1”.	B	O
Padding to force DFDF59 plus padding to be a multiple of 8 (for TDES) or 16 (for AES) bytes for encryption.

#### Response. Command has started running: {% code overflow="wrap" %} ``` AA-00 81-04-82-05-12-01 // Response of Command 0x1201 82-04-01-00-00-00 // Started ``` {% endcode %} #### Notification 0x0101 (Engagement event with QR Code) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 // Notification 0x0101 82 04 40 01 01 00 // Event: Engagement with QR Code ``` {% endcode %} #### Notification 0x0101 (Engagement event with NFC) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 // Notification 0x0101 82 04 40 01 02 00 // Event: Engagement with NFC ``` {% endcode %} #### Notification 0x0101, Tagged Data attached, Security is enabled (for both QR Code and NFC modes) **Case #1: Both Encryption and MACing are using TDES key** {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 82 04 40 08 01 02 84 82 00 6A 01 01 // 0x006A, LN7=LN6 + 6 84 82 00 64 // 0x0064, LN6=LN5 + 2 + 5(Padding) + 4(CKSUM) 00 59 // 0x0059, LN5=LN4 + 4 F9 82 00 55 // 0x0055, LN4=LN3 + 25 (23 for TDES MAC) DF DF 54 0A FFFF987654321020001B // MAC KSN, 10 bytes for TDES DF DF 55 01 82 // MAC Algorithm Type F8 82 00 3E // 0x003E, LN3=LN2 + 6(Len) + 26(56+57+58)(24 for TDES ENC) = 62 DF DF 59 82 00 20 // 0x0020, LN2=LN1 + 4(Len) + 7(ENC Padding) 43B582C4ED23B5631A0E8F5FB06F1612 // LN1=0x20 – 4(Len) – 7(ENC Padding) = 21 761672430C5C363D2A98660827AA345E DF DF 56 0A FFFF987654321020001A // Encryption KSN, 10 bytes for TDES DF DF 57 01 80 // Encryption Algorithm Type DF DF 58 01 07 // Padding count for Encryption, 7 bytes 05 05 05 05 05 // PKCS7 padding bytes for MACing, 5 bytes 3B AE 3A 8B // MAC checksum, 4 bytes ``` {% endcode %} **Case #2: Both Encryption and MACing are using AES key** {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 82 04 40 08 01 02 84 82 00 6A 01 01 // 0x006A, LN7=LN6 + 6 84 82 00 64 // 0x0064, LN6=LN5 + 2 + 1(Padding) + 4(CKSUM) 00 5D // 0x005D, LN5=LN4 + 4 F9 82 00 59 // 0x0059, LN4=LN3 + 25 = 89 DF DF 54 0C 123456789012345600000002 // MAC KSN, 12 bytes for AES DF DF 55 01 9A // MAC Algorithm Type F8 82 00 40 // 0x0040, LN3=LN2 + 6(Len) + 26(56+57+58) = 64 DF DF 59 82 00 20 // 0x0020, LN2=LN1 + 4(Len) + 7(ENC Padding) C68F6CE9A4793966B82B06FA918A5CF2 // LN1=0x20 – 4(Len) – 7(ENC Padding) = 21 6289664054265992C4C5E021495186C0 DF DF 56 0C 123456789012345600000001 // Encryption KSN, 12 bytes for AES DF DF 57 01 9D // Encryption Algorithm Type DF DF 58 01 07 // Padding for encryption, 7 bytes 01 // Padding for MACing, 1 byte 6A 4A 24 AE // MAC checksum ``` {% endcode %} #### Decrypted Data: {% code overflow="wrap" %} ``` FF 43 82 00 17 // Data Conatiner, 23 bytes DF B0 01 82 00 04 // Tag 0xDFB001, “family_name”, 4 bytes 43 48 4F 55 DF B0 02 82 00 07 // Tag 0xDFB002, “given_name”, 7 bytes 57 45 49 2D 54 41 49 04 04 04 04 // 4 bytes of PKCS7 padding ``` {% endcode %} #### Notification 0x0101, Tagged Data attached, Security is disabled (for both QR Code and NFC modes) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 // Notification 0x0101 82 04 40 08 01 02 // mDoc data attached (SessionData) 84 82 00 1F 01 01 // Notification Payload, 31 bytes 84 82 00 19 // Payload, 25 bytes FD 82 00 15 // Data Conatiner, 21 bytes 9F 01 82 00 04 // Tag 0x9F01, “family_name”, 4 bytes 43 48 4F 55 9F 02 82 00 07 // Tag 0x9F02, “given_name”, 7 bytes 57 45 49 2D 54 41 49 ``` {% endcode %} #### Notification 0x0101, SessionData failure has been detected (for both QR Code and NFC modes) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 01 // Notification 0x0101 82 04 40 08 02 02 // Event: SessionData Failure occurred ``` {% endcode %} #### Notification 0x0105, Timeout has occurred (for both QR Code and NFC modes) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 05 // Notification 0x0105 82 04 00 01 00 00 ``` {% endcode %} #### Notification 0x0105, Host Cancel (CMD 0x1008) (for both QR Code and NFC modes) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 05 // Notification 0x0105 82 04 00 03 01 00 ``` {% endcode %} #### Notification 0x0105, User Cancel (Display ONLY) (for both QR Code and NFC modes) {% code overflow="wrap" %} ``` AA 00 81 04 83 00 01 05 // Notification 0x0105 82 04 00 03 02 00 ``` {% endcode %} ### Notification Payload for mDoc Subscription Warning #### **Level 5 Heading:** Notification 0101 = Transaction Information Update


Tag	Len	Value / Description	Typ	Req	Default
84	var	Notification Payload
/81	1	Configured Warning Days (from OID 1.2.9.1.1.2 Byte 0)	B	R
/82	1	Calculated Days Remaining Until ValidTo	B	R
/83	8	Configured ValidTo Epoch time (uint64, little-endian)	B	R

{% hint style="info" %} **Example inner payload shape under 84:** 81 01 05 82 01 01 83 08 00 65 5D 6A 00 00 00 00 (5 warn days, 1 day remaining, ValidTo = 2026-07-20 00:00:00 UTC) {% endhint %} ### Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached

Tag	Len	Value / Description	Typ	Req
Beginning of Notification Message
0101 = DynaPro Format Transaction Data
84	var	Transaction Data	B	R
/null	(v)	EMV ARQC Type data blob, if the notification is an ARQC Update (Quick Chip) notification. EMV Batch Data Type data blob, if the notification is a Batch Data notification. Decoded raw barcode data, if the notification is a Barcode event notification. If the barcode data is Base64 encoded, the device sends the decoded version in binary format. NFC UID Type reports the unique ID from the NFC tag (EMV Contactless Only) GPO Response Type reports the card’s GPO Response (EMV Contactless Only)	B	O
End of Notification Message

### Notification Payload for Barcode Reader, Barcode Event, Type (Encrypted Data Attached)

Tag	Len	Value / Description	Typ	Req
Beginning of Notification Message
1805 = User Interface Operation Complete
84	var	Notification Payload	B	R
/DFDF59	var	Encrypted Data Primitive Decrypt the value of this TLV data object using the algorithm and variant specified in the Encrypted Data KSN parameter and the Encrypted Data Encryption Type parameter to read its contents. The format of the decrypted data is shown in Table 316.	B	R
/DFDF50	var	Encrypted Data KSN	B	R
/DFDF51	01	Encrypted Data Encryption Type — See section 4.4 Encryption Type for a list of valid values.	B	R
End of Notification Message

### Notification Payload for Barcode Reader, Barcode Event, Type, Data Attached (Unencrypted Data)

Tag	Len	Value / Description	Typ	Req	Default
FC	var	Barcode Data Container	T	R
/DF74	var	Barcode Data	B	O

### VAS Error Report

Tag	Len	Value / Description	Typ	Req
FC	var	VAS Error Container	T	R
/DFDF25	var	Device Serial Number (IFD Serial Number)	B	R
/DF75	var	VAS Error Report — Byte 1 = SW1 returned by the Apple or Android device; Byte 2 = SW2 returned by the Apple or Android device; Byte 3 = Slot Number; Byte 4 = Where in the VAS command sequence the error occurred: 0x00 = Select OSE Error; 0x01 = Get VAS Data Error (Apple only); 0x02 = Select Smart Tap Error (Google only); 0x03 = Negotiate Secure Session Error (Google only); 0x04 = Get Select Smart Tap Error (Google only).	B	R

Tag

Len

Value / Description

Typ

Req

Default

var

VAS Error Container

/DFDF25

var

Device Serial Number (IFD Serial Number)

/DF75

var

VAS Error Report —

Byte 1 = SW1 returned by the Apple or Android device;
Byte 2 = SW2 returned by the Apple or Android device;
Byte 3 = Slot Number;
Byte 4 = Where in the VAS command sequence the error occurred:

0x00 = Select OSE Error;
0x01 = Get VAS Data Error (Apple only);
0x02 = Select Smart Tap Error (Google only);
0x03 = Negotiate Secure Session Error (Google only);
0x04 = Get Select Smart Tap Error (Google only).

### Notification Example - VAS Error Report - A {% code title="Example (hex)" %} ``` AA 00 81 04 83 00 01 01 82 04 10 08 02 02 84 82 01 F8 01 01 84 82 01 F2 01 E9 F9 82 01 E5 DF DF 54 0A 00 00 00 00 00 00 00 00 00 00 DF DF 55 01 82 DF DF 25 0F 42 34 44 42 38 31 37 31 31 31 39 31 39 41 41 FA 82 01 BB 70 82 01 B7 DF DF 53 01 00 5F 20 12 47 55 53 54 49 4E 2F 53 54 45 50 48 41 4E 49 45 20 4D 5F 30 02 02 01 DF DF 4D 25 3B 35 33 32 32 30 30 30 30 36 30 30 30 31 36 37 34 3D 31 38 30 39 32 30 31 30 30 30 30 30 30 30 30 30 30 30 3F DF DF 52 01 05 F8 82 01 66 DF DF 59 82 01 48 36 69 98 57 4C 81 08 66 28 B6 1F DD 69 B1 C3 43 F7 BA 98 B2 5A 92 53 5F DA 63 6D DA 44 95 F1 15 2D 01 07 9A 4C EB 28 0B 30 5C 21 B2 39 ED E7 EE B6 1A 79 43 56 2E 26 1E C9 87 86 19 68 FA EB 4A 2B BD F5 5D 54 6F C4 67 97 FF 42 2C D6 CF 36 03 48 58 A4 23 9B 51 03 5C 32 0B DC 5E 4E E5 95 1B B5 C5 18 E7 33 0B D2 FE 8D E8 5C 47 4D 3C 16 79 42 48 1D CD 83 D5 58 64 48 23 17 F3 29 A7 F1 F1 75 F4 B9 C6 45 F3 02 28 1C 90 C7 83 B9 49 AF 56 BD 76 73 E7 45 7D 25 C5 77 3F C7 9A 1B ED 52 0A 05 54 15 B7 9A 2A 59 C1 67 6D E2 8C 02 8B 97 64 96 5D 4C F8 31 A2 20 75 12 8D 99 C1 A2 DF AB 55 0A 62 24 79 CF A8 51 3D AE 84 91 A5 80 19 9F BC 75 B0 F9 56 5E BA 57 A3 B1 61 AA 84 43 F0 D8 E6 44 C1 FA 51 0E 0A B0 F7 F2 61 57 5B 86 7E AB DC 49 00 87 A0 3B 69 5F C1 45 C4 10 9A A8 5F B6 30 59 2C 25 FA 15 A5 44 83 24 96 3D 5A 03 50 36 02 EC 6B 15 7C 8D CC 66 BF B7 F4 CF 4C 6D 67 75 87 B9 4E D4 08 76 25 F8 B8 EF BF A8 A0 72 F9 81 AB FF 49 84 E7 BC 8F C5 DD A0 86 B2 74 DD 59 8A B2 83 5D DD CC 0C 30 01 96 DF DF 56 0A 90 10 01 0B 4D B8 17 00 00 03 DF DF 57 01 80 DF DF 58 01 05 00 00 00 00 00 00 00 ``` {% endcode %} ### Notification Example - VAS Error Report - B {% code title="Example (hex)" %} ``` 03 DF DF 57 01 80 DF DF 58 01 05 00 00 00 00 00 00 00 ``` {% endcode %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.magtek.com/api-and-command-reference/7-30-26-draft-version-scra-dynafamily-programmers-manual/7-30-26-draft-version-notifications/7-30-26-draft-version-0x0101-transaction-information-update.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.