This notification reports information about general state changes that occur within the device, outside the context of specific operations like transactions (Notification Source 0x01nn - Notifications from Transactions), requests the host receives from the firmware’s integrated display interface (Notification Source 0x18nn - Notifications from User Interface), and so on.
For this notification, Notification Detail described in section 3.2.2.3 Notification Message 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 Notification Message depend on which combination of four bytes is included in Notification Detail, and are described below.
The device can notify the host when the mDoc subscription is approaching expiration or has expired. The expiration warning period and notification interval are configurable.
When a notification is due, the device sends a Device Notification Event (0x1001) indicating either Subscription Warning or Subscription Expired.
After a notification is sent, another notification will not be sent until at least the configured notification interval has elapsed.
Category 0x02 Session Management contains notification detail codes involving session management functionality (Session Management Only). Each possible notification has a unique Reason value:
Reason 0x00 = Session Expiring Soon
Category 0x03 Key Management contains notification detail codes involving key management functionality (WLAN Only). Each possible notification has a unique Reason value:
Reason 0x00 = CSR keys generated
Reason 0x01 = Certificate Expiring Soon
Category 0x04 Temperature contains notification detail codes involving temperature reporting. Each possible notification has a unique Reason value:
Reason 0x00 = Temperature out of range
Cat
Rsn
Det
Ext
Meaning
Error Codes
05
00
Tag
Len
Value / Description
Typ
Req
Default
2
Category 0x00 Power / Reset contains notification detail codes involving the device’s power and reset functionality. Each possible notification has a unique Reason value:
Reason 0x00 = Device Reset Occurred
Reason 0x01 = Device Reset Will Occur Soon
Reason 0x02 = Low Battery
Reason 0x03 = Key Management
Reason 0x04 = Temperature
00
00
00
00
Power/Reset, Device Reset Occurred, Reserved, Reserved
The device sends and repeats this notification after the device power cycles or resets, depending on the setting in Device Reset Occurred Notification Control - Property 1.2.7.1.1.1. If it is set to repeat, it does so until the host acknowledges it using Property 1.2.7.1.1.2 Device Reset Occurred Notification Acknowledged.
These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table XXX.
00000000
00
01
0
00
Power/Reset, Device Reset Will Occur Soon, Reserved, Reserved
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 Device Reset Will Occur Soon Notification Control - Property 1.2.7.1.1.3.
See 24 Hour Automatic Reset PCI Requirement for more information.
These notifications always include the Notification Payload parameter in the Notification Message, which directly contains one byte indicating the number of minutes (0x01 to 0xFF) until the device will perform the reset.
0001000
00
02
00
00
Power/Reset, Battery, Low Battery Warning, Percent
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.
00020000
00
02
01
00
Power/Reset, Battery, Power Down Imminent, Reserved
The device sends this notification one minute before it automatically powers down the device because the battery charge has reached 0 percent.
00020100
00
02
2
00
Power/Reset, Battery, Battery Charge Complete, Reserved
The device sends this notification when the battery charger detects that the battery is fully charged.
0002200
00
03
00
00
Power/Reset, Device reset per Command 0x1F01.
The device sends this notification to notify the host when Device executes Reset Command 0x1F01.
00030000
Category 0x01 User Event contains notification detail codes involving events triggered by user actions. Each possible notification has a unique Reason value:
Reason 0x00 = Contactless Card Presented (EMV Contactless Only)
Reason 0x01 = Contactless Card Removed (EMV Contactless Only)
Reason 0x02 = Card Seated in Slot (EMV Contact Only)
Reason 0x03 = Card Unseated from Slot (EMV Contact Only)
Reason 0x04 = Card Swiped (MSR Only)
Reason 0x05 = Touch Sensor Press On Display (Touch Only)
Reason 0x06 = Touch Sensor Release On Display (Touch Only)
Reason 0x07 = Barcode Read (BCR Only)
The host can use User Event Notification Controls Enable - Property 1.2.7.1.2.1 to enable these notification reasons individually.
The host may choose to use these notifications to determine when to send additional commands. For example, it may send Start Transaction - Command 0x1001. 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.
01
00
00
00
User Event, Contactless Card Presented, EMV, Reserved (EMV Contactless Only)
01000000
01
01
00
00
User Event, Contactless Card Removed, EMV, Reserved (EMV Contactless Only)
01010000
01
00
01
00
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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000100
01
01
01
00
User Event, Contactless Card Removed, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only)
01010100
01
00
02
00
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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000200
01
01
02
00
User Event, Contactless Card Removed, MIFARE Classic, 1K (EMV Contactless Only)
01010200
01
00
03
00
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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000300
01
01
03
00
User Event, Contactless Card Removed, MIFARE Classic, 4K (EMV Contactless Only)
01010300
01
00
04
00
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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000400
01
01
04
00
User Event, Contactless Card Removed, MIFARE DESFire Light (EMV Contactless Only)
01010400
01
00
05
00
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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000500
01
01
05
00
User Event, Contactless Card Removed, MIFARE MINI® (EMV Contactless Only)
01010500
01
00
06
00
User Event, Contactless Card Presented, MIFARE Plus EV1 (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000600
01
01
06
00
User Event, Contactless Card Removed, MIFARE Plus EV1 (EMV Contactless Only)
01010600
01
00
07
00
User Event, Contactless Card Presented, MIFARE Plus EV2 (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000700
01
01
07
00
User Event, Contactless Card Removed, MIFARE Plus EV2 (EMV Contactless Only)
014010700
01
00
08
00
User Event, Contactless Card Presented, MIFARE Plus SE (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000800
01
01
08
00
User Event, Contactless Card Removed, MIFARE Plus SE (EMV Contactless Only)
01010800
01
00
09
00
User Event, Contactless Card Presented, MIFARE Plus X (EMV Contactless Only). The contactless reader has successfully read an NFC tag. In this case, the device includes UID data in the Notification Payload portion of the Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000900
01
01
09
00
User Event, Contactless Card Removed, MIFARE Plus X (EMV Contactless Only)
01010900
01
00
0A
00
User Event, Contactless Card Presented, MIFARE DESFire EV1 (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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000A00
01
01
0A
00
User Event, Contactless Card Removed, MIFARE DESFire EV1 (EMV Contactless Only)
01010A00
01
00
0B
00
User Event, Contactless Card Presented, MIFARE DESFire EV2 (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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000B00
01
01
0B
00
User Event, Contactless Card Removed, MIFARE DESFire EV2 (EMV Contactless Only)
01010B00
01
00
0C
00
User Event, Contactless Card Presented, MIFARE DESFire EV3 (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 Notification Message. UID Data is in the format described in Table XXX - Notification Payload for UID. A sample notification is shown here: Table XXX – Notification Payload for UID Example
01000C00
01
01
0C
00
User Event, Contactless Card Removed, MIFARE DESFire EV3 (EMV Contactless Only)
01010C00
01
02
00
00
User Event, Card Seated in Slot, Reserved, Reserved (EMV Contact Only)
01020000
01
03
00
00
User Event, Card Unseated from Slot, Reserved, Reserved (EMV Contact Only)
01030000
01
04
00
00
User Event, Card Swiped, Reserved, Reserved (MSR Only). When the host receives this notification, it should call Start Transaction - Command 0x1001 before the timeout configured in User Event Notification MSR Data Timeout (MSR Only) - Property 1.2.7.1.2.2 to process the MSR swipe data the device is temporarily storing in memory.
01040000
01
05
00
00
User Event, Touch Sensor Press On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table XXX.
01050000
01
06
00
00
User Event, Touch Sensor Release On Display, Reserved, Reserved (Touch Only). These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table XXX.
01060000
01
07
00
00
Type values:
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 XXX - Notification Payload for Personal Info Entry and Table XXX - Notification Payload for Personal Info Entry. Data that is not encrypted is in the format described in Table XXX.
01070000
Session Management, Session Expiring Soon, Reserved, Reserved
02
00
00
00
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 Extend Session - Command 0x1F03 or by sending any command request. These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table XXX.
02000000
Key management, CSR keys generated, Reserved, Reserved
03
00
00
00
This notification does not include a Notification Payload. See Generate CSR keys (WLAN Only) - Command 0xEF02 for more information.
03000000
03
01
00
00
Key management, Certificate Expiring Soon, Reserved, Reserved. See Certificate Expiring Soon Notification Threshold - Property 1.2.2.1.1.B for more information. These notifications always include the Notification Payload parameter in the Notification Message, as shown in Table XXX - Notification Payload for Key management, Certificate Expiring Soon.
03010000
Temperature, Out of Range, Low Warning, Temperature
04
00
00
00
The device sends this notification when the device’s temperature falls below the temperature set in Low Temperature Notification Level (1.2.7.1.4.1). The temperature reported is in Celsius.
04000000
04
00
01
00
Temperature, Out of Range, High Warning, Temperature. The device sends this notification when the device’s temperature rises above the temperature set in High Temperature Notification Level (1.2.7.1.4.2). The temperature reported is in Celsius.
04010100
01
01
Subscription Status, mDoc Subscription, Expiration, Warning
05000101
05
00
01
02
Subscription Status, mDoc Subscription, Expiration, Expired
05000102
Notification ID 0x1001
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
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)