Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Transaction notifications are the asynchronous messages a Dyna-family reader sends while a transaction is running, reporting progress, state changes, and completion. Use the table below to jump to a specific notification.
Applies to: All Dyna Family products
Click category to go specific commands
Notification Group
When it fires
During a transaction.
The device sends this notification when the battery charger detects that the battery is fully charged.
On progress and when states changes during interaction with the Banking Functions modules.
On progress and when states changes during a Pass-Through Mode.
When checking on or reporting the status of a firmware update.
During general state changes that occur within the device, outside the context of specific operations like transactions
During operations involving the User Interface
Notification Group
When it fires
During a transaction.
Upon completion of a transaction
Notification Group
When it fires
This notification reports information about progress and state changes involving the device’s Banking Functions modules.
This notification reports information about progress and state changes that occur during interaction with the Banking Functions modules.
Notification Group
When it fires
This notification reports information about progress and state changes that occur during a Pass-Through Mode.
Notification Group
When it fires
This notification reports the successful completion of firmware update operations the host initiated using Load Firmware File and Commit Firmware from File
This notification reports the failure of a Firmware Update command the host initiated using Load Firmware File and Commit Firmware from File.
This notification reports Firmware is up to date for host initiated Load Firmware File.
Notification Group
When it fires
This notification reports information about general state changes that occur within the device.
The device sends this notification when the battery charge reaches 15 percent.
The device sends this notification one minute before it automatically powers down the device.
Notification Group
When it fires
Requests that the host take action during operations involving the device’s User Interface modules.
Requests that the host take action during operations involving the device’s User Interface modules.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This notification reports the successful completion of firmware update operations the host initiated using Load Firmware File - Command 0xD801 and Commit Firmware from File - Command 0xD901. The Notification Detail for those two commands are shown in the table below.
This notification reports information about progress and state changes involving the device’s Banking Functions modules.
For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each, shown in Table - Notification Detail Codes, to indicate:
The Payment Technology (PT) involved
The
08
01
0A
03
Commit Firmware from File Complete, Success
08
01
09
03
Load Firmware File Complete, Success
Detail (Det) about the notification that has different meanings depending on the Reason, and
An Extra field (Ext) that has different meanings depending on the Reason.
Payment Technology 0x07 Manual Card Entry (MCE) contains transaction notification detail codes involving manual card entry (MCE Only).
Reason 0x01 = Card Event
Reason 0x08 = Data Update
Reason 0x10 = State Update
07
01
01
00
Manual Card Entry (MCE), Card Event, Data Entered, Reserved
Payment Technology 0x08 Magnetic Stripe Reader (MSR) contains transaction notification detail codes involving magnetic stripe cards (MSR Only).
Reason 0x01 = Card Event
Reason 0x08 = Data Update
Reason 0x10 = State Update
08
01
01
00
MSR, Card Event, Swiped, Reserved (MSR Only)
08
01
02
00
MSR, Card Event, Inserted, Reserved (MSR Only)
08
01
03
00
MSR, Card Event, Removed, Reserved (MSR Only)
08
01
04
00
MSR, Card Event, Detected, Reserved (MSR Only)
Payment Technology 0x10 EMV Contact contains transaction notification detail codes involving contact chip cards (EMV Contact Only).
Reason 0x01 = Card Event
Reason 0x08 = Data Update
Reason 0x10 = State Update
10
01
02
00
EMV Contact, Card Event, Inserted, Reserved (EMV Contact Only)
10
01
03
00
EMV Contact, Card Event, Removed, Reserved (EMV Contact Only)
10
01
04
00
EMV Contact, Card Event, Detected, Reserved (EMV Contact Only)
Payment Technology 0x20 EMV Contactless contains transaction notification detail codes involving contactless cards and contactless payment devices. (EMV Contactless Only)
Reason 0x01 = Card Event
Reason 0x08 = Data Update
Reason 0x10 = State Update
20
01
03
00
EMV Contactless, Card Event, Removed, Reserved (EMV Contactless Only)
20
01
04
00
EMV Contactless, Card Event, Detected, Reserved (EMV Contactless Only)
20
01
05
00
EMV Contactless, Card Event, Collision, Reserved (EMV Contactless Only)
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 Table - Notification Message Formatand Table - Battery Charged Notification Example.
AA 00 81 04 83 00 10 01 82 00 02 02 001001 = Device Information Update
81
04
Press / Release Coordinates 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 Custom Idle Page Image Device Locked (Display Only) - Property 1.2.3.1.1.2. 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.
B
R
End of Notification Message
1001 = Device Information Update
81
1
Interface 0x00 = WLAN
B
R
82
1
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 Maximum Client Connections - Property 1.2.2.1.1.A since there is only a single session for all clients. See **Command 0x1F03 - Extend Session (Session Management Only)**for more information on this scenario.
B
R
83
1
Expiration Time The time in minutes until the session expires.
B
R
xx
var
More data objects may be added in future firmware revisions.
End of Notification Message
1001 = Device Information Update
81
1
This parameter has the same length and value described by Certificate Expiring Soon Notification Threshold - Property 1.2.2.1.1.B.
B
R
82
1
This parameter contains the certificate identifier. See the certificate file type section (File Type 0x03) from Table 206 to identify this certificate by locating the certificate that has a File Subtype that matches this certificate identifier.
B
R
83
1
The number of days the certificate is still valid.
B
R
End of Notification Message
1001 = Device Information Update
84
var
NFC Payload
B
R
/DF79
var
NFC UID
B
R
End of Notification Message
Beginning of Notification Message
1001 = Device Information Update
81
var
This parameter has the same length and value described by Device Operational Status - Property 2.3.1.2.1.1.
B
R
82
var
This parameter has the same length and value described by Offline Status Detail - Property 2.3.1.2.1.2.
B
R
xx
var
More data objects may be added in future firmware revisions.
End of Notification Message
Beginning of Notification Message
Beginning of Notification Message
Beginning of Notification Message
Beginning of Notification Message
AA00 81 04 83001001 82 04 00000000 84 08 1001 81 01 02 82 01 00AA00 81 04 83001001 82 04 00000000 84 08 1001 81 04 00 80 00 80AA00 81 04 83001001 82 04 00000000 84 0B 1001 81 01 00 82 01 00 83 01 05AA 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 80This 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.
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.
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.
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.
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.
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.
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.
01
00
00
00
User Event, Contactless Card Presented, EMV, Reserved (EMV Contactless Only)
01
01
00
00
User Event, Contactless Card Removed, EMV, Reserved (EMV Contactless Only)
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
01
01
01
00
User Event, Contactless Card Removed, NTag/MIFARE Ultralite, Reserved (EMV Contactless Only)
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
01
01
02
00
User Event, Contactless Card Removed, MIFARE Classic, 1K (EMV Contactless Only)
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
01
01
03
00
User Event, Contactless Card Removed, MIFARE Classic, 4K (EMV Contactless Only)
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
01
01
04
00
User Event, Contactless Card Removed, MIFARE DESFire Light (EMV Contactless Only)
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
01
01
05
00
User Event, Contactless Card Removed, MIFARE MINI® (EMV Contactless Only)
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
01
01
06
00
User Event, Contactless Card Removed, MIFARE Plus EV1 (EMV Contactless Only)
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
01
01
07
00
User Event, Contactless Card Removed, MIFARE Plus EV2 (EMV Contactless Only)
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
01
01
08
00
User Event, Contactless Card Removed, MIFARE Plus SE (EMV Contactless Only)
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
01
01
09
00
User Event, Contactless Card Removed, MIFARE Plus X (EMV Contactless Only)
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
01
01
0A
00
User Event, Contactless Card Removed, MIFARE DESFire EV1 (EMV Contactless Only)
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
01
01
0B
00
User Event, Contactless Card Removed, MIFARE DESFire EV2 (EMV Contactless Only)
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
01
01
0C
00
User Event, Contactless Card Removed, MIFARE DESFire EV3 (EMV Contactless Only)
01
02
00
00
User Event, Card Seated in Slot, Reserved, Reserved (EMV Contact Only)
01
03
00
00
User Event, Card Unseated from Slot, Reserved, Reserved (EMV Contact Only)
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.
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.
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.
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
0 2
0 0
0 0
0 0
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.
0 3
0 0
0 0
0 0
This notification does not include a Notification Payload. See Generate CSR keys (WLAN Only) - Command 0xEF02 for more information.
0 3
0 1
0 0
0 0
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.
0 4
0 0
0 0
0 0
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.
0 4
0 0
0 1
0 0
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.
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
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.
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
Session Management, Session Expiring Soon, Reserved, Reserved
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
Key management, CSR keys generated, Reserved, Reserved
Category 0x04 Temperature contains notification detail codes involving temperature reporting. Each possible notification has a unique Reason value:
Reason 0x00 = Temperature out of range
Temperature, Out of Range, Low Warning, Temperature
This notification reports the failure of a Firmware Update command the host initiated using Load Firmware File - Command 0xD801 and Commit Firmware from File - Command 0xD901. The Notification Detail for those two commands are shown in the table below.
08
01
0A
04
Commit Firmware from File Complete, Failed
08
01
09
04
Load Firmware File Complete, Failed
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 Table 14 - Notification Message Formatand Table 338 Low Battery Shutdown Response Example.
AA 00 81 04 83 00 10 01 82 00 02 01 00This notification reports information about progress and state changes that occur during interaction with the Banking Functions modules.
For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each to indicate:
The User Interface Module (UI) involved
The Reason (Rsn) for the notification (UI Event)
Detail (Det) about the notification that has different meanings depending on the Reason, and
An Extra field (Ext) that has different meanings depending on the Reason.
01
02
01
01
(Banking Functions Only) Touchscreen, PIN Entry, Success, Data Attached — In this case, the device includes additional data defined in Table XXX, or in Table XXX if the device is including account data with PIN data.
01
02
02
01
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Timeout
01
02
02
02
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Hardware Not Available
01
02
02
03
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Canceled
01
02
02
04
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Error
01
02
02
05
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, PIN Verify Failed
01
02
02
06
(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Account Data Capture Failed
0205 = User Interface Operation Complete
84
var
Notification Payload
B
R
/F5
var
Container for Encrypted PIN Data
B
R
//DF71
01
PIN Block Format
0x00 = ISO Format 0
0x01 = ISO Format 1
0x03 = ISO Format 3
B
R
//99
var
Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes
B
R
//DFDF41
var
PIN Key Serial Number (KSN)
B
R
//DFDF42
01
PIN Encryption Type — See section 4.4 Encryption Type for a list of valid values.
B
R
End of Notification Message
0205 = 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 XXX.
B
R
/DFDF56
var
Encrypted Data KSN
B
R
/DFDF57
01
Encrypted Data Encryption Type — See Encryption Type for a list of valid values.
B
R
/F5
var
Container for Encrypted PIN Data
TC
R
//DF71
01
PIN Block Format
0x00 = ISO Format 0
0x01 = ISO Format 1
0x03 = ISO Format 3
B
R
//99
var
Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes
B
R
//DFDF41
var
PIN KSN
B
R
//DFDF42
01
PIN Encryption Type — See Encryption Type for a list of valid values.
B
R
End of Notification Message
/DF42
var
MSR Track 2 Clear Text Data
B
O
/57
var
Track 2 Equivalent Data
B
O
/5A
var
Primary Account Number
B
O
Padding to force DFDF59 plus padding to be a multiple of 8 bytes
Module 0x01 Touchscreen contains UI notification detail codes that are specific to the touchscreen module (Touch Only)
Reason 0x01 = Signature Capture
Reason 0x02 = PIN Entry (Banking Functions Only)
Beginning of Notification Message
Beginning of Notification Message
FC
var
Decrypted Data Container
T
R
0x04 = ISO Format 4
0x04 = ISO Format 4
This notification reports information about progress and state changes that occur during a transaction.
For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each, shown in Table 313, 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
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).
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).
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).
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).
30
08
00
02
Barcode Reader, Barcode Update, Type, Data Attached
Type 0x00 = Unknown
Type 0x01 = MagTek
Type 0x02 = EMV
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)
B
O
End 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
/DF74
var
Barcode Data
B
O
/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;
B
R
0x07
0x01
0x01
0x00
Manual Card Entry, Card Event, Data Entered, Reserved (MCE Only)
0x08
0x01
0x01
0x00
MSR, Card Event, Swiped, Reserved (MSR Only)
0x10
0x01
0x02
0x00
EMV Contact, Card Event, Inserted, Reserved (EMV Contact Only)
0x00
0x10
0x01
0x00
None, State Update, Transaction Started by Device, Legacy EMV Flow (Touch Only)
30
01
01
00
(BCR Only) Barcode Reader, Barcode Event, Read, Reserved
Beginning of Notification Message
Beginning of Notification Message
FC
var
Barcode Data Container
T
FC
var
VAS Error Container
T
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 00Payment 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.
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
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
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
Payment Technology 0x30 Barcode Reader contains transaction notification detail codes involving barcodes (BCR Only). Reason: 0x01 = Barcode Event.
R
R
(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
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).
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 Table 14 - Notification Message Format and Table 337 Low Battery Notification Example.
Charge the device using a USB power source soon after receiving this notification.
AA 00 81 04 83 00 10 01 82 00 02 00 0D01
09
03
Load Firmware File Complete, Complete
This sections of the DynaFamily Programmer's Manual details notifications that come from generic pass-through mode.
Applies to: All Dyna Family products
Notification
When it fires
This notification reports information about progress and state changes that occur during a Pass-Through Mode.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email:
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This sections of the DynaFamily Programmer's Manual details notifications that come from firmware updates
Applies to: All Dyna Family products
Notification
When it fires
This notification reports the successful completion of firmware update operations the host initiated using Load Firmware File and Commit Firmware from File
This notification reports the failure of a Firmware Update command the host initiated using Load Firmware File and Commit Firmware from File.
This notification reports Firmware is up to date for host initiated Load Firmware File.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This notification reports the final result of a transaction the host initiated using Command 0x1001 - Start Transaction.
For this notification, the Notification Detail described in section 3.2.2.3 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
00
01
00
00
None, Timeout/No Cards Detected, Transaction Timed Out, Reserved
00
03
01
00
None, Transaction Terminated, Transaction Canceled by Host, Reserved
00
03
02
00
None, Transaction Terminated, Transaction Canceled by User, Reserved (Display Only)
07
03
05
00
MCE, Transaction Terminated, Transaction Canceled due to entry error, Reserved (MCE Only)
07
04
00
00
MCE, Transaction Completed, Reserved, Reserved (MCE Only)
08
03
05
00
MSR, Transaction Terminated, Transaction Canceled Due To Card Read Error, Reserved (MSR Only)
08
02
06
00
MSR, Outcome, Approved, Reserved (MSR Only)
08
02
06
01
MSR, Outcome, Approved, Signature Capture Requested (MSR Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
08
02
06
05
MSR, Outcome, Approved, Signature Capture Success (MSR Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
08
02
06
06
MSR, Outcome, Approved, Signature Capture Fail (MSR Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
08
02
07
00
MSR, Outcome, Quick Chip Deferred, Reserved (MSR Only)
08
02
07
01
MSR, Outcome, Quick Chip Deferred, Signature Capture Requested (MSR Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
08
02
07
05
MSR, Outcome, Quick Chip Deferred, Signature Capture Success (MSR Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
08
02
07
06
MSR, Outcome, Quick Chip Deferred, Signature Capture Fail (MSR Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
08
02
80
00
MSR, Outcome, Declined, Reserved (MSR Only)
08
02
80
01
MSR, Outcome, Declined, Signature Capture Requested (MSR Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
08
02
80
05
MSR, Outcome, Declined, Signature Capture Success (MSR Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
08
02
80
06
MSR, Outcome, Declined, Signature Capture Fail (MSR Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
10
02
08
03
ICC, Kernel Outcome, Failed, MSR Fallback (EMV Contact Only)
10
02
09
03
ICC, Kernel Outcome, Empty Candidate List, MSR Fallback (EMV Contact Only)
10
02
00
00
ICC, Kernel Outcome, None, Reserved (EMV Contact Only)
10
02
00
02
ICC, Kernel Outcome, None, Technical Fallback (EMV Contact Only)
10
02
0F
02
ICC, Kernel Outcome, End Application, Technical Fallback (EMV Contact Only)
10
02
01
00
ICC, Kernel Outcome, Try Another Interface, Reserved (EMV Contact Only)
10
02
01
03
ICC, Kernel Outcome, Try Another Interface, MSR Fallback (EMV Contact Only) Device Driven Fallback must be disabled and MSR channel is enabled
10
02
02
00
ICC, Kernel Outcome, Offline Approved, Reserved (EMV Contact Only)
10
02
02
01
ICC, Kernel Outcome, Offline Approved, Signature Capture Requested (EMV Contact Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
10
02
02
05
ICC, Kernel Outcome, Offline Approved, Signature Capture Success (EMV Contact Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
10
02
02
06
ICC, Kernel Outcome, Offline Approved, Signature Capture Fail (EMV Contact Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
10
02
03
00
ICC, Kernel Outcome, Offline Declined, Reserved (EMV Contact Only)
10
02
04
00
ICC, Kernel Outcome, Offline Failed, Reserved (EMV Contact Only)
10
02
05
00
ICC, Kernel Outcome, Offline Not Accepted, Reserved (EMV Contact Only)
10
02
06
00
ICC, Kernel Outcome, Approved, Reserved (EMV Contact Only)
10
02
06
01
ICC, Kernel Outcome, Approved, Signature Capture Requested (EMV Contact Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
10
02
06
05
ICC, Kernel Outcome, Approved, Signature Capture Success (EMV Contact Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
10
02
06
06
ICC, Kernel Outcome, Approved, Signature Capture Fail (EMV Contact Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
10
02
07
00
ICC, Kernel Outcome, Quick Chip Deferred, Reserved (EMV Contact Only)
10
02
07
01
ICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Requested (EMV Contact Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
10
02
07
05
ICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Success (EMV Contact Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
10
02
07
06
ICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Failed (EMV Contact Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
10
02
08
00
ICC, Kernel Outcome, Failed, Reserved (EMV Contact Only)
10
02
09
00
ICC, Kernel Outcome, Not Accepted, Reserved (EMV Contact Only)
10
02
0A
00
ICC, Kernel Outcome, Transaction Canceled, Reserved (EMV Contact Only)
10
02
0B
00
ICC, Kernel Outcome, Select Next Not Accepted, Reserved (EMV Contact Only)
10
02
0C
00
ICC, Kernel Outcome, Select Next Retry, Reserved (EMV Contact Only)
10
02
0D
00
ICC, Kernel Outcome, Try Again, Reserved (EMV Contact Only)
10
02
0E
00
ICC, Kernel Outcome, Online Request, Reserved (EMV Contact Only)
10
02
0F
00
ICC, Kernel Outcome, End Application, Reserved (EMV Contact Only)
10
02
10
00
ICC, Kernel Outcome, Not EMV Card Pooled, Reserved (EMV Contact Only)
10
02
80
00
ICC, Kernel Outcome, Declined, Reserved (EMV Contact Only)
10
02
80
01
ICC, Kernel Outcome, Declined, Signature Capture Requested (EMV Contact Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
10
02
80
05
ICC, Kernel Outcome, Declined, Signature Capture Success (EMV Contact Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
10
02
80
06
ICC, Kernel Outcome, Declined, Signature Capture Failed (EMV Contact Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
10
04
07
00
ICC, Transaction Completed, Declined, Reserved (EMV Contact Only)
20
02
00
00
PICC, Kernel Outcome, None, Reserved (EMV Contactless Only)
20
02
01
00
PICC, Kernel Outcome, Try Another Interface, Reserved (EMV Contactless Only)
20
02
02
00
PICC, Kernel Outcome, Offline Approved, Reserved (EMV Contactless Only)
20
02
02
01
PICC, Kernel Outcome, Offline Approved, Signature Capture Requested (EMV Contactless Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
20
02
02
05
PICC, Kernel Outcome, Offline Approved, Signature Capture Success (EMV Contactless Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
20
02
02
06
PICC, Kernel Outcome, Offline Approved, Signature Capture Fail (EMV Contactless Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
20
02
03
00
PICC, Kernel Outcome, Offline Declined, Reserved (EMV Contactless Only)
20
02
04
00
PICC, Kernel Outcome, Offline Failed, Reserved (EMV Contactless Only)
20
02
05
00
PICC, Kernel Outcome, Offline Not Accepted, Reserved (EMV Contactless Only)
20
02
06
00
PICC, Kernel Outcome, Approved, Reserved (EMV Contactless Only)
20
02
06
01
PICC, Kernel Outcome, Approved, Signature Capture Requested (EMV Contactless Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
20
02
06
05
PICC, Kernel Outcome, Approved, Signature Capture Success (EMV Contactless Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
20
02
06
06
PICC, Kernel Outcome, Approved, Signature Capture Fail (EMV Contactless Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
20
02
07
00
PICC, Kernel Outcome, Quick Chip Deferred, Reserved (EMV Contactless Only)
20
02
07
01
PICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Requested (EMV Contactless Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
20
02
07
05
PICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Success (EMV Contactless Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
20
02
07
06
PICC, Kernel Outcome, Quick Chip Deferred, Signature Capture Failed (EMV Contactless Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
20
02
08
00
PICC, Kernel Outcome, Failed, Reserved (EMV Contactless Only)
20
02
09
00
PICC, Kernel Outcome, Not Accepted, Reserved (EMV Contactless Only)
20
02
0A
00
PICC, Kernel Outcome, Transaction Canceled, Reserved (EMV Contactless Only)
20
02
0B
00
PICC, Kernel Outcome, Select Next Not Accepted, Reserved (EMV Contactless Only)
20
02
0C
00
PICC, Kernel Outcome, Select Next Retry, Reserved (EMV Contactless Only)
20
02
0D
00
PICC, Kernel Outcome, Try Again, Reserved (EMV Contactless Only)
20
02
0E
00
PICC, Kernel Outcome, Online Request, Reserved (EMV Contactless Only)
20
02
0F
00
PICC, Kernel Outcome, End Application, Reserved (EMV Contactless Only)
20
02
10
00
PICC, Kernel Outcome, Not EMV Card Pooled, Reserved (EMV Contactless Only)
20
02
80
00
PICC, Kernel Outcome, Declined, Reserved (EMV Contactless Only)
20
02
80
01
PICC, Kernel Outcome, Declined, Signature Capture Requested (EMV Contactless Only) If the device includes a touchscreen, the host should respond by sending Command 0x1801 - Request Cardholder Signature (Touch Only).
20
02
80
05
PICC, Kernel Outcome, Declined, Signature Capture Success (EMV Contactless Only) The device includes signature data inside EMV Batch Data Type tag DFDF3E.
20
02
80
06
PICC, Kernel Outcome, Declined, Signature Capture Failed (EMV Contactless Only) The host may send Command 0x1801 - Request Cardholder Signature (Touch Only) to retry capturing a signature.
20
04
07
00
PICC, Transaction Completed, Declined, Reserved (EMV Contactless Only)
20
05
00
00
PICC, NFC TAG, Tag Removed, Reserved (EMV Contactless Only)
Payment Technology 0x00 None contains transaction notification detail codes that are not specific to a particular payment technology.
0x00 = Reserved
0x01 = Timeout/No Cards Detected
0x02 = Kernel Outcome
0x03 = Transaction Terminated
0x04 = Transaction Completed
Payment Technology 0x07 Manual Card Entry contains transaction notification detail codes involving manual card entry (MCE Only).
0x00 = Reserved
0x01 = Timeout/No Cards Detected
0x02 = Kernel Outcome
0x03 = Transaction Terminated
0x04 = Transaction Completed
Payment Technology 0x08 Magnetic Stripe Reader (MSR) contains transaction notification detail codes involving magnetic stripe cards (MSR Only).
0x00 = Reserved
0x01 = Timeout/No Cards Detected
0x02 = Kernel Outcome
0x03 = Transaction Terminated
0x04 = Transaction Completed
Payment Technology 0x10 EMV Contact (“ICC”) contains transaction notification detail codes involving contact chip cards (EMV Contact Only).
0x00 = Reserved
0x01 = Timeout, no cards detected
0x02 = Kernel Outcome
0x03 = Transaction Terminated
0x04 = Transaction Completed
Payment Technology 0x20 EMV Contactless (“PICC”) contains transaction notification detail codes involving contactless cards and contactless payment devices (EMV Contactless Only).
0x00 = Reserved
0x01 = Timeout, no cards detected
0x02 = Kernel Outcome
0x03 = Transaction Terminated
0x04 = Transaction Completed
AA 00 81 04 83 00 01 05 82 04 20 00 00 00This notification requests that the host take action during operations involving the device’s User Interface modules.
For this notification, Notification Detail described in Notification Message contains one byte each, shown in Table XXX, to indicate:
The User Interface Module (UI) involved
The Reason (Rsn) for the notification (UI Event)
Detail (Det) about the notification that has different meanings depending on the Reason, and
An Extra field (Ext) that has different meanings depending on the Reason.
This notification reports information about progress and state changes that occur during a Pass-Through Mode.
For this notification, Notification Detail described in section Notification Messages contains one byte each, shown in Table - Notification Detail Codes, 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, and
An Extra field (Ext) that has different meanings depending on the Reason.
20
01
04
11
Contactless, Card Event, Detected, ISO 14443 Type B (Contactless Only)
20
01
04
12
Contactless, Card Event, Detected, Not Supported (Contactless Only)
20
01
05
00
Contactless, Card Event, Collision, Reserved (EMV Contactless Only)
20
08
04
02
Contactless, Data Update, NFC UID data, Data Attached
In this case, the device includes additional data, defined in Table 8 - Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached, in the Notification Payload portion of the Notification Message. (Contactless Only)
0101 = DynaPro Format Transaction Data
0301 = Generic Pass-Through 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. (MCE Only) If the notification is for manual card entry, the data blob does not contain Track 3 Data or MagnePrint Data. EMV Batch Data Type data blob, if the notification is a Batch Data notification. (MCE Only) If the notification is for manual card entry, the data blob does not contain Track 3 Data or MagnePrint Data. 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) – MIFARE Card Data Type reports the data reading from NFC/MIFARE tag (EMV Contactless Only)
B
O
End of any wrappers, at minimum including Response Message
PT
Rsn
Det
Ext
Meaning
20
01
04
10
Tag
Len
Value / Description
Typ
Req
Default
Beginning of Notification Message
Payment Technology 0x20 EMV Contactless contains transaction notification detail codes involving contactless cards and contactless payment devices.
Reason 0x01 = Card Event
Reason 0x02 = Online PIN Event
Reason 0x08 = Data Update
Reason 0x10 = State Update
Contactless, Card Event, Detected, ISO 14443 Type A (Contactless Only)
01
02
02
00
Touchscreen, Functional button Middle selected
01
02
03
00
Touchscreen, Functional button Right selected
01
03
01
00
Touchscreen, Text string button 1 selected
01
03
02
00
Touchscreen, Text string button 2 selected
01
03
03
00
Touchscreen, Text string button 3 selected
01
03
04
00
Touchscreen, Text string button 4 selected
01
03
05
00
Touchscreen, Text string button 5 selected
01
03
06
00
Touchscreen, Text string button 6 selected
01
04
00
00
Touchscreen, $Amount button selected, Data Attached contain the amount selected as described in Table - Notification Payload for $ Amount button selected, Data Attached
01
05
00
00
Touchscreen, Present card functional button Right selected
02
01
01
00
Display, Display Message, Data Attached, No Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
This notification is for simple messages. The host should show the requested message until another notification arrives or until the host needs to use the display for its own purposes. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like CARD READ OK - REMOVE CARD , THANK YOU , and WELCOME .
02
01
02
00
Display, Display Message, Data Attached, Include Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
The host should show the requested message and should allow the request to be canceled by a cardholder or operator. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like “TAP, INSERT, or SWIPE CARD,” where cancelation is appropriate. If the cancel button involves canceling the whole transaction, the host should send Command 0x1008 - Cancel Transaction.
02
02
00
00
Display, Cardholder Selection, Data Attached, Reserved
In this case, the notification includes additional data and display control, defined in
Table - Notification Payload for Cardholder Selection Notifications (No Display Only), in the Notification Payload portion of the Notification Message.
The host should show the requested selection, then send Command 0x1802 - Report Cardholder Selection to device to return the cardholder’s selection to the device.
02
03
00
00
(MAGTEK INTERNAL ONLY FOR NOW, No Display Only)
Display, Online PIN Request, Application ID / Amount, Data Attached, Reserved.
In this case, the notification includes additional data, defined in Table 354, in the
Notification Payload portion of the Notification Message.
The host must send Command TBD to the device to indicate PIN Capture data and result.
1803 = Notification 0x1803 - User Interface Host Action Request
/81
01
Reserved for time functions. 0x00
B
R
/82
01
Append or Clear Display
· 0x00 = Append the message(s) on the next available row.
· 0x01 = Clear the display first and display the requested message on the first row.
B
R
/83
var
Message
This parameter is a set of one or more ASCII strings the host should show, with each string terminated by any one of the following characters. MagTek recommends proceeding to the next row on receiving any of these characters:
· Null (0x00)
· LF (0x0A)
· The end of the Message parameter.
B
R
/85
var
Enhanced Application Select Message
For Contactless, this parameter will return the PPSE response starting from tag BF0C
BF0C <LEN><VALUE>
For Contact, this parameter will return all available AID returned from the PSE or List Of AIDs, from tag 70
70 <len>
61 <len>
4F<len><value of AID> 50<len><value of Application Label>
87<len><value of Application Priority Indicator> 61 <len>
B
O
End of Notification Message
1803 = Command 0x1803 - Display Message (Display Only)
84
9
Amount selected payload
B
R
/9F02
6
Dollar and cents amount selected in BCD format
B
R
End of Notification Message
1803 = Notification 0x1803 - User Interface Host Action Request
/81
01
Time in seconds the device will wait for host to respond with
Command 0x1802 - Report Cardholder Selection.
B
R
/82
01
Append or Clear Display
· 0x00 = Append, display the messages on the next line.
· 0x01 = Clear, clear the display first and display the requested message on the first line.
B
R
/83
var
Message
This parameter is a set of one or more ASCII strings the host should show, with each string terminated by any one of the following characters. MagTek recommends proceeding to the next row on receiving any of these characters:
· Null (0x00)
· LF (0x0A)
· The end of the Message parameter.
B
R
End of Notification Message
UI
Rsn
Det
Ext
Meaning
UI
Rsn
Det
Ext
Meaning
01
02
01
00
UI
Rsn
Det
Ext
Meaning
02
01
00
00
Tag
Len
Value / Description
Typ
Req
Default
Beginning of Notification Message
Tag
Len
Value / Description
Typ
Req
Default
Beginning of Notification Message .
Tag
Len
Value / Description
Typ
Req
Default
Beginning of Notification Message
Module 0x00 Miscellaneous contains UI notification detail codes that are not specific to a particular UI module.
Module 0x01 Touchscreen contains UI notification detail codes that are specific to the touchscreen module (Touch Only).
Reason 0x01 = Signature Capture
Reason 0x02 = Functional button selected
Reason 0x03 = Button text string selected
Reason 0x04 = Button $Amount selected
Reason 0x05 = Present card functional button Right is selected
Module 0x02 Display contains UI notification detail codes that are specific to the display module. The device primarily uses these notifications to request that the host stand in as a display to interact with cardholders / operators when the device does not have a display of its own or the display is configured with Property 1.2.3.1.2.3 Send UI notifications along with showing message on the display.
Reason 0x01 = Display Message Request
Reason 0x02 = Cardholder Selection Request
Reason 0x03 = Online PIN Request (MAGTEK INTERNAL ONLY FOR NOW
Touchscreen, Functional button Left selected
Display, Display Message, No Data Attached, Clear Display.
The host should clear any existing messages it is currently displaying.
The0x01nn Transaction Update notifications report progress and state changes that occur during a transaction. Its Notification Detail carries a Payment Technology (PT), a Reason (Rsn), and Detail (Det) and Extra (Ext) fields whose meaning depends on the reason.
87<len><value of Application Priority Indicator, optional>
If the GPO Response returns a Notification 0x0101 - Transaction Information Update of’69 85’, the response will be sent first by the device and this Enhanced Application Select Message will be sent again.
Notification
When it fires
During a transaction.
Applies to: All Dyna Family products
Upon completion of a transaction
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email:
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This sections of the DynaFamily Programmer's Manual details notifications that come from the device itself
Applies to: All Dyna Family products
Notification
When it fires
This notification reports information about general state changes that occur within the device.
The device sends this notification when the battery charge reaches 15 percent.
The device sends this notification one minute before it automatically powers down the device.
The device sends this notification when the battery charger detects that the battery is fully charged.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This sections of the DynaFamily Programmer's Manual details notifications that come from the device's user interface.
Applies to: All Dyna Family products
Notification
When it fires
This notification requests that the host take action during operations involving the device’s User Interface modules.
This notification requests that the host take action during operations involving the device’s User Interface modules.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
This notification requests that the host take action during operations involving the device’s User Interface modules.
For this notification, Notification Detail described in Notification Message contains one byte each, shown in Table XXX, to indicate:
The User Interface Module (UI) involved
The Reason (Rsn) for the notification (UI Event)
Detail (Det) about the notification that has different meanings depending on the Reason, and
An Extra field (Ext) that has different meanings depending on the Reason.
This notification requests that the host take action during operations involving the device’s User Interface modules.
For this notification, Notification Detail described in Notification Message contains one byte each, shown in Table 350, to indicate:
The User Interface Module (UI) involved
The Reason (Rsn) for the notification (UI Event)
Detail (Det) about the notification that has different meanings depending on the Reason, and
01
02
02
00
Touchscreen, Functional button Middle selected
01
02
03
00
Touchscreen, Functional button Right selected
01
03
01
00
Touchscreen, Text string button 1 selected
01
03
02
00
Touchscreen, Text string button 2 selected
01
03
03
00
Touchscreen, Text string button 3 selected
01
03
04
00
Touchscreen, Text string button 4 selected
01
03
05
00
Touchscreen, Text string button 5 selected
01
03
06
00
Touchscreen, Text string button 6 selected
01
04
00
00
Touchscreen, $Amount button selected, Data Attached contain the amount selected as described in Table - Notification Payload for $ Amount button selected, Data Attached
01
05
00
00
Touchscreen, Present card functional button Right selected
02
01
01
00
Display, Display Message, Data Attached, No Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
This notification is for simple messages. The host should show the requested message until another notification arrives or until the host needs to use the display for its own purposes. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like CARD READ OK - REMOVE CARD , THANK YOU , and WELCOME .
02
01
02
00
Display, Display Message, Data Attached, Include Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
The host should show the requested message and should allow the request to be canceled by a cardholder or operator. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like “TAP, INSERT, or SWIPE CARD,” where cancelation is appropriate. If the cancel button involves canceling the whole transaction, the host should send Command 0x1008 - Cancel Transaction.
02
02
00
00
Display, Cardholder Selection, Data Attached, Reserved
In this case, the notification includes additional data and display control, defined in
Table - Notification Payload for Cardholder Selection Notifications (No Display Only), in the Notification Payload portion of the Notification Message.
The host should show the requested selection, then send Command 0x1802 - Report Cardholder Selection to device to return the cardholder’s selection to the device.
04
03
01
01
Barcode Reader, Read Barcode Result, Success, MagTek Blob Type
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. MagTek Blob data is always encrypted. The data is in the format described in Table XXX.
04
03
01
02
Barcode Reader, Read Barcode Result, Success, EMV Type
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. EMV barcode data is always encrypted. The data is in the format described in Table XXX.
04
03
02
01
Barcode Reader, Read Barcode Result, Operation Failed, Timeout
05
04
02
00
Buzzer, Buzzer Result, Operation Fail, Reserve
06
05
02
01
Card Emulation, Card Emulation Result, Operation Fail, Timeout
06
05
02
03
Card Emulation, Card Emulation Result, Operation Fail, Cancel
06
05
02
04
Card Emulation, Card Emulation Result, Operation Fail, Error
07
06
01
01
LED Result, LED 1 Operation, Fail
07
06
02
03
LED Result, LED 2 Operation, Success
07
06
02
01
LED Result, LED 2 Operation, Fail
07
06
03
00
LED Result, LED 3 Operation, Success
07
06
03
01
LED Result, LED 3 Operation, Fail
07
06
04
00
LED Result, LED 4 Operation, Success
07
06
04
01
LED Result, LED 4 Operation, Fail
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 7.4‑6.
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
R
/DF74
var
Barcode Data
B
O
0x0003
“Please Select”
0x0004
“Touch Screen To Continue”
0x0005
“Cancel”
0x0006
“Select a Transaction”
0x0007
“Deposit”
0x0008
“Withdrawal”
0x0009
“Choose PIN”
0x000A
“Change PIN”
0x000B
“Balance”
0x000C
“Cash Advance”
0x000D
“Authenticate Me”
0x000E
“Transfer”
0x000F
“Make Payment”
0x0010
“On Sale”
0x0011
“Discount”
0x0012
“Clearance”
0x0013
“$5.00 /5 Mins.”
0x0014
“$6.00 /7 Mins.”
0x0015
“$7.00 /9 Mins.”
0x0016
“$8.00 /15 Mins.”
0x0017
“Call Attendant”
0x0018
“Print Receipt”
0x0019
“Email Receipt”
0x001A
“Text Receipt”
0x001B
“Please Select An Amount”
0x001C
“Please Select A Tip Amount”
0x001D
“Menu Selection 1”
0x001E
“Menu Selection 2”
0x001F
“Menu Selection 3”
0x0020
“Menu Selection 4”
0x0021
“Service Request”
0x0022
“Show More”
0x0023
“Options”
0x0024
“What is the issue?”
0x0025
“Exit”
0x0026
“No Hot Water”
0x0027
“Doesn't Spin”
0x0028
“Water Leakage”
0x0029
“No Heat”
0x002A
“Please select a Machine”
0x002B
“Pump 1”
0x002C
“Pump 2”
0x002D
“Pump 3”
0x002E
“Pump 4”
0x002F
“A1”
0x0030
“A2”
0x0031
“A3”
0x0032
“A4”
0x0033
“B1”
0x0034
“B2”
0x0035
“B3”
0x0036
“B4”
0x0037
“C1”
0x0038
“C2”
0x0039
“C3”
0x003A
“C4”
0x003B
“$5.50 – Cake”
0x003C
“$5.00 – Muffin”
0x003D
“$6.50 – Croissant”
0x003E
“$4.50 – Danish”
0x003F
“Req. QR Code”
0x0040
“Scan QR Code”
0x0041
“Scan NFC”
0x0042
“Call Server”
0x0043
“Request Bill”
0x0044
“Approve”
0x0045
“Reject”
0x0046
“Verify SMS”
0x0047
“Verify Email”
0x0048
“English”
0x0049
“Spanish”
0x0080
“Hola”
0x0081
“Por Favor Seleccione”
0x0082
“Toca Para Continuar”
0x0083
“Cancelar”
0x0084
“Seleccione Una Transaccion”
0x0085
“Deposito”
0x0086
“Retiro”
0x0087
“Elija PIN”
0x0088
“Cambiar PIN”
0x0089
“Adelanto En Efectivo”
0x008A
“Autenticarme”
0x008B
“Verificar SMS”
0x008C
“Confirmar”
0x008D
“Mostrar Mas”
0x008E
“Opciones”
0x008F
“Salida”
0x0090
“Transferir”
0x0091
“Realizar Pago”
0x0092
“En Venta”
0x0093
“Descuento”
0x0094
“Autorizacion”
0x0095
“Operador De Llamada”
0x0096
“Imprimir Recibo”
0x0097
“Correo Electronico”
0x0098
“Recibo De Texto”
0x0099
“Seleccione Una Cantidad”
0x009A
“Anadir Un Consejo”
0x009B
“Requerido Codigo QR”
0x009C
“Escanear Codigo QR”
0x009D
“Escanear NFC”
0x009E
“Servidor De Llamadas”
0x009F
“Solicitar Factura”
0x00A0
“Aprobar”
0x00A1
“Rechazar”
0x00A2
“Gracias”
0x00A3
“Ingles”
0x00A4
“Espanol”
01
02
02
00
Touchscreen, Functional button Middle selected
01
02
03
00
Touchscreen, Functional button Right selected
01
03
01
00
Touchscreen, Text string button 1 selected
01
03
02
00
Touchscreen, Text string button 2 selected
01
03
03
00
Touchscreen, Text string button 3 selected
01
03
04
00
Touchscreen, Text string button 4 selected
01
03
05
00
Touchscreen, Text string button 5 selected
01
03
06
00
Touchscreen, Text string button 6 selected
01
04
00
00
Touchscreen, $Amount button selected, Data Attached contain the amount selected as described in Table - Notification Payload for $ Amount button selected, Data Attached
01
05
00
00
Touchscreen, Present card functional button Right selected
02
01
01
00
Display, Display Message, Data Attached, No Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
This notification is for simple messages. The host should show the requested message until another notification arrives or until the host needs to use the display for its own purposes. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like CARD READ OK - REMOVE CARD , THANK YOU , and WELCOME .
02
01
02
00
Display, Display Message, Data Attached, Include Cancel Function
In this case, the notification includes additional data and display control, defined in Table - Notification Payload for Display Message Request Notifications, in the Notification Payload portion of the Notification Message.
The host should show the requested message and should allow the request to be canceled by a cardholder or operator. For example, during a transaction, this notification will pass along the simple messages in the transaction sequence like “TAP, INSERT, or SWIPE CARD,” where cancelation is appropriate. If the cancel button involves canceling the whole transaction, the host should send Command 0x1008 - Cancel Transaction.
02
02
00
00
Display, Cardholder Selection, Data Attached, Reserved
In this case, the notification includes additional data and display control, defined in
Table - Notification Payload for Cardholder Selection Notifications (No Display Only), in the Notification Payload portion of the Notification Message.
The host should show the requested selection, then send Command 0x1802 - Report Cardholder Selection to device to return the cardholder’s selection to the device.
02
03
00
00
(MAGTEK INTERNAL ONLY FOR NOW, No Display Only)
Display, Online PIN Request, Application ID / Amount, Data Attached, Reserved.
In this case, the notification includes additional data, defined in Table 354, in the
Notification Payload portion of the Notification Message.
The host must send Command TBD to the device to indicate PIN Capture data and result.
04
03
01
01
Barcode Reader, Read Barcode Result, Success, MagTek Blob Type
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. MagTek Blob data is always encrypted. The data is in the format described in Table 7.4‑5.
04
03
01
02
Barcode Reader, Read Barcode Result, Success, EMV Type
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. EMV barcode data is always encrypted. The data is in the format described in Table 7.4‑5.
04
03
02
01
Barcode Reader, Read Barcode Result, Operation Failed, Timeout
05
04
02
00
Buzzer, Buzzer Result, Operation Fail, Reserve
06
05
02
01
Card Emulation, Card Emulation Result, Operation Fail, Timeout
06
05
02
03
Card Emulation, Card Emulation Result, Operation Fail, Cancel
06
05
02
04
Card Emulation, Card Emulation Result, Operation Fail, Error
07
06
01
01
LED Result, LED 1 Operation, Fail
07
06
02
00
LED Result, LED 2 Operation, Success
07
06
02
01
LED Result, LED 2 Operation, Fail
07
06
03
00
LED Result, LED 3 Operation, Success
07
06
03
01
LED Result, LED 3 Operation, Fail
07
06
04
00
LED Result, LED 4 Operation, Success
07
06
04
01
LED Result, LED 4 Operation, Fail
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 XXX.
B
R
/DFDF50
var
Encrypted Data KSN
B
R
/DFDF51
01
Encrypted Data Encryption Type
See Encryption Type for a list of valid values.
B
R
End of Notification Message
R
/DF74
var
Barcode Data
B
O
0x0003
“Please Select”
0x0004
“Touch Screen To Continue”
0x0005
“Cancel”
0x0006
“Select a Transaction”
0x0007
“Deposit”
0x0008
“Withdrawal”
0x0009
“Choose PIN”
0x000A
“Change PIN”
0x000B
“Balance”
0x000C
“Cash Advance”
0x000D
“Authenticate Me”
0x000E
“Transfer”
0x000F
“Make Payment”
0x0010
“On Sale”
0x0011
“Discount”
0x0012
“Clearance”
0x0013
“$5.00 /5 Mins.”
0x0014
“$6.00 /7 Mins.”
0x0015
“$7.00 /9 Mins.”
0x0016
“$8.00 /15 Mins.”
0x0017
“Call Attendant”
0x0018
“Print Receipt”
0x0019
“Email Receipt”
0x001A
“Text Receipt”
0x001B
“Please Select An Amount”
0x001C
“Please Select A Tip Amount”
0x001D
“Menu Selection 1”
0x001E
“Menu Selection 2”
0x001F
“Menu Selection 3”
0x0020
“Menu Selection 4”
0x0021
“Service Request”
0x0022
“Show More”
0x0023
“Options”
0x0024
“What is the issue?”
0x0025
“Exit”
0x0026
“No Hot Water”
0x0027
“Doesn't Spin”
0x0028
“Water Leakage”
0x0029
“No Heat”
0x002A
“Please select a Machine”
0x002B
“Pump 1”
0x002C
“Pump 2”
0x002D
“Pump 3”
0x002E
“Pump 4”
0x002F
“A1”
0x0030
“A2”
0x0031
“A3”
0x0032
“A4”
0x0033
“B1”
0x0034
“B2”
0x0035
“B3”
0x0036
“B4”
0x0037
“C1”
0x0038
“C2”
0x0039
“C3”
0x003A
“C4”
0x003B
“$5.50 – Cake”
0x003C
“$5.00 – Muffin”
0x003D
“$6.50 – Croissant”
0x003E
“$4.50 – Danish”
0x003F
“Req. QR Code”
0x0040
“Scan QR Code”
0x0041
“Scan NFC”
0x0042
“Call Server”
0x0043
“Request Bill”
0x0044
“Approve”
0x0045
“Reject”
0x0046
“Verify SMS”
0x0047
“Verify Email”
0x0048
“English”
0x0049
“Spanish”
0x0080
“Hola”
0x0081
“Por Favor Seleccione”
0x0082
“Toca Para Continuar”
0x0083
“Cancelar”
0x0084
“Seleccione Una Transaccion”
0x0085
“Deposito”
0x0086
“Retiro”
0x0087
“Elija PIN”
0x0088
“Cambiar PIN”
0x0089
“Adelanto En Efectivo”
0x008A
“Autenticarme”
0x008B
“Verificar SMS”
0x008C
“Confirmar”
0x008D
“Mostrar Mas”
0x008E
“Opciones”
0x008F
“Salida”
0x0090
“Transferir”
0x0091
“Realizar Pago”
0x0092
“En Venta”
0x0093
“Descuento”
0x0094
“Autorizacion”
0x0095
“Operador De Llamada”
0x0096
“Imprimir Recibo”
0x0097
“Correo Electronico”
0x0098
“Recibo De Texto”
0x0099
“Seleccione Una Cantidad”
0x009A
“Anadir Un Consejo”
0x009B
“Requerido Codigo QR”
0x009C
“Escanear Codigo QR”
0x009D
“Escanear NFC”
0x009E
“Servidor De Llamadas”
0x009F
“Solicitar Factura”
0x00A0
“Aprobar”
0x00A1
“Rechazar”
0x00A2
“Gracias”
0x00A3
“Ingles”
0x00A4
“Espanol”
O
Beginning of Notification Message
1803 = Notification 0x1803 - User Interface Host Action Request
/9F06
var
This contains the AID (Tag) if Tag 9F12 is not provided by the card.
B
O
/9F02
06
This contains the Amount (Tag 9F02) if it should be displayed. For example, the device excludes this when using a provisional amount for a Quick Chip transaction.
B
O
End of Notification Message
UI
Rsn
Det
Ext
Meaning
UI
Rsn
Det
Ext
Meaning
01
02
01
00
UI
Rsn
Det
Ext
Meaning
02
01
00
00
UI
Rsn
Det
Ext
Meaning
04
03
01
00
UI
Rsn
Det
Ext
Meaning
05
04
01
00
UI
Rsn
Det
Ext
Meaning
06
05
01
00
UI
Rsn
Det
Ext
Meaning
07
06
01
00
Tag
Len
Value/Description
Typ
Req
Default
Beginning of Notification Message
Tag
Len
Value / Description
Typ
Req
Default
FC
var
Barcode Data Container
Display String ID
Display String
0x0000
“ ”
0x0001
“Thank You”
0x0002
“Hello”
UI
Rsn
Det
Ext
Meaning
UI
Rsn
Det
Ext
Meaning
01
02
01
00
UI
Rsn
Det
Ext
Meaning
02
01
00
00
UI
Rsn
Det
Ext
Meaning
04
03
01
00
UI
Rsn
Det
Ext
Meaning
05
04
01
00
UI
Rsn
Det
Ext
Meaning
06
05
01
00
UI
Rsn
Det
Ext
Meaning
07
06
01
00
Tag
Len
Value/Description
Typ
Req
Default
Beginning of Notification Message
Tag
Len
Value / Description
Typ
Req
Default
FC
var
Barcode Data Container
Display String ID
Display String
0x0000
“ ”
0x0001
“Thank You”
0x0002
“Hello”
Tag
Len
Value / Description
Typ
Req
Default
/9F12
var
This contains AID Preferred Name (Tag 9F12) if it is provided by the card.
Module 0x00 Miscellaneous contains UI notification detail codes that are not specific to a particular UI module.
Module 0x01 Touchscreen contains UI notification detail codes that are specific to the touchscreen module (Touch Only).
Reason 0x01 = Signature Capture
Reason 0x02 = Functional button selected
Reason 0x03 = Button text string selected
Reason 0x04 = Button $Amount selected
Reason 0x05 = Present card functional button Right is selected
Module 0x02 Display contains UI notification detail codes that are specific to the display module. The device primarily uses these notifications to request that the host stand in as a display to interact with cardholders / operators when the device does not have a display of its own or the display is configured with Property 1.2.3.1.2.3 Send UI notifications along with showing message on the display.
Reason 0x01 = Display Message Request
Reason 0x02 = Cardholder Selection Request
Module 0x04 Barcode Reader contains notification detail codes that are specific to the barcode reader module.
Reason 0x03 = Read Barcode Result
Module 0x05 Buzzer contains notification detail codes that are specific to the buzzer module.
Reason 0x04 = Buzzer Result
Module 0x06 Card Emulation contains notification detail codes that are specific to card emulation.
Reason 0x05 = Card Emulation Result
Module 0x07 LED contains notification detail codes that are specific to the LED module. • Reason 0x06 = LED Result
String ID value can be from 0x0000 to 0x012B, and String length maximum is 30 characters. This default configured Strings can be changed and uploaded to the device
Module 0x00 Miscellaneous contains UI notification detail codes that are not specific to a particular UI module.
Module 0x01 Touchscreen contains UI notification detail codes that are specific to the touchscreen module (Touch Only).
Reason 0x01 = Signature Capture
Reason 0x02 = Functional button selected
Reason 0x03 = Button text string selected
Reason 0x04 = Button $Amount selected
Reason 0x05 = Present card functional button Right is selected
Module 0x02 Display contains UI notification detail codes that are specific to the display module. The device primarily uses these notifications to request that the host stand in as a display to interact with cardholders / operators when the device does not have a display of its own or the display is configured with Property 1.2.3.1.2.3 Send UI notifications along with showing message on the display.
Reason 0x01 = Display Message Request
Reason 0x02 = Cardholder Selection Request
Reason 0x03 = Online PIN Request (MAGTEK INTERNAL ONLY FOR NOW
Module 0x04 Barcode Reader contains notification detail codes that are specific to the barcode reader module.
Reason 0x03 = Read Barcode Result
Module 0x05 Buzzer contains notification detail codes that are specific to the buzzer module.
Reason 0x04 = Buzzer Result
Module 0x06 Card Emulation contains notification detail codes that are specific to card emulation.
Reason 0x05 = Card Emulation Result
Module 0x07 LED contains notification detail codes that are specific to the LED module. • Reason 0x06 = LED Result
String ID value can be from 0x0000 to 0x012B, and String length maximum is 30 characters. This default configured Strings can be changed and uploaded to the device
Touchscreen, Functional button Left selected
Display, Display Message, No Data Attached, Clear Display.
The host should clear any existing messages it is currently displaying.
Barcode Reader, Read Barcode Result, Success, Unidentified Type
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. Data that is not encrypted is in the format described in Table XXX.
Buzzer, Buzzer Result, Operation Success, Reserve
Card Emulation, Card Emulation Result, Operation Success, Reserve
LED Result, LED 1 Operation, Success
T
Touchscreen, Functional button Left selected
Display, Display Message, No Data Attached, Clear Display.
The host should clear any existing messages it is currently displaying.
Barcode Reader, Read Barcode Result, Success, Unidentified Type
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.
Buzzer, Buzzer Result, Operation Success, Reserve
Card Emulation, Card Emulation Result, Operation Success, Reserve
LED Result, LED 1 Operation, Success
T
B
This sections of the DynaFamily Programmer's Manual details notifications that come strictly from external banking sources.
Applies to: All DynaFamily products
Notification
When it fires
This notification reports information about progress and state changes involving the device’s Banking Functions modules.
This notification reports information about progress and state changes that occur during interaction with the Banking Functions modules.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!