Page 1
DynaFlex II Go Secure Card Reader Programmer’s Manual (COMMANDS) April 2024 Document Number: D998200597-102 REGISTERED TO ISO 9001:2015 MagTek I 1710 Apollo Court I Seal Beach, CA 90740 I Phone: (562) 546-6400 I Technical Support: (562) 546-6800 www.magtek.com...
Page 2
Printed in the United States of America INFORMATION IN THIS PUBLICATION IS SUBJECT TO CHANGE WITHOUT NOTICE. MAGTEK CANNOT BE HELD LIABLE FOR ANY USE OF THE CONTENTS OF THIS DOCUMENT. ANY CHANGES OR IMPROVEMENTS MADE TO THIS PRODUCT WILL BE INCLUDED IN THE NEXT PUBLICATION RELEASE.
Page 3
02 00 in Table 7.3-1 - Notification Detail Codes ; updated Table 7.3-1 - Notification Detail Codes to distinguish 1K or 4K Mifare Classic cards; Add DynaFlex II Go on page 1; Add October 10, 2023 NFC pass through commands Command 0x1100 – Pass Through Commands for NFC Tag Type 2 ;...
Page 4
5% or less in Property 1.2.7.1.2.1 User Event Notification Controls Enable; Changed Property 1.2.2.3.1.C Bluetooth LE Sleep Enabled default to enabled, made it customer facing and added DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 4 of 301 (D998200597-102)
Page 5
Message; Remove default setting: -mt.test from CN (Subject) and DNS (Subject Alternate Names), Update Table 6.6-1 - File Types Add: Request file from MagTek services Set: No DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 5 of 301 (D998200597-102)
Page 9
Property 1.1.2.2.1.3 PAN Number of Leading Unmasked Characters ....199 8.2.2.3 Property 1.1.2.2.1.4 PAN Number of Trailing Unmasked Characters ....200 8.2.2.4 Property 1.1.2.2.1.5 PAN MOD 10 Check Digit Correction ........201 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 9 of 301 (D998200597-102)
Page 10
Property 1.2.7.1.1.1 Device Reset Occurred Notification Control ....... 231 8.3.5.2 Property 1.2.7.1.1.2 Device Reset Occurred Notification Acknowledged ..232 8.3.5.3 Property 1.2.7.1.1.3 Device Reset Will Occur Soon Notification Control ... 233 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 10 of 301 (D998200597-102)
Page 11
Property 2.1.2.3.5.3 Mastercard MCL Kernel Checksum (Contactless Only) ..262 8.4.3.13 Property 2.1.2.3.6.1 Visa payWave Kernel ID (Contactless Only) ......263 8.4.3.14 Property 2.1.2.3.6.2 Visa payWave Kernel Firmware Part Number (Contactless Only) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 11 of 301 (D998200597-102)
Page 12
Load CAPK with AID: 0000000000 to erase all current CAPK keys with this CAPK key: Empty Amex DRL: Load AMEX DRL file with “EMPTY” content ..........290 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 12 of 301 (D998200597-102)
Page 13
Empty Entry Point: Load Entry file with “EMPTY” content and 1 delimiter (FF35) ..... 293 Appendix D Physical Button (DynaFlex Only) ..................294 Appendix E Warranty, Standards, and Certifications ................295 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 13 of 301 (D998200597-102)
Introduction About This Document This document describes how to communicate with Secure Card Reader Authenticator (SCRA) devices which implement MagTek Messaging Schema (MMS) and the DynaFlex II Go system architecture. The document uses bold face to: • Highlight terms / concepts being formally defined in the current sentence / paragraph •...
The combination of device(s), host(s), host software, device firmware, device configuration settings, physical mounting and environment, user experience, and documentation is referred to as the solution. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 15 of 301 (D998200597-102)
MagTek has also developed sample software that demonstrates direct communication with the device, which software developers can use to test the device and which provides a starting point for developing other software. For more information, see the MagTek web site, or contact your reseller or MagTek Support Services.
DynaFlex II with USB Only DynaFlex II PED with USB Only WLAN DynaFlex II PED w/WLAN DynaFlex II Go with USB Only GATT DynaFlex II Go w/Bluetooth LE DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 17 of 301 (D998200597-102)
When connecting via USB, MMS devices connect to the USB host as a vendor-defined Human Interface Device. MMS devices identify themselves to the host with MagTek’s vendor ID 0x0801. DynaFlex products report as Product ID (PID) 0x2020, DynaProx products report as Product ID (PID) 0x2023 and DynaFlex II Go report as Product ID (PID) 0x2024.
Packet Number, and to truncate the padding based on Message Length or Remaining Message Length. 7) Parse the final response message using the Response table in the documentation for the command. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 21 of 301 (D998200597-102)
Page 22
Table 2.1-5 - Multi-Packet Cancel Format Byte Offset Field Name Field Value Packet Type 0x04 = Multi-Packet Cancel 1..2 Reason for Cancel 0x0000 = General 3..63 Padding 0x00 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 22 of 301 (D998200597-102)
4) Determine the message type and message ID and parse it according to the corresponding Response table or Notification table in section 3. 5) Route the fully composed message to the appropriate handler. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 23 of 301 (D998200597-102)
So host applications should be written with appropriate error detection and handling to account for these potential drops. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 24 of 301 (D998200597-102)
Page 26
7) If the message counter advances by more than one between two messages, assume a message has been dropped. The device should ignore this situation. The host can ignore this situation too or implement error handling of its choice. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 26 of 301 (D998200597-102)
3.2 Message Format. For information about transmitting and receiving messages using specific connection types, which involves following connection-specific rules for breaking messages down into transmittable Message Streams, see section 2 Connection Types. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 27 of 301 (D998200597-102)
For example, FF is a single byte with all bits set to 1, not the two-byte string literal “FF.” DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 28 of 301 (D998200597-102)
Value 00, 000000 = OK / Done, General / All Good / Requested operation was successful • 84, 07, DF018103010203 o Tag 84 = Response Message Parameter 4 for Response Payload o Length 07 o Value DF018103010203 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 29 of 301 (D998200597-102)
In tables that show TLV data objects, a Length of var means the length is variable, and the device or host must calculate it based on whatever is nested inside the TLV data object. See Table 3.2-1 below for an example. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 30 of 301 (D998200597-102)
Page 31
“slice apart” the contents of 84 into separate values. //null This is another byte contained by 84. //null This is another byte contained by 84. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 31 of 301 (D998200597-102)
(lower) versions: • 0x00 = Pre-production development (limited breaking changes). At minimum, every device MagTek ever produces using the MMS framework will accept this value. • 0x01 = First Production release (no breaking changes) •...
(lower) versions: • 0x00 = Pre-production development (limited breaking changes). At minimum, every device MagTek ever produces using the MMS framework will accept this value. • 0x01 = First Production release (no breaking changes) •...
Page 34
EMV tag. See the Command definition in section 6 Commands for command-specific Additional Details. Response Payload As documented in the message’s Response table in section 6 Commands. Reserved DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 34 of 301 (D998200597-102)
(lower) versions: • 0x00 = Pre-production development (limited breaking changes). At minimum, every device MagTek ever produces using the MMS framework will accept this value. • 0x01 = First Production release (no breaking changes) •...
(lower) versions: • 0x00 = Pre-production development (limited breaking changes). At minimum, every device MagTek ever produces using the MMS framework will accept this value. • 0x01 = First Production release (no breaking changes) •...
• is the Cardholder Name. Manually entered data uses string literal CARDHOLDER NAME/ MANUAL ENTRY/ • The string of s is the Expiration Date (YYMM). DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 42 of 301 (D998200597-102)
Page 43
0 or a 1. This Field Option tells what data is included in the track data, where 0 = Acct, Date, CVV and 1 = Name on Card, Acct, Date, CVV. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 43 of 301 (D998200597-102)
0x01 = Magnetic Stripe ISO/ABA Financial (MSR) ///DFDF52 01 • 0x02 = Magnetic Stripe AAMVA (MSR) • 0x03 = Manual Entry • 0x04 = Unknown DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 47 of 301 (D998200597-102)
Page 48
DFDF59 itself is formatted like Table 4.5-2 after the host decrypts it. Table 4.5-2 - EMV ARQC (DynaPro Format) DFDF59 Decrypted Contents Value / Description Typ Req Default Decrypted Data Container DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 48 of 301 (D998200597-102)
Page 49
0x80 = UI Request on Outcome Present 0x40 = UI Request on Restart Present 0x20 = Data Record Present 0x10 = Discretionary Data Present 0x08 = Provide Receipt DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 49 of 301 (D998200597-102)
Page 50
0 = Standard MagnePrint o 1 = Extended MagnePrint • Bits 4 through 15 = ASIC Revision • Bit 16 = Reserved • Bit 17 = Reserved DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 50 of 301 (D998200597-102)
Page 51
//DFDF51 See section 4.4 Encryption Type for a list of valid values. Padding to force DFDF59 plus padding to be a multiple of 8 bytes DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 51 of 301 (D998200597-102)
Specifications for Payment Systems 4.3. The host may ///72 include as many instances of this parameter as needed, up to a maximum length of 128 bytes including Tags and Lengths. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 52 of 301 (D998200597-102)
For payWave, see Visa Contact Specifications v2.2. • For Expresspay, see Expresspay Terminal Specification v4.0.x. • For D-PAS, see Discover Contactless D-PAS: Terminal Application Specifications, v1.0. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 53 of 301 (D998200597-102)
Number of padding bytes added to DFDF59 value to force length to a multiple of 8 bytes Merchant Data ///F7 This contains an instance of Merchant Data Container. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 54 of 301 (D998200597-102)
Page 55
Four byte CBC-MAC. The host should calculate the CBC-MAC and verify that it matches. For details about calculating a CBC-MAC, see About Message Authentication Codes (MAC). DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 55 of 301 (D998200597-102)
Page 56
0x80 = UI Request on Outcome Present 0x40 = UI Request on Restart Present 0x20 = Data Record Present 0x10 = Discretionary Data Present 0x08 = Provide Receipt DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 56 of 301 (D998200597-102)
Page 57
Data and Magneprint are using the same KSN. MagnePrint Status Data (MSR Only) //DFDF43 Only included for MSR swipe transactions and when Track Data and Magneprint are using the same KSN. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 57 of 301 (D998200597-102)
Table 4.7-3 - Merchant Data Container Description Source Format Length Masked Track 1 Status (MSR Only) • DFDF30 0x00 = OK Device • 0x01 = Empty DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 58 of 301 (D998200597-102)
Page 59
Indicates the results of the last CVM 9F34 Device performed 5F57 Account Type Device 5F34 PAN Sequence Number Card DFDF4D Masked ICC Track 2 Data Card 30..38 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 59 of 301 (D998200597-102)
Page 60
4 - Data Types and Shared TLV Data Objects DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 60 of 301 (D998200597-102)
EMV Entry Point Configuration File Type the host loads into the device. MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet for more convenient authoring, review, and change tracking. For a reference sample spreadsheet that contains EMVCo approved configurations, contact MagTek Support Services.
Processing Table Slot 1, the contents of the second are loaded into Processing Table Slot 2, etc. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 62 of 301 (D998200597-102)
Page 63
/DF15 Only applies when Payment Brand Identifier indicates Contact. TAC default 00 00 00 /DF20 Only applies when Payment Brand Identifier indicates 00 00 Contact. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 63 of 301 (D998200597-102)
Page 64
Only applies when Payment Brand Identifier indicates Contact. Additional instances of the AID Delimiter Container parameter, one per Application Identifier (AID) the device should support. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 64 of 301 (D998200597-102)
Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 65 of 301 (D998200597-102)
Page 66
Magnetic Stripe Default UDOL This value only applies when the Kernel Configuration //DF1A 9F 6A 04 parameter is set to support MSD. The device ignores this value. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 66 of 301 (D998200597-102)
Page 67
Bit 6 = Signature • Bit 5 = Enciphered Offline PIN • Bit 4 = No CVM • Bits 3..1 = Reserved for future use DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 67 of 301 (D998200597-102)
Page 68
00 18 Resistance R-APDU (100 of micro seconds) Relay Resistance Accuracy Threshold (100 of micro //DF36 01 2C seconds) Relay Resistance Transmission Time Mismatch Threshold //DF37 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 68 of 301 (D998200597-102)
//9F6D 01 = Expresspay 2.0 and Expresspay >= 3.x (MSD) • 11 = Expresspay >= 3.x(MSD) Bits 6..1 = 0 (Reserved, not to be configured) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 71 of 301 (D998200597-102)
Page 72
//DF27 Timeout, Field off request (100 of ms) //DF2D Message Hold Time (100 of ms) 00 00 0F DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 72 of 301 (D998200597-102)
Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 73 of 301 (D998200597-102)
Page 74
Bits 3..1 = Reserved for future use Status Zero Amount Allowed Flag • //DF32 0x01 = Option 1, Online Cryptogram Request • 0x02 = Option 2, Not Allowed DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 74 of 301 (D998200597-102)
Command 0xD812 - Start Send File to Device (Unsecured). MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet in xlsx format for more convenient authoring, review, and change tracking. For a reference sample spreadsheet, contact MagTek Support Services.
Command 0xD812 - Start Send File to Device (Unsecured). See the Expresspay 4.0.2 specification for functional details. MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet in xlsx format for more convenient authoring, review, and change tracking. For a reference sample spreadsheet, contact MagTek Support Services.
0x02 = Command Authorization Using Signature • 0x03 = Command Authorization Using MAC • 0x05 = Data Authentication Using MAC • 0x07 = Data Encryption • 0x10 = Data Signature DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 77 of 301 (D998200597-102)
Page 78
If Operation Type is an Encryption type: • 0x01 = DEA • 0x02 = 2TDEA • 0x03 = 3TDEA • 0x04 = AES-128 • 0x05 = AES-192 • 0x06 = AES-256 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 78 of 301 (D998200597-102)
Page 80
If Operation Type is a MAC type, this specifies the data to be MACed must be padded to a multiple of this many bytes. For all other Operation Types, do not include this byte. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 80 of 301 (D998200597-102)
Reserved for future use. Do not include. 4.16 NFC UID Type (EMV Contactless Only) Table 4.16-1 – NFC UID Type Value / Description Typ Req Default DF79 var NFC UID DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 81 of 301 (D998200597-102)
Usage column. Look up the desired Key Type in Table 4.17-2 below Algorithm and select this value from the Algorithm column. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 82 of 301 (D998200597-102)
Page 83
Owner Tag ‘MGTK’ Avoid collision with others using Block ID ‘21’ 8..9 Data Tag ‘10’ Field ID 10..11 Data Len ‘01’ Field Length (ASCII Hex 00-FF) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 83 of 301 (D998200597-102)
Page 84
Transport TR31-F 10xx Transport Keys (KBPK) agreement process from 1000 TMPTK Temporary KBPK Command 0xF017 - Establish Ephemeral KBPK 1001 Master Transport Key TMPTK K1AD DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 84 of 301 (D998200597-102)
4 - Data Types and Shared TLV Data Objects 4.17.1.1.1 DUKPT Slot IDs The existing TR31 Module supports 32 MagTek DUKPT Slot IDs, from 0x2000 to 0x201F. The Key Injection Software Tool shall inject DUKPT keys through these DUKPT Slot IDs. 4.17.1.1.2 Transformation IDs This is the list of DUKPT transformations defined in both the Legacy and AES specifications.
200702: Map MAC to DKPTM7-2007 MAC Generate/Verify Variant. d) 20030B: Map MangePrint to DKPTM3-2003 Data Encryption Usage. e) 000004: MagTek Token is RFU, 0000 ID does not exist (this is default value). f) 000004: User Data is RFU, 0000 ID does not exist (this is default value).
- Start Get File from Device. After fetching the CSR, the keys used to generate the CSR will still exist in non-volatile memory associated with a CSR and can be used to generate a new CSR if needed. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 89 of 301 (D998200597-102)
The device can use two different types of keys: Triple Data Encryption Standard (TDES) DUKPT Keys and AES DUKPT Keys. The Key Serial Number (KSN) format is slightly different depending on which DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 90 of 301 (D998200597-102)
Device Serial Number, and a 3 bit Initial Key Load Counter the injecting host increments each time the same key is re-loaded into the device. In these cases, the key can be referenced by an 8-digit MagTek part number (“key ID”) consisting of the 7 hex digit Key Set ID plus a trailing “0.”...
2) Optionally send Command 0x1F01 - Reset Device instead of waiting for the automatic reset to occur. 3) Re-connect with the device and re-start any operation that was in process. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 92 of 301 (D998200597-102)
The host should respond by showing the prompt, receiving input from the cardholder, and calling Command 0x1802 - Report Cardholder Selection (No Touch Only) to report the selection result to the device. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 93 of 301 (D998200597-102)
Page 94
Stripe Reader, the host should check the contents of the Card Type tag DFDF52 in the EMV ARQC Type from the notification. Per payment brand fallback rules: DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 94 of 301 (D998200597-102)
Page 95
Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached (3) No ARQC or BATCH data will be sent (4) The host application can continue interfacing with the NFC tag by sending pass-through commands DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 95 of 301 (D998200597-102)
Page 97
• Bit 0 Transaction Flow o Value 1 = Quick Chip Transaction Flow o Value 0 = EMV Transaction Flow • Bit 1 Response Format DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 97 of 301 (D998200597-102)
Page 98
“WELCOME.” The host can include this parameter to direct the device to suppress the “THANK YOU” message during this transaction. Override Final Transaction Message null DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 98 of 301 (D998200597-102)
End of any wrappers, at minimum including Response Message found on page 33 Table 6.1-12 - Request Example Example (Hex) AA 00 81 04 01 13 10 08 84 02 10 08 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 101 of 301 (D998200597-102)
The GET_VERSION command is used to retrieve information on the NTAG family, the product version, storage size and other product data Get Version required to identify the specific NTAG21x. Byte 0 = 0x60 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 102 of 301 (D998200597-102)
Page 103
Note: This command is sent in 2 steps, which the Firmware will handle (1) <CMD><Address to Write><CRCH><CRCL> (2) <16 Bytes of Data to Write><CRCH><CRCL> DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 103 of 301 (D998200597-102)
Page 104
1100 = Command 0x1100 – Pass Through Commands for NFC Tag Type 2 Command For NFC Tag Tag Response Code 0x00 = Success 0x01 = Failed DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 104 of 301 (D998200597-102)
End of Notification Message found on page 39 Table 6.2-7 – Unencrypted NFC Data Value / Description Typ Req Default NFC Data Container /DF7A NFC Data DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 105 of 301 (D998200597-102)
Byte 4 – Key Type 0 = A, 1 = B Byte 5 to 10 = 6 Byte Key Byte 11 to x = Variable length Byte Data (16 bytes per block) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 106 of 301 (D998200597-102)
Page 107
If encrypted, see Table 6.2-6 - Payload for Encrypted NFC Data If unencrypted see Table 6.2-7 – Unencrypted NFC Data End of any wrappers, at minimum including Response Message found on page 33 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 107 of 301 (D998200597-102)
End of any wrappers, at minimum including Request Message found on page 32 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 108 of 301 (D998200597-102)
The sequence of events is as follows: 1) The host has already invoked Command 0x1001 - Start Transaction and the transaction is still in process. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 109 of 301 (D998200597-102)
Page 110
Table 6.3-3 - Request Example Example (Hex) AA 00 81 04 01 00 18 02 84 08 18 02 81 01 00 82 01 00 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 110 of 301 (D998200597-102)
0x00 = Infinite. The device leaves the barcode reader 0x00 enabled until it reads a barcode, or until the host sends this command again to disable the barcode reader. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 111 of 301 (D998200597-102)
Notification 0x1805 - User Interface Operation Complete to report Buzzer/Buzzer Result. The host should wait for Notification 0x1805 - User Interface Operation Complete before sending another command. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 112 of 301 (D998200597-102)
Apply changes to the Bluetooth LE interface Apply changes to the UART interface End of any wrappers, at minimum including Request Message found on page 32 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 115 of 301 (D998200597-102)
Page 116
End of any wrappers, at minimum including Response Message found on page 33 Table 6.4-7 - Request Example Example (Hex) AA00 810401551F02 8402 1F02 Table 6.4-8 - Response Example Example (Hex) AA00 810482551F02 820400000000 8402 1F02 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 116 of 301 (D998200597-102)
This document refers to these data elements collectively as Properties. The list of all properties and their corresponding OIDs and other characteristics is provided in section 8 Configuration. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 118 of 301 (D998200597-102)
Page 119
2B 06 01 This value is the root of the “long form” of the Property OID, 04 01 F6 and is the same for all MagTek devices. Leave this parameter empty and use the default. Device Family ID This value is the second portion of the “long form” of the Property OID, and is the same for all similar MagTek devices within the same product family.
Page 120
This contains the Property OID Tree Prefix the host included in the request message. If this parameter is not included in the request, the response does not include it. var Property OID Remainder DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 120 of 301 (D998200597-102)
Page 121
Get Property 1.2.7.1.1.1 Device Reset Occurred Notification Control using longer Property OID Remainder: AA00 8104 0155D101 8411 D101 8501 01 890A E208 E706 E104 E102 C100 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 121 of 301 (D998200597-102)
6.5.2 Command 0xD111 - Set Property Properties are stored in flash memory, which inherently has a limited number of read- write cycles before it begins to wear. For this reason, MagTek recommends setting properties as few times as possible over the lifecycle of the device.
Page 124
This contains the Company ID the host included in the request message. If this parameter is not included in the request, the response does not include it. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 124 of 301 (D998200597-102)
File Payload fields in “raw” form (e.g. certificates and images) with metadata coming from the command request and response. Other file types require the addition of MagTek metadata included inside the File Payload blob; these are documented in the “File Type” subsections of section 4 Data Types and Shared TLV Data Objects.
Page 127
Reserved for future use. Set: No EMV configuration, Discover update Get: No 0x00 0x00 0x09 0x00 conditions. Reserved for future use. Set: No DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 127 of 301 (D998200597-102)
6 - Commands 6.6.2 Command 0xD801 - Load Firmware File The host uses this command to send a firmware image file, signed by MagTek, to the device as the first step in updating firmware. The sequence of events is as follows: 1) The host is assumed to have access to a binary file containing a firmware image signed by MagTek.
Page 129
Plus 0C7628 bytes of firmware Payload, excluded here for brevity. Table 6.6-5 - Response Example Example (Hex) AA 00 81 04 82 01 D8 01 82 04 00 00 00 00 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 129 of 301 (D998200597-102)
D811 = Command 0xD811 - Start Send File to Device (Secured) File ID from Table 6.6-1 - File Types var File transfer properties var Length of File Payload DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 130 of 301 (D998200597-102)
Page 131
If the request started successfully, the Request Status in the message wrapper is OK, Started / Running, All good / requested operation was successful. Note: For additional support, please contact MagTek Support. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 131 of 301 (D998200597-102)
File transfer properties Length of File Payload This is the length of the File Payload parameter in the Data File Message the host sends to the device. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 132 of 301 (D998200597-102)
Page 133
If the request started successfully, the Request Status in the message wrapper is OK, Started / Running, All good / requested operation was successful. Note: For additional support, please contact MagTek Support. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 133 of 301 (D998200597-102)
The host uses this command to request a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data). In many cases, the files retrieved by this command have been sent by a host previously using Command 0xD811 - Start Send File to Device (Secured) or Command 0xD812 - Start Send File to Device (Unsecured).
Page 135
End of any wrappers, at minimum including Response Message found on page 33 If the request started successfully, the Request Status in the message wrapper is OK, Done. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 135 of 301 (D998200597-102)
The host uses this command to request the file information of a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data). In many cases, the file information retrieved by this command have been sent by a host previously using Command 0xD811 - Start Send File to Device (Secured) or Command 0xD812 - Start Send File to Device (Unsecured).
Page 137
7C D1 D9 15 11 08 A3 1D 81 0B 54 45 53 54 5F 31 4B 2E 62 69 6E 82 05 4C 61 62 65 6C 83 07 31 2E 30 2E 30 2E 31 Note: For additional support, please contact MagTek Support. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 137 of 301 (D998200597-102)
End of any wrappers, at minimum including Response Message found on page 33 If the request started successfully, the Request Status in the message wrapper is OK, Started / Running, All good / requested operation was successful. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 138 of 301 (D998200597-102)
Value / Description Typ Req Default Beginning of any wrappers, at minimum including Response Message found on page 33 DF01 = Command 0xDF01 - Echo DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 139 of 301 (D998200597-102)
Beginning of any wrappers, at minimum including Request Message found on page 32 E001 = Command 0xE001 - Get Challenge Request ID to be protected DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 140 of 301 (D998200597-102)
When the time expires, the device will no longer accept the Challenge Token and the host will have to retrieve another one. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 141 of 301 (D998200597-102)
Page 142
Message Payload. See the documentation for that command to determine the format of the response. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 142 of 301 (D998200597-102)
Page 143
30 33 33 33 30 33 30 87 01 01 9E 10 7D E4 27 C8 A0 70 72 08 19 0A 1E 0A 3F 48 BB F1 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 143 of 301 (D998200597-102)
EF01 = Command 0xEF01 - Load Key Using TR-31 Key Block This is a populated, secured TR-31 Key Block Type. End of any wrappers, at minimum including Request Message found on page 32 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 144 of 301 (D998200597-102)
Table 6.9-12 - Request Data for Command 0xEF11 - Get Key Info Value / Description Typ Req Default Beginning of any wrappers, at minimum including Request Message found on page 32 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 145 of 301 (D998200597-102)
Page 146
0x05 = AES192 • 0x06 = AES256 Key Check Value • For AES-CMAC, 5 bytes. • For TDES-CMAC or TDES-CBCMAC, 3 bytes var Key Derivation Information DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 146 of 301 (D998200597-102)
Build the Security Parameters Type portion of the wrapper with: i) Security Operation Type populated with the following values: (1) Operation Type = Command Authorization Using Signature (2) Operation Algorithm = ECDSA (indeterministic) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 147 of 301 (D998200597-102)
Page 148
TEMP KBPK if the device is power cycled or reset, and the host would need to restart the process with a new TEMP KBPK. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 148 of 301 (D998200597-102)
Page 149
Table 6.10-3 - Request Example Example (Hex) AA 00 81 04 01 10 F0 17 84 82 01 8C EE EE // Secure Wrapper A1 24 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 149 of 301 (D998200597-102)
Page 150
03 31 0F 8A 28 C0 DB 1A B7 1B 51 B3 E6 BD FF 50 77 CA 02 42 01 EE D8 2D 9F A3 D1 98 4E 74 C8 85 11 52 93 15 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 150 of 301 (D998200597-102)
Page 151
84 08 4C 4A EC 0B 47 E4 53 EB // TLV of 8-byte random # for TEMP-KBPK Note: For additional support, please contact MagTek Support. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 151 of 301 (D998200597-102)
08 08 In this case, the device includes additional data, defined in Table 7.1-2, in the Notification Payload portion of the Notification Message (MSR Only). DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 152 of 301 (D998200597-102)
Page 154
In this case, the device includes additional data, defined in Table 7.1-2, in the Notification Payload portion of the Notification Message. Table 7.1-2 - Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 154 of 301 (D998200597-102)
Page 155
Table 7.1-4 - Notification Payload for Barcode Reader, Barcode Event, Type, Data Attached (Unencrypted Data) Value / Description Typ Req Default Barcode Data Container /DF74 Barcode Data DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 155 of 301 (D998200597-102)
Notification Detail for those two commands are shown in the table below. Table 7.2-2 - Notification Detail Codes B1 B2 B3 B4 Meaning 08 01 04 Commit Firmware from File Complete, Failed DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 161 of 301 (D998200597-102)
The other optional message parameters in the Notification Message depend on which combination of four bytes is included in Notification Detail, and are described in Table 7.3-1. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 163 of 301 (D998200597-102)
Page 164
0 percent. Power/Reset, Battery, Battery Charge Complete, Reserved The device sends this notification when the battery charger detects that the battery is fully charged. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 164 of 301 (D998200597-102)
Page 165
A sample notification is shown here: Table 7.3-5 – Notification Payload for UID Example User Event, Contactless Card Removed, NFC/Mifare Ultralite, Reserved (EMV Contactless Only) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 165 of 301 (D998200597-102)
Page 166
Start Transaction before the timeout configured in Property 1.2.7.1.2.2 User Event Notification MSR Data Timeout (MSR Only) to process the MSR swipe data the device is temporarily storing in memory. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 166 of 301 (D998200597-102)
Page 167
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. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 167 of 301 (D998200597-102)
For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each, shown in Table 7.4-1, to indicate: • The User Interface Module (UI) involved DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 168 of 301 (D998200597-102)
Page 169
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. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 169 of 301 (D998200597-102)
Page 170
MagTek recommends proceeding to the next row on receiving any of these characters: • Null (0x00) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 170 of 301 (D998200597-102)
The barcode reader has successfully read a barcode. In this case, the device 04 03 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. Barcode Reader, Read Barcode Result, Success, EMV Type The barcode reader has successfully read a barcode.
Page 172
Table 7.4-6 - Notification Payload for Barcode Reader, Read Barcode Result, Success (Unencrypted Data) Value / Description Typ Req Default Barcode Data Container /DF74 Barcode Data DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 172 of 301 (D998200597-102)
To reflect this hierarchy, this section of the document groups settings by major categories that correspond to the tree structure, which roughly breaks down into overall property type, module, and submodule. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 173 of 301 (D998200597-102)
The device uses this property when it generates an EMV Batch Data Type data object to contain transaction result data, to determine what tags to include in the data object. Description It serves the same purpose that MagTek custom tag DFDF17 serves on some other MagTek devices. Securing Key None Min.
The device uses this property when it generates an EMV Batch Data Type data object to contain reversal data, to determine what tags to include in the data object. It serves Description the same purpose that MagTek custom tag DFDF05 serves on some other MagTek devices. Securing Key None Min.
Bit 1: Support digital receipt Bit 2: Support service issuance Bit 3: Support OTA POS data Bit 4: RFU Bit 5: RFU Bit 6: RFU Bit 7: RFU DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 195 of 301 (D998200597-102)
When the device sends masked track data, it replaces some characters in the track data with a specified mask character. The specific characters the device masks depends on the card encode type. The device DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 197 of 301 (D998200597-102)
This OID is reserved for Mey Mapping of MagTek Token. 8.2.2.9 Property 1.1.2.4.1.6 Key Mapping of User Data 1 This OID is reserved for Mey Mapping of User Data 1. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 204 of 301 (D998200597-102)
To avoid ambiguity, if the solution specifies that more than one device of the same name will be available, MagTek recommends including a unique identifier in the device name so the operator can differentiate.
Data Type Binary Valid Values A prefix, such as “DF II Go-“ for DynaFlex II Go, followed by the device’s serial number. For example, “DF II Go-B603226”. Devices are always deployed with the serial number loaded, but prior to loading the...
Only values between 6 and 3200 are valid. After the host changes this property, the device must be reset before the changes will take effect. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 218 of 301 (D998200597-102)
REQUEST. See the Core Bluetooth Specification for details. Only values between 0 Description and 499 are valid. After the host changes this property, the device must be reset before the changes will take effect. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 219 of 301 (D998200597-102)
Specification for details. Only values between 10 and 3200 are valid. After the host changes this property, the device must be reset before the changes will take effect. Securing Key None DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 220 of 301 (D998200597-102)
Bluetooth LE connection. Description After the host changes this property, the device must be reset before the changes will take effect. Securing Key None Min. Len (b) DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 221 of 301 (D998200597-102)
8.3.3.7 Property 1.2.2.3.1.7 Bluetooth LE Minimum Advertising Interval Table 8.3-65 - Property 1.2.2.3.1.7 Bluetooth LE Minimum Advertising Interval Property Description Property OID 1.2.2.3.1.7 / 0x010202030107 Name Bluetooth LE Minimum Advertising Interval DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 222 of 301 (D998200597-102)
Page 223
Table 8.3-67 - Get Response Example Example (Hex) AA0081048232D1018204000000008482001CD10181072B06010401F609850101890CE20AE208E30 6E104C70200A0 Table 8.3-68 - Set Request Example Example (Hex) AA0081040112D111841CD11181072B06010401F609850101890CE20AE208E306E104C70200B0 Table 8.3-69 - Set Response Example Example (Hex) AA0081048212D1118204000000008482001CD11181072B06010401F609850101890CE20AE208E30 6E104C70200B0 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 223 of 301 (D998200597-102)
AA00 81040128D101 841AD101 81072B06010401F609 850101 890AE208E206E304E102C800 Table 8.3-72 - Get Response Example Example (Hex) AA0081048232D1018204000000008482001CD10181072B06010401F609850101890CE20AE208E30 6E104C80200A0 Table 8.3-73 - Set Request Example Example (Hex) AA0081040112D111841CD11181072B06010401F609850101890CE20AE208E306E104C80200B0 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 224 of 301 (D998200597-102)
AA00 81040128D101 841AD101 81072B06010401F609 850101 890AE208E206E304E102CA00 Table 8.3-82 - Get Response Example Example (Hex) AA0081048232D1018204000000008482001BD10181072B06010401F609850101890BE209E207E305 E103CA0100 Table 8.3-83 - Set Request Example Example (Hex) AA0081040112D111841BD11181072B06010401F609850101890BE209E207E305E103CA0100 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 226 of 301 (D998200597-102)
After the host changes this property, the device must be reset before the changes will take effect. Securing Key None Min. Len (b) Max. Len (b) 1 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 227 of 301 (D998200597-102)
Property 1.2.2.3.1.D Bluetooth LE Debug Mode Enabled Table 8.3-90 - Property 1.2.2.3.1.D Bluetooth LE Debug Mode Enabled Property Description Property OID 1.2.2.3.1.D / 0x01020203010D Name Bluetooth LE Debug Mode Enabled DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 228 of 301 (D998200597-102)
Page 229
Table 8.3-93 - Set Request Example Example (Hex) AA00 81040155D111 8410 D111 850101 870402020301 8903 CD0100 Table 8.3-94 - Set Response Example Example (Hex) AA0081048255D11182040000000084820010D1118501018704020203018903CD0100 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 229 of 301 (D998200597-102)
Property 2.1.2.3.9.1 Apple VAS Kernel ID Table 8.4-88 - Property 2.1.2.3.9.1 Apple VAS Kernel ID Property Description Property OID 2.1.2.3.9.1 / 0x020102030901 Name Apple VAS Kernel ID DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 271 of 301 (D998200597-102)
The device uses this property to report its PCI Hardware ID. Customers can use this Description value to compare against the device’s certification records on the PCI web site. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 273 of 301 (D998200597-102)
Securing Key None Min. Len (b) Max. Len (b) 1 Data Type Binary Valid Values 0x00..0x64 Default None DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 282 of 301 (D998200597-102)
ID, followed by the tree prefix, followed by the relative OID. If a message does not include the optional company ID or tree prefix, company ID is assumed to be the MagTek arc above, and the tree prefix is assumed to be a reasonable sequence of additional nodes based on the purpose and scope of the message.
128 decimal (0x80). For primary values greater than 0x80, additional encoding rules apply that are not necessary to detail here, because for simplicity MagTek selects OID primary values that are equal to 0x79 or less (and in many cases, 0x30 or less); In addition, TLV encoding places additional restrictions on selection of OID, in that if the OID is to be used directly as a tag in a TLV data object, it must not be greater than 0x1F (see section 3.2.1.1...
06. Its encoding is E3 06 E5 04 E7 02 C9 00, which is the final encoding of whole “empty bucket” OID 3.5.7.9. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 287 of 301 (D998200597-102)
Table 8.6-25 - Get Response Example Example (Hex) AA00810482CED812820400000000 Table 8.6-26 - Get Request Example Example (Hex) AA0081080400D8120000030084818D4D47544B41503130C10400000300CE7D00000000000001600 00000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000583F99A8DF1A414B11A1607402AE67722C4F59B9 Table 8.6-27 - Get Response Example Example (Hex) AA0081048200D812820400000000 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 289 of 301 (D998200597-102)
Table 8.6-29 - Get Response Example Example (Hex) AA008104828DD812820400000000 Table 8.6-30 - Get Request Example Example (Hex) AA0081080400D8120000050084114D47544B41503130C10400000500CE01AA Table 8.6-31 - Get Response Example Example (Hex) AA0081048200D812820400000000 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 290 of 301 (D998200597-102)
Table 8.6-33 - Get Response Example Example (Hex) AA0081048214D812820400000000 Table 8.6-34 - Get Request Example Example (Hex) AA0081080400D8120000000084114D47544B41503130C10400000000CE01AA Table 8.6-35 - Get Response Example Example (Hex) AA0081048200D812820400000000 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 291 of 301 (D998200597-102)
Table 8.6-37 - Get Response Example Example (Hex) AA008104821BD812820400000000 Table 8.6-38 - Get Request Example Example (Hex) AA0081080400D8120000010084284D47544B41503130C10400000100CE18AA9A6CCE52123D231 5BF3759D466BC0F7C4572A754FF3300 Table 8.6-39 - Get Response Example Example (Hex) AA0081048200D812820400000000 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 292 of 301 (D998200597-102)
Table 8.6-41 - Get Response Example Example (Hex) AA0081048235D812820400000000 Table 8.6-42 - Get Request Example Example (Hex) AA0081080400D8120000020084284D47544B41503130C10400000200CE18AA3dcfbc51fcdfd06ada3 6181f1cd3aee3f8f879bcFF3500 Table 8.6-43 - Get Response Example Example (Hex) AA0081048200D812820400000000 DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS) Page 293 of 301 (D998200597-102)
Physical Button (DynaFlex Only) All DynaFlex devices have a single physical button. On the DynaFlex II Go, it is located on the left side. On all other DynaFlex models, the button on the back of the device near the USB port. Pressing and holding this button can activate extra functions on the device.
MagTek’s published specifications. This warranty shall be provided only for a period of one year from the date of the shipment of the product from MagTek (the “Warranty Period”). This warranty shall apply only to the “Buyer” (the original purchaser, unless that entity resells the product as authorized by MagTek, in which event this warranty shall apply only to the first repurchaser).
Page 296
Appendix E - Warranty, Standards, and Certifications LIMITATION ON LIABILITY EXCEPT AS PROVIDED IN THE SECTIONS RELATING TO MAGTEK’S LIMITED WARRANTY, MAGTEK’S LIABILITY UNDER THIS AGREEMENT IS LIMITED TO THE CONTRACT PRICE OF THIS PRODUCT. MAGTEK MAKES NO OTHER WARRANTIES WITH RESPECT TO THE PRODUCT, EXPRESSED...
Page 297
• Consult the dealer or an experienced radio/TV technician for help. Caution: Changes or modifications not expressly approved by MagTek could void the user’s authority to operate this equipment. CANADIAN DECLARATION OF CONFORMITY This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Page 298
Class B devices. EU STATEMENT Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU.
Page 299
Be careful when moving or relocating the device. Use proper lifting techniques. • Use materials and supplies specifically designed for MagTek devices. Using unsuitable materials may result in poor performance, and in some cases may be hazardous. DynaFlex II Go| Secure Card Reader | Programmer’s Manual (COMMANDS)
Page 300
SUPPORT. TERMS, CONDITIONS, AND RESTRICTIONS MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the "Software." LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products.
Page 301
Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of the State of California and shall inure to the benefit of MagTek, Incorporated, its successors or assigns.
Need help?
Do you have a question about the DynaFlex II Go and is the answer not in the manual?
Questions and answers