Programmer's99875629 Owner's manual
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 Connection Types
- 3 Command Set
- 3.1 About Big Block Data Mode
- 3.2 About SRED / Non-SRED Firmware
- 3.3 About Commands Tagged As “MAC”
- 3.4 General Feature Reports
- 3.4.1 Report 0x01 – Response ACK
- 3.4.2 Report 0x02 – End Session
- 3.4.3 Report 0x03 – Request Swipe Card
- 3.4.4 Report 0x04 – Request PIN Entry
- 3.4.5 Report 0x05 – Cancel Command
- 3.4.6 Report 0x06 – Request User Selection
- 3.4.7 Report 0x07 – Display Message
- 3.4.8 Report 0x08 – Request Device Status
- 3.4.9 Report 0x09 – Set Device Configuration
- 3.4.10 Report 0x09 – Get Device Configuration
- 3.4.11 Report 0x0A – Request MSR Data
- 3.4.12 Report 0x0B – Get Challenge
- 3.4.13 Report 0x0D – Send Session Data - Amount
- 3.4.14 Report 0x0D – Send Session Data - PAN
- 3.4.15 Report 0x0E – Get Information
- 3.4.16 Report 0x0F – Login/Authenticate
- 3.4.17 Report 0x0F – Logout
- 3.4.18 Report 0x10 – Send Big Block Data to Device
- 3.4.19 Report 0x11 – Request Manual Card Entry
- 3.4.20 Report 0x14 – Request User Data Entry
- 3.4.21 Report 0x1A – Request Device Information
- 3.4.22 Report 0x1C – Set/Get BLE Power Configuration (BLE Only)
- 3.4.23 Report 0x1D – Set BLE Module Control Data (BLE Only)
- 3.4.24 Report 0x1E – Set iAP Protocol Info (30-pin Only)
- 3.4.25 Report 0x1E – Get iAP Protocol Info (30-pin Only)
- 3.4.26 Report 0x1F – Request Clear Text User Data Entry
- 3.4.27 Report 0x30 – Set / Get KSN
- 3.4.28 Report 0x31 – Set KSN Encrypted Data
- 3.4.29 Report 0x32 – Set BIN Table Data (MAC)
- 3.4.30 Report 0x32 – Get BIN Table Data
- 3.4.31 Report 0xFF – Device Reset
- 3.5 General Input Reports
- 3.5.1 Report 0x20 – Device State Report
- 3.5.2 Report 0x21 – User Data Entry Response Report
- 3.5.3 Report 0x22 – Card Status Report
- 3.5.4 Report 0x23 – Card Data Report
- 3.5.5 Report 0x24 – PIN Response Report
- 3.5.6 Report 0x25 – User Selection Response Report
- 3.5.7 Report 0x27 – Display Message Done Report
- 3.5.8 Report 0x29 – Send Big Block Data to Host
- 3.5.9 Report 0x2A – Delayed Response ACK
- 3.5.10 Report 0x2B – Test Response
- 3.5.11 Report 0x2D –BLE Module Control Data (BLE Only)
- 3.5.12 Report 0x2E – Clear Text User Data Entry Response Report
- 3.6 EMV-Related Reports
- 3.6.1 Report 0x2C – EMV Cardholder Interaction Status Report
- 3.6.2 Report 0xA1 – Set or Get EMV Tag(s) (MAC)
- 3.6.3 Report 0xA2 – Request Start EMV Transaction
- 3.6.4 Report 0xA4 – Acquirer Response (MAC)
- 3.6.5 Report 0xA5 – Set or Get CA Public Key (MAC)
- 3.6.6 Report 0xA8 – Get Kernel Info
- 3.6.7 Report 0xAB – Request EMV Transaction Data (MAC)
- 3.6.8 Report 0xAC – Merchant Bypass PIN Command
- Appendix A Examples
- Appendix B Terminology
- Appendix C Status and Message Table
- Appendix D MagTek Custom EMV Tags
- Appendix E Configurations
- Appendix F Error Codes
- Appendix G User-Defined Messages
- Appendix H Factory Defaults
- Appendix I Language and Country Codes
- Appendix J BLE Module Control Data
- J.1 BLE Module Configuration Properties
- J.1.1 Get property command
- J.1.2 Set property command
- J.1.3 Software ID property
- J.1.4 Bluetooth Device Address property
- J.1.5 Bluetooth Device Name property
- J.1.6 Configuration Revision property
- J.1.7 Power Timeout property
- J.1.8 Power Control property
- J.1.9 Advertising Control property
- J.1.10 Passkey property
- J.1.11 Desired Minimum Connection Interval Property
- J.1.12 Desired Maximum Connection Interval Property
- J.1.13 Desired Slave Latency Property
- J.1.14 Desired Supervision Timeout Property
- J.1.15 Connection Parameter Update Request Control Property
- J.2 Other Commands
- J.1 BLE Module Configuration Properties

