> 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/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update.md).

# 0x1001 - Device Information Update

This notification reports information about general state changes that occur within the device, outside the context of specific operations like transactions ([<mark style="color:red;">**Notification Source 0x01nn - Notifications from Transactions**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x01nn-transactions)**), requests the host receives from the firmware’s integrated display interface (**[<mark style="color:red;">**Notification Source 0x18nn - Notifications from User Interface**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x18nn-from-user-interface)), and so on.

For this notification, Notification Detail described in [<mark style="color:red;">**Notification Message**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format) contains one byte each, shown in the tables below, to indicate:

* The Category (Cat) of notification (for example, the subsystem the notification is originating from)
* The Reason (Rsn) for the notification (Device Event)
* 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

The other optional message parameters in the [<mark style="color:red;">**Notification Message**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format) depend on which combination of four bytes is included in Notification Detail, and are described below.

## Notification Detail Codes - Category 0x00 Power / Reset

<table><thead><tr><th width="75.727294921875">Cat</th><th width="75.3636474609375">Rsn</th><th width="71.63641357421875">Det</th><th width="74.54541015625">Ext</th><th>Meaning</th><th width="124.72723388671875">Detail Code</th></tr></thead><tbody><tr><td colspan="6"><p></p><p>Category <strong>0x00 Power / Reset</strong> contains notification detail codes involving the device’s power and reset functionality. Each possible notification has a unique <strong>Reason</strong> value:</p><ul><li>Reason 0x00 = Device Reset Occurred</li><li>Reason 0x01 = Device Reset Will Occur Soon</li><li>Reason 0x02 = Low Battery</li><li>Reason 0x03 = Key Management</li><li>Reason 0x04 = Temperature</li></ul></td></tr><tr><td>00</td><td>00</td><td>00</td><td>00</td><td><p>Power/Reset, Device Reset Occurred, Reserved, Reserved</p><p></p><p>The device sends and repeats this notification after the device power cycles or resets, depending on the setting in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.1.1-device-reset-occurred-notification-control"><mark style="color:red;"><strong>Property 1.2.7.1.1.1 - Device Reset Occurred Notification Control</strong></mark></a>. If it is set to repeat, it does so until the host acknowledges it using <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.1.2-device-reset-occurred-notification-acknowledged"><mark style="color:red;"><strong>Property 1.2.7.1.1.2 Device Reset Occurred Notification Acknowledged</strong></mark></a>. </p><p></p><p>These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>, as shown in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-device-reset-occurred"><strong>Notification Payload for Device Reset Occurred</strong>.</a></p></td><td>00000000</td></tr><tr><td>00</td><td>01</td><td> 0</td><td>00</td><td><p>Power/Reset, Device Reset Will Occur Soon, Reserved, Reserved</p><p></p><p>The device sends this notification before it automatically resets to conform to PCI’s 24 hour Self-Test requirement, and behaves according to the setting in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.1.3-device-reset-will-occur-soon-notification-control"><mark style="color:red;"><strong>Property 1.2.7.1.1.3  - Device Reset Will Occur Soon Notification Control</strong>.</mark> </a></p><p></p><p>See <a href="https://developer.magtek.com/guides/guides/security-and-key-management/pci-requirements"><mark style="color:red;"><strong>24 Hour Automatic Reset PCI Requirement</strong></mark></a> for more information. </p><p></p><p>These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>, which directly contains one byte indicating the number of minutes (0x01 to 0xFF) until the device will perform the reset.</p></td><td>0001000</td></tr><tr><td>00</td><td>02</td><td>00</td><td>00</td><td><p>Power/Reset, Battery, Low Battery Warning, Percent</p><p></p><p>The device sends this notification when the battery charge reaches 15 percent. If a device is powered on with a charge that is already 15 percent or below, this notification is sent shortly after power up and includes the current battery charge percentage. Percent indicates the percent of battery charge remaining. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-low-battery-warning"><strong>Notification Payload - Low Battery Warning</strong></a>.</p></td><td>00020000</td></tr><tr><td>00</td><td>02</td><td>01</td><td>00</td><td><p>Power/Reset, Battery, Power Down Imminent, Reserved</p><p></p><p>The device sends this notification one minute before it automatically powers down the device because the battery charge has reached 0 percent. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-low-battery-shutdown"><strong>Notification Payload - Low Battery Shutdown</strong></a>.</p></td><td>00020100</td></tr><tr><td>00</td><td>02</td><td> 02</td><td>00</td><td><p>Power/Reset, Battery, Battery Charge Complete, Reserved</p><p></p><p>The device sends this notification when the battery charger detects that the battery is fully charged. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-battery-charged"><strong>Notification Payload - Battery Charged</strong></a>.</p></td><td>00020200</td></tr><tr><td>00</td><td>02</td><td>03</td><td>00</td><td>Power/Reset, Battery, Battery Too Hot, Reserved</td><td>00020300</td></tr><tr><td>00</td><td>02</td><td>04</td><td>00</td><td>Power/Reset, Battery, Battery Too Cold, Reserved </td><td>00020400</td></tr><tr><td>00</td><td>02</td><td>05</td><td>00</td><td>Power/Reset, Battery, Battery Temperature Normal, Reserved </td><td>00020500</td></tr><tr><td>00</td><td>03</td><td>00</td><td>00</td><td><p>Power/Reset, Device reset per Command 0x1F01.</p><p></p><p>The device sends this notification to notify the host when Device executes Reset Command 0x1F01.</p></td><td>00030000</td></tr></tbody></table>

#### Notification Payload - Device Reset Occurred

<table><thead><tr><th width="100">Tag</th><th width="76">Len</th><th>Value / Description</th><th width="75.727294921875">Typ</th><th width="76.3636474609375">Req</th><th width="97.0909423828125">Default</th></tr></thead><tbody><tr><td colspan="6">Beginning of <strong>Notification Message</strong><br>1001 = Device Information Update</td></tr><tr><td>81</td><td>var</td><td>This parameter has the same length and value described by <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/2.3.1.nnn-system-status-information/2.3.1.2.1.n-system-status-device-state-information#device-operational-status-property-2.3.1.2.1.1"><mark style="color:red;"><strong>Property 2.3.1.2.1.1 - Device Operational Status</strong></mark>.</a></td><td>B</td><td>R</td><td></td></tr><tr><td>82</td><td>var</td><td>This parameter has the same length and value described by <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/2.3.1.nnn-system-status-information/2.3.1.2.1.n-system-status-device-state-information#property-2.3.1.2.1.2-offline-status-detail"><mark style="color:red;"><strong>Property 2.3.1.2.1.2</strong>. - <strong>Offline Status Detail</strong></mark><strong>.</strong></a></td><td>B</td><td>R</td><td></td></tr><tr><td>xx</td><td>var</td><td>More data objects may be added in future firmware revisions.</td><td></td><td></td><td></td></tr><tr><td colspan="6">End of <strong>Notification Message</strong> </td></tr></tbody></table>

**Device Reset Occurred Example**

{% code title="Example (hex)" %}

```
AA00 81 04 83001001 82 04 00000000 84 08 1001 81 01 02 82 01 00
```

{% endcode %}

#### Notification Payload - Low Battery Warning&#x20;

The device sends this notification when the battery charge reaches 15 percent. If a device is powered on with a charge that is already 15 percent or below, this notification is sent shortly after power up and includes the current battery charge percentage. Percent indicates the percent of battery charge remaining.

It is recommended that the device is charged using a USB power source soon after receiving this notification. See [<mark style="color:red;">**Notification Message Format**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format) and [<mark style="color:red;">**Low Battery Notification Example**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-low-battery-warning#low-battery-notification-example).

{% hint style="warning" %}
Charge the device using a USB power source soon after receiving this notification.
{% endhint %}

**Low Battery Notification Example**

{% code title="Example (hex)" %}

```
AA 00 81 04 83 00 10 01 82 00 02 00 0D
```

{% endcode %}

#### Notification Payload - Low Battery Shutdown

The device sends this notification one minute before it automatically powers down the device. This occurs when the battery charge has reached 0 percent. Shutdown can be prevented by connecting the device to a USB power source. See [<mark style="color:red;">**Notification Message Format**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format) and **Low Battery Shutdown Response Example**.

Low Battery Shutdown Response Example

{% code title="Example (hex)" %}

```
AA 00 81 04 83 00 10 01 82 00 02 01 00
```

{% endcode %}

#### Notification Payload - Battery Charged

The device sends this notification when the battery charger detects that the battery is fully charged. This only occurs when the device is powered by a USB power source. See [<mark style="color:red;">**Notification Message Format**</mark>](#notification-example-for-touch-sensor-press-or-release-on-display-touch-only) and **Battery Charged Notification Example**.

**Battery Charged Notification Example**

{% code title="Example (hex)" %}

```
AA 00 81 04 83 00 10 01 82 00 02 02 00
```

{% endcode %}

***

## Notification Detail Codes - Category 0x01 User Event

<table><thead><tr><th width="74">Cat</th><th width="75.54547119140625">Rsn</th><th width="72.6363525390625">Det</th><th width="70.818115234375">Ext</th><th>Meaning</th><th width="126.33343505859375">Detail Codes</th></tr></thead><tbody><tr><td colspan="6"><p>Category 0x01 User Event contains notification detail codes involving events triggered by user actions. Each possible notification has a unique Reason value:</p><ul><li>Reason 0x00 = Contactless Card Presented (EMV Contactless Only)</li><li>Reason 0x01 = Contactless Card Removed (EMV Contactless Only)</li><li>Reason 0x02 = Card Seated in Slot (EMV Contact Only)</li><li>Reason 0x03 = Card Unseated from Slot (EMV Contact Only)</li><li>Reason 0x04 = Card Swiped (MSR Only)</li><li>Reason 0x05 = Touch Sensor Press On Display (Touch Only)</li><li>Reason 0x06 = Touch Sensor Release On Display (Touch Only)</li><li>Reason 0x07 = Barcode Read (BCR Only)</li></ul><p></p><p>The host can use <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.2.1-user-event-notification-controls-enable"><mark style="color:red;"><strong>Property</strong></mark> <mark style="color:red;"><strong>1.2.7.1.2.1 - User Event Notification Controls Enable</strong></mark></a> to enable these notification reasons individually.</p><p> </p><p>The host may choose to use these notifications to determine when to send additional commands. For example, it may send <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction</strong></mark></a>. The host should do this as quickly as possible to minimize the response time between when the cardholder presents a card and when the device provides feedback via a visible or audible state change or attempts to read a chip card. Note there are cases where the device may send a notification with Reason = Contactless Card Presented while the cardholder is inserting or swiping a card, so the host should start transactions with all supported card interfaces enabled to maximize the chances of a successful card read.</p></td></tr><tr><td>01</td><td>00</td><td>00</td><td>00</td><td>User Event, Contactless Card Presented, EMV, Reserved (EMV Contactless Only)</td><td>01000000</td></tr><tr><td>01</td><td>01</td><td>00</td><td>00</td><td>User Event, Contactless Card Removed, EMV, Reserved (EMV Contactless Only)</td><td>01010000</td></tr><tr><td>01</td><td>00</td><td>01</td><td>00</td><td>User Event, Contactless Card Presented, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://sites.gitbook.com/preview/site_ybA8x/api-and-command-reference/~/revisions/Q4BoOPqXE84vIVcK0N1m/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update?theme=light#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. A sample notification is shown here: <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-battery-charged#notification-payload-for-uid"><mark style="color:red;"><strong>Notification Payload for UID Example</strong></mark></a></td><td>01000100</td></tr><tr><td>01</td><td>01</td><td>01</td><td>00</td><td>User Event, Contactless Card Removed, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only)</td><td>01010100</td></tr><tr><td>01</td><td>00</td><td>02</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE Classic, 1K (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://sites.gitbook.com/preview/site_ybA8x/api-and-command-reference/~/revisions/Q4BoOPqXE84vIVcK0N1m/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update?theme=light#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. A sample UID notification is also.</td><td>01000200</td></tr><tr><td>01</td><td>01</td><td>02</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Classic, 1K (EMV Contactless Only)</td><td>01010200</td></tr><tr><td>01</td><td>00</td><td>03</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE Classic, 4K (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. A sample UID notification is also.</td><td>01000300</td></tr><tr><td>01</td><td>01</td><td>03</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Classic, 4K (EMV Contactless Only)</td><td>01010300</td></tr><tr><td>01</td><td>00</td><td>04</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE DESFire Light (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a><mark style="color:red;"><strong>.</strong></mark> UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong>.</a> A sample UID notification is also.</td><td>01000400</td></tr><tr><td>01</td><td>01</td><td>04</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE DESFire Light (EMV Contactless Only)</td><td>01010400</td></tr><tr><td>01</td><td>00</td><td>05</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000500</td></tr><tr><td>01</td><td>01</td><td>05</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE MINI® (EMV Contactless Only)</td><td>01010500</td></tr><tr><td>01</td><td>00</td><td>06</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000600</td></tr><tr><td>01</td><td>01</td><td>06</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Plus EV1 (EMV Contactless Only)</td><td>01010600</td></tr><tr><td>01</td><td>00</td><td>07</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000700</td></tr><tr><td>01</td><td>01</td><td>07</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Plus EV2 (EMV Contactless Only)</td><td>014010700</td></tr><tr><td>01</td><td>00</td><td>08</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a><mark style="color:red;"><strong>e</strong></mark>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000800</td></tr><tr><td>01</td><td>01</td><td>08</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Plus SE (EMV Contactless Only)</td><td>01010800</td></tr><tr><td>01</td><td>00</td><td>09</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000900</td></tr><tr><td>01</td><td>01</td><td>09</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE Plus X (EMV Contactless Only)</td><td>01010900</td></tr><tr><td>01</td><td>00</td><td>0A</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000A00</td></tr><tr><td>01</td><td>01</td><td>0A</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE DESFire EV1 (EMV Contactless Only)</td><td>01010A00</td></tr><tr><td>01</td><td>00</td><td>0B</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000B00</td></tr><tr><td>01</td><td>01</td><td>0B</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE DESFire EV2 (EMV Contactless Only)</td><td>01010B00</td></tr><tr><td>01</td><td>00</td><td>0C</td><td>00</td><td>User Event, Contactless Card Presented, MIFARE MINI® (EMV Contactless Only). The contactless reader has successfully read a NFC tag. In this case, the device includes UID data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>. UID Data is in the format described in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-uid"><strong>Notification Payload for UID</strong></a>. An example UID notification is also included.</td><td>01000C00</td></tr><tr><td>01</td><td>01</td><td>0C</td><td>00</td><td>User Event, Contactless Card Removed, MIFARE DESFire EV3 (EMV Contactless Only)</td><td>01010C00</td></tr><tr><td>01</td><td>02</td><td>00</td><td>00</td><td>User Event, Card Seated in Slot, Reserved, Reserved (EMV Contact Only)</td><td>01020000</td></tr><tr><td>01</td><td>03</td><td>00</td><td>00</td><td>User Event, Card Unseated from Slot, Reserved, Reserved (EMV Contact Only)</td><td>01030000</td></tr><tr><td>01</td><td>04</td><td>00</td><td>00</td><td>User Event, Card Swiped, Reserved, Reserved (MSR Only). When the host receives this notification, it should call <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction</strong></mark> b</a>efore the timeout configured in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.2.2-user-event-notification-msr-data-timeout-msr-only"><mark style="color:red;"><strong>Property 1.2.7.1.2.2 - User Event Notification MSR Data Timeout (MSR Only)</strong></mark></a> to process the MSR swipe data the device is temporarily storing in memory.</td><td>01040000</td></tr><tr><td>01</td><td>05</td><td>00</td><td>00</td><td>User Event, Touch Sensor Press On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a><mark style="color:red;">,</mark> as shown in<a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-touch-sensor-press-or-release-on-display"> <strong>Notification Payload for Touch Sensor Press/Release</strong></a><strong>.</strong></td><td>01050000</td></tr><tr><td>01</td><td>06</td><td>00</td><td>00</td><td>User Event, Touch Sensor Press On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a><mark style="color:red;">,</mark> as shown in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-touch-sensor-press-or-release-on-display"><strong>Notification Payload for Touch Sensor Press/Release.</strong></a></td><td>01060000</td></tr><tr><td>01</td><td>07</td><td>00</td><td>00</td><td><p>Type values:</p><ul><li>Type 0x00 = Unknown</li><li>Type 0x01 = MagTek</li><li>Type 0x02 = EMV</li></ul><p>The barcode reader has successfully read a barcode. In this case, the device includes barcode data in the Notification Payload portion of the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Messag</strong></mark></a><mark style="color:red;"><strong>e</strong></mark>. If the data is encrypted, the data is in the format described in Notification Payload for Personal Info Entry. Data that is not encrypted is in the format described in Unencrypted Barcode Payload.</p></td><td>01070000</td></tr></tbody></table>

#### **Notification Payload - UID**

<table><thead><tr><th width="100">Tag</th><th width="64.18182373046875">Len</th><th>Value / Description</th><th width="74.818115234375">Typ</th><th width="75.3636474609375">Req</th><th width="98.9090576171875">Default</th></tr></thead><tbody><tr><td colspan="6">Beginning of <strong>Notification Message</strong><br>1001 = Device Information Update</td></tr><tr><td>84</td><td>var</td><td>NFC Payload</td><td>B</td><td>R</td><td></td></tr><tr><td>/DF79</td><td>var</td><td>NFC UID</td><td>B</td><td>R</td><td></td></tr><tr><td colspan="6">End of <strong>Notification Message</strong></td></tr></tbody></table>

**Notification Payload for UID Example**

{% code title="Example (hex)" %}

```
AA 00 81 04 83 00 10 01 82 04 01 00 01 00 84 0E 10 01 84 0A DF 79 07 04 37 1F 71 BF 61 80
```

{% endcode %}

#### **Notification Payload - Touch Sensor Press or Release On Display**

<table><thead><tr><th width="100">Tag</th><th width="100">Len</th><th>Value / Description</th><th width="74">Typ</th><th width="74.5455322265625">Req</th><th width="97.0908203125">Default</th></tr></thead><tbody><tr><td colspan="6">Beginning of <strong>Notification Message</strong> <br>1001 = Device Information Update</td></tr><tr><td>81</td><td>04</td><td>Press / Release Coordinates of the press / release from origin 0,0 at the top left corner of the display, automatically adjusted to match the device’s orientation as configured by <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/2.3.1.nnn-system-status-information/2.3.1.2.1.n-system-status-device-state-information#device-operational-status-property-2.3.1.2.1.1"><mark style="color:red;"><strong>Property 2.3.1.2.1.1 - Device Operational Status</strong></mark></a>. Bytes 1..2 X Coordinate X coordinate of press / release, in big endian order. Bytes 3..4 Y Coordinate Y Coordinate of press / release, in big endian order.</td><td>B</td><td>R</td><td></td></tr><tr><td colspan="6">End of <strong>Notification Message</strong></td></tr></tbody></table>

**Touch Sensor Press or Release Example**

{% code title="Example (hex)" %}

```
AA00 81 04 83001001 82 04 00000000 84 08 1001 81 04 00 80 00 80
```

{% endcode %}

***

## Notification Detail Codes - Category 0x02 — Session Management

<table><thead><tr><th width="100">Cat</th><th width="75.45452880859375">Rsn</th><th width="75.3636474609375">Det</th><th width="69.9090576171875">Ext</th><th>Meaning</th><th width="123.93951416015625">Detail Codes</th></tr></thead><tbody><tr><td colspan="6"><p>Category <strong>0x02 Session Management</strong> contains notification detail codes involving session management functionality (Session Management Only). Each possible notification has a unique <strong>Reason</strong> value:</p><ul><li>Reason 0x00 = Session Expiring Soon</li></ul></td></tr><tr><td>02</td><td>00</td><td>00</td><td>00</td><td><p>Session Management, Session Expiring Soon, Reserved, Reserved</p><p></p><p>The device sends this notification 5 minutes before a session expires and every minute after that until the session is extended or the connection is closed. The host can optionally extend the session with <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f03-extend-session-session-management-only"><mark style="color:red;"><strong>Command 0x1F03 - Extend Session</strong></mark></a> or by sending any command request. These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>, as shown in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-session-expiring-soon-session-management-only"><strong>Notification Payload for Session Expiring Soon</strong></a>.</p></td><td>02000000</td></tr></tbody></table>

#### **Notification Payload - Session Expiring Soon (Session Management Only)**

<table><thead><tr><th width="100">Tag</th><th width="72.3636474609375">Len</th><th>Value / Description</th><th width="73.818115234375">Typ</th><th width="75.3636474609375">Req</th><th width="100.7271728515625">Default</th></tr></thead><tbody><tr><td colspan="6">Beginning of <strong>Notification Message</strong><br>1001 = Device Information Update</td></tr><tr><td>81</td><td>1</td><td>Interface 0x00 = WLAN</td><td>B</td><td>R</td><td></td></tr><tr><td>82</td><td>1</td><td>Connection 0x00 = Connection 0, Interfaces that only support one connection will use connection 0. WLAN will always set this to 0 even if the device is configured to support more than one connection with <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.2.1.nn-basic-properties#property-1.2.2.1.1.a-maximum-client-connections"><mark style="color:red;"><strong>Property 1.2.2.1.1.A - Maximum Client Connections</strong></mark></a> since there is only a single session for all clients. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f03-extend-session-session-management-only"><mark style="color:red;"><strong>Command 0x1F03 - Extend Session (Session Management Only)</strong></mark></a> for more information on this scenario.</td><td>B</td><td>R</td><td></td></tr><tr><td>83</td><td>1</td><td>Expiration Time The time in minutes until the session expires.</td><td>B</td><td>R</td><td></td></tr><tr><td>xx</td><td>var</td><td>More data objects may be added in future firmware revisions.</td><td></td><td></td><td></td></tr><tr><td colspan="6">End of Notification Message</td></tr></tbody></table>

#### **Session Expiring Soon (Session Management Only) Example**

{% code title="Example (hex)" %}

```
AA00 81 04 83001001 82 04 00000000 84 0B 1001 81 01 00 82 01 00 83 01 05
```

{% endcode %}

***

## Notification Detail Codes - Category 0x03 — Key Management (WLAN Only)

<table><thead><tr><th width="100">Cat</th><th width="76.272705078125">Rsn</th><th width="100">Det</th><th width="74.54541015625">Ext</th><th>Meaning</th><th width="100">Detail Codes</th></tr></thead><tbody><tr><td colspan="6"><p>Category <strong>0x03 Key Management</strong> contains notification detail codes involving key management functionality (WLAN Only). Each possible notification has a unique <strong>Reason</strong> value:</p><ul><li>Reason 0x00 = CSR keys generated</li><li>Reason 0x01 = Certificate Expiring Soon</li></ul></td></tr><tr><td>03</td><td>00</td><td>00</td><td>00</td><td><p>Key management, CSR keys generated, Reserved, Reserved</p><p></p><p>This notification does not include a Notification Payload. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0xennn-security/0xef02-generate-csr-keys-wlan-only"><mark style="color:red;"><strong>Command 0xEF02 - Generate CSR keys (WLAN Only)</strong></mark> </a>for more information.</p></td><td>03000000</td></tr><tr><td>03</td><td>01</td><td>00</td><td>00</td><td>Key management, Certificate Expiring Soon, Reserved, Reserved. See <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.2.1.nn-wlan-settings-wlan-only-a#property-1.2.2.1.1.b-certificate-expiring-soon-notification-threshold"><mark style="color:red;"><strong>Property 1.2.2.1.1.B - Certificate Expiring Soon Notification Threshold</strong></mark></a> for more information. These notifications always include the Notification Payload parameter in the <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format"><mark style="color:red;"><strong>Notification Message</strong></mark></a>, as shown in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update#notification-payload-key-management-certificate-expiring-soon-session-management-only"><strong>Notification Payload for Key management, Certificate Expiring Soon</strong></a>.</td><td>03010000</td></tr></tbody></table>

#### **Notification Payload - Key management, Certificate Expiring Soon (Session Management Only)**

<table><thead><tr><th width="100">Tag</th><th width="75.9090576171875">Len</th><th>Value / Description</th><th width="75.727294921875">Typ</th><th width="77.272705078125">Req</th><th width="97.0908203125">Default</th></tr></thead><tbody><tr><td colspan="6">Beginning of <strong>Notification Message</strong><br>1001 = Device Information Update</td></tr><tr><td>81</td><td>1</td><td>This parameter has the same length and value described by <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.2.1.nn-wlan-settings-wlan-only-a"><mark style="color:red;"><strong>Property 1.2.2.1.1.B - Certificate Expiring Soon Notification Threshold</strong></mark></a>.</td><td>B</td><td>R</td><td></td></tr><tr><td>82</td><td>1</td><td>This parameter contains the certificate identifier. See the certificate file type section (File Type 0x03) from File Types to identify this certificate by locating the certificate that has a File Subtype that matches this certificate identifier.</td><td>B</td><td>R</td><td></td></tr><tr><td>83</td><td>1</td><td>The number of days the certificate is still valid.</td><td>B</td><td>R</td><td></td></tr><tr><td colspan="6">End of <strong>Notification Message</strong></td></tr></tbody></table>

**Key management, Certificate Expiring Soon (Session Management Only) Example**

{% code title="Example (hex)" %}

```
```

{% endcode %}

***

## Notification Detail Codes - Category 0x04 — Temperature

<table><thead><tr><th width="100">Cat</th><th width="73.54541015625">Rsn</th><th width="71.63629150390625">Det</th><th width="77.272705078125">Ext</th><th>Meaning</th><th width="128.87884521484375">Detail Codes</th></tr></thead><tbody><tr><td colspan="6"><p>Category <strong>0x04 Temperature</strong> contains notification detail codes involving temperature reporting. Each possible notification has a unique <strong>Reason</strong> value:</p><ul><li>Reason 0x00 = Temperature out of range</li></ul></td></tr><tr><td>04</td><td>00</td><td>00</td><td>00</td><td><p>Temperature, Out of Range, Low Warning, Temperature.</p><p>The device sends this notification when the device’s temperature falls below the temperature set in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.4.2-device-high-temperature-notification-level"><mark style="color:red;"><strong>Property 1.2.7.1.4.1 - Low Te</strong></mark></a><mark style="color:red;"><strong>mperature Notification Level</strong></mark>. The temperature reported is in Celsius.</p></td><td>04000000</td></tr><tr><td>04</td><td>00</td><td>01</td><td>00</td><td>Temperature, Out of Range, High Warning, Temperature. The device sends this notification when the device’s temperature rises above the temperature set in <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/properties/1.2.nnnn-device-settings/1.2.7.nnn-system-settings-b#property-1.2.7.1.4.2-device-high-temperature-notification-level"><mark style="color:red;"><strong>Property 1.2.7.1.4.2 - High Temperature Notification Level</strong></mark></a>. The temperature reported is in Celsius.</td><td>04010100</td></tr></tbody></table>

***

## Notification Detail Codes - Category 0x05 — Subscription Status

<table data-header-hidden><thead><tr><th width="62.81817626953125" valign="top"></th><th width="61.1817626953125" valign="top"></th><th width="87.3636474609375" valign="top"></th><th width="66.33331298828125" valign="top"></th><th valign="top"></th><th width="100"></th></tr></thead><tbody><tr><td valign="top"><strong>Cat</strong></td><td valign="top"><strong>Rsn</strong></td><td valign="top"><strong>Det</strong></td><td valign="top"><strong>Ext</strong></td><td valign="top"><strong>Meaning</strong></td><td><strong>Detail Codes</strong></td></tr><tr><td colspan="6" valign="top"><p></p><p>Category <strong>0x05 Subscription Status</strong> contains notification detail codes involving the device's subscriptions. Each possible notification has a unique Reason value:</p><ul><li>Reason 0x00 = mDoc Subscription</li></ul><p>For Reason 0x00, Detail 0x01 = Expiration, and the Extra byte gives the expiration state:</p><ul><li>Extra 0x01 = Warning (the subscription is approaching expiration)<br>Extra 0x02 = Expired </li></ul><p>The expiration warning period and notification interval are configurable.</p><ul><li>When a notification is due, the device sends Notification 0x1001 Device Information Update with either Subscription Warning (05000101) or Subscription Expired (05000102).</li><li>After a notification is sent, another notification will not be sent until at least the configured notification interval has elapsed.</li><li>After <strong>Subscription Expired</strong> (<code>05000102</code>), the device disables <strong>0x1201 - Read Mobile Document</strong> and <strong>0x1202 - Age Verification for ISO 18013-5</strong> until a new subscription is provisioned. Payment and other non-mDoc functions are unaffected.</li></ul><p>The two table rows below that (05 00 01 01 and 05 00 01 02) already match the code, so they can stay as they are.</p></td></tr><tr><td valign="top">05</td><td valign="top">00</td><td valign="top">01</td><td valign="top">01</td><td valign="top">Subscription Status, mDoc Subscription, Expiration, Warning</td><td>05000101</td></tr><tr><td valign="top">05</td><td valign="top">00</td><td valign="top">01</td><td valign="top">02</td><td valign="top">Subscription Status, mDoc Subscription, Expiration, Expired</td><td>05000102</td></tr></tbody></table>

#### Notification Payload - mDoc Subscription

<table data-header-hidden><thead><tr><th width="66.18182373046875" valign="top"></th><th width="59.81817626953125" valign="top"></th><th valign="top"></th><th width="78.9090576171875" valign="top"></th><th width="69.4544677734375" valign="top"></th><th width="100" valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Tag</strong></td><td valign="top"><strong>Len</strong></td><td valign="top"><strong>Value / Description</strong></td><td valign="top"><strong>Typ</strong></td><td valign="top"><strong>Req</strong></td><td valign="top"><strong>Default</strong></td></tr><tr><td valign="top"> </td><td valign="top">2</td><td valign="top">Notification ID 0x1001</td><td valign="top"> </td><td valign="top"> </td><td valign="top"> </td></tr><tr><td valign="top">81</td><td valign="top">1</td><td valign="top">Configured Warning Days (from OID 1.2.9.1.1.2 Byte 0)</td><td valign="top">B</td><td valign="top">R</td><td valign="top"> </td></tr><tr><td valign="top">82</td><td valign="top">1</td><td valign="top">Calculated Days Remaining Until ValidTo</td><td valign="top">B</td><td valign="top">R</td><td valign="top"> </td></tr><tr><td valign="top">83</td><td valign="top">8</td><td valign="top">Configured ValidTo Epoch time (uint64, little-endian)</td><td valign="top">B</td><td valign="top">R</td><td valign="top"> </td></tr><tr><td colspan="6" valign="top"><p>Example inner payload shape under 84:</p><p>81 01 05 82 01 01 83 08 00 65 5D 6A 00 00 00 00</p><p>(5 warn days, 1 day remaining, ValidTo = 2026-07-20 00:00:00 UTC)</p></td></tr></tbody></table>

***

## Notification Detail Codes - Category 0x06 — Automatic Transaction Start

<table data-header-hidden data-search="false"><thead><tr><th width="61.66668701171875" valign="top"></th><th width="64" valign="top"></th><th width="57.33331298828125" valign="top"></th><th width="77" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Cat</strong></td><td valign="top"><strong>Rsn</strong></td><td valign="top"><strong>Det</strong></td><td valign="top"><strong>Ext</strong></td><td valign="top"><strong>Meaning</strong></td></tr><tr><td colspan="5" valign="top"><p>Notification 0x1001 (Device Information Update) reports device-level status and events to the host outside of a transaction. Each notification is identified by a four-byte code (Category / Reason / Detail / Extra). Category 0x06 Automatic Transaction Start reports whether the device started a session from stored configuration, or skipped / blocked a start.</p><p>Category <strong>0x06 Automatic Transaction Start</strong> reports ATS status to the host: when the device is listening for media, when it starts a transaction, and when it does not start one and why.</p><ul><li>Reason 0x01 = OID problem</li><li>Reason 0x02 = Listening</li><li>Reason 0x03 = Triggered</li><li>Reason 0x04 = Blocked</li></ul><p>These notifications do not include a Notification Payload.</p></td></tr><tr><td valign="top">06</td><td valign="top">01</td><td valign="top">00</td><td valign="top">00</td><td valign="top">ATS Status, OID problem, Reserved, Reserved<br><br>A required ATS property can't be read, so no transaction is started</td></tr><tr><td valign="top">06</td><td valign="top">02</td><td valign="top">00</td><td valign="top">00</td><td valign="top">ATS Status, Listening, Reserved, Reserved<br><br>At power-up if ATS is on, and after each ATS transaction ends. Not sent when ATS is turned on with a SET</td></tr><tr><td valign="top">06</td><td valign="top">03</td><td valign="top">00</td><td valign="top">00</td><td valign="top">ATS Status, Triggered, Reserved, Reserved<br><br>Configuration read OK; sent just before the transaction runs</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">01</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Host Command 0x1001 Rejected, Reserved<br><br>Host sent 0x1001 while ATS is on</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">02</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Transaction Not Idle, Reserved<br><br>Media presented while a transaction is already running</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">03</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Non-Payment Contactless (mDL), Reserved<br><br>An mDL (non-payment contactless) was presented</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">04</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, NFC Not Enabled, Reserved<br><br>A MIFARE card was presented but Reader Options tag 83 has the NFC bit off</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">05</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Device Busy, Reserved<br><br>PIN entry, an on-demand barcode read, or UI settings is in progress.</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">06</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Device Offline, Reserved<br><br>The device is offline.</td></tr><tr><td valign="top">06</td><td valign="top">04</td><td valign="top">07</td><td valign="top">00</td><td valign="top">ATS Status, Blocked, Internal Error, Reserved<br><br>The device could not allocate memory or save the transaction data.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x10nn-from-device/0x1001-device-information-update.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