3 - Command Set
DynaPro Mini| PIN Encryption Device | Programmer’s Reference (Commands)
Page 67
ICC, and will advise the cardholder that ICC is preferred by displaying USE CHIP READER. If the ICC
fails or the service code does not begin with a 2 or a 6, the device will prompt the cardholder for an MSR
swipe. After a successful swipe, the device will prompt the user to select debit or credit. If this is a debit
account type, the device will request a PIN.
If the user presents an ICC card, the LCD display will show ICC applications that are mutually supported
and ask the cardholder to choose the preferred application. If a PIN entry is needed per EMV 4.x
requirements, the LCD will show ENTER PIN and start the PIN entry timer. If the user presses the
cancelation button or the transaction times out, cancelled or timed out, the device will perform 0xA2
Command Completion.
After PIN entry, the device will display either PIN OK or will cycle through INCORRECT PIN and TRY
AGAIN up to the PIN retry limit. If the number of attempts reaches PIN try limit-1, the device will
display LAST TRY. If the user exceeds the PIN entry retry limit, the device will perform 0xA2
Command Completion, otherwise the transaction proceeds to the approval stage.
When the device is configured to allow PIN bypass using tag DFDF68, the PIN requirement can be
bypassed by the merchant by setting bit 0, byte 6 of the 0xA2 command. CVM and TVR bits must be set
appropriately per EMV 4.x requirements. The PIN requirement can also be bypassed by the cardholder.
The transaction approval method will be determined per EMV 4.x requirements.
For OFFLINE, the device gets the TC or AAC from the ICC for later transmission to the host. Depending
on the transaction outcome, the LCD will show APPROVED, DECLINED, or ERROR, and the device
will perform 0xA2 Command Completion.
For ONLINE, the device sends the ARQC tags encrypted using the MSR DUKPT data variant key and
signed MAC variant key to the host using Report 0x29 – Send Big Block Data to Host for approval,
starts a HOST response timer, and waits for Report 0xA4 – Acquirer Response, processes the Host
Response, gets TC or AAC from the ICC, depending on the transaction outcome, the LCD will show
“APPROVED”, “DECLINED” or "ERROR," and perform 0xA2 Command Completion.
A transaction can be forced ONLINE by the merchant by setting bit 1, byte 6 of the 0xA2 command.
3.6.3.1 0xA2 Command Completion
When this command completes (card read OK, transaction finished, ICC problems, command cancelled,
cardholder cancels, or timeout), the device clears all sensitive data buffers and sends a Report 0x22 –
Card Status Report to the host. If the Card and Operation Status are both OK, the host should send a
request to get the EMV card data with Report 0xAB – Request EMV Transaction Data.
3.6.4 Report 0xA4 – Acquirer Response (MAC)
If a smart card and the device decide to handle a transaction online, after sending the related EMV tags in
the EMV authorization request to host, the host returns a response from the acquirer/issuer.
The response using big block data includes one or more of the following EMV data:
‘8A’ – response code
‘91’ – ARPC
‘71’ – Issuer Script Template 1
‘72’ – Issuer Script Template 2