This page provides access to the essential documentation resources for developing with and managing the DynaFlex I PED secure card reader. Here you will find installation and operation manuals, subsidiary development manuals, software instructions and much more

DynaFlex II PED Documentation

Product-specific Manuals

The following instructions detail how to use the MTNET OEM Demo with mDynamo or DynaDip on Windows PC via USB interface.

MTNET OEM Demo queries for device features upon connecting. Some demo features are disabled based on what is supported on the device. MTNET OEM Demo does not automatically set Time.

• Connect the device to the USB port of the Windows PC.

• Launch the MTNET OEM Demo and press the button to scan for connected USB devices

• If your device has an additionally attached device to its SPI or UART port, select the appropriate device type in the list for SPI port and UART Port before connecting.

• Select the Device ID and press the Connect button to open the device

• Swipe a magnetic stripe card to read the card data if you have an attached MSR head.

• To send a command to the device, enter the command in the command text box, select the appropriate device to send to and press the Send Command button..

• To read a chip card, press the Set Time button and send to the Board. If you have an attached NFC module connected to the UART port, press the Set Time button, and send the UART before reading a contactless card.

• To begin an EMV transaction, select desired Transaction type and Response, press the Start button, and then present the appropriate card whenthe Present Card message appears.

• Select an Application in the Select Application window.

• If you want to cancel the EMV transaction, press the Cancel button. Please note that the cancel feature will only work before the card is inserted.

• To clear the screen, press the Clear button.

• To close the device, press the Disconnect button

Overview

DynaFlex II Go and DynaFlex II Go BCR deliver the next generation of mobile payment solutions, both models are PCI PTS 6.x. These secure card reader authenticator devices accept magnetic stripe cards; EMV chip cards (contact and contactless); NFC enabled mobile wallets including Apple® Pay, Samsung™ Pay, Google Pay™, with support for Google Smart Tap and Apple VAS protocols, and MIFARE® Classic,

MIFARE® DESFire, and NTag. DynaFlex II Go BCR additionally has an integrated barcode reader. Ideal for cafés, restaurants, boutiques, airlines, retail banks, and other developers looking to build a secure payment solution that accepts swipe, tap, and dip technology.

Major Components

DynaFlex II Go Major Components

Top Face

Environmental Notice

DynaFlex II Go products are designed to provide flexible mounting options. The device can be mounted to the host via an external clip or the embedded lanyard. When designing an enclosure or mounting bracket, ensure there is adequate clearance for cardholders to tap, swipe, dip, and for users to present a bar code. Proximity to metal can reduce the device’s reading range. DynaFlex II Go offers an optional OtterBox uniVERSE clip adapter and a countertop stand.

DynaFlex II Go is available with USB-C or USB-C and Bluetooth LE connection. Check you model number for connection configuration.

For best results, use the cable that is included with the device. Connect the cable to the device. Connect the other end to the HOST USB port. Device will automatically power on. Windows will start an installation of the driver on initial connection. Windows will report DEVICE IS READY and device shows in Windows Device Manager under HUMAN INTERFACE DEVICES as two devices HID-COMPLIANT VENDOR-DEFINED (VID 0801, PID 2024) and USB INPUT DEVICES.

See D998200386 MagTek Universal SDK

Disconnect any active connections to the device. Install Android HOST software. Press and hold the POWER BUTTON for 4 beeps until LED 4 starts flashing indicating Bluetooth LE pairing is in process. LED flashes once per second for up to 3 minutes. On the Android HOST, launch SETTINGS >BLUETOOTH> SEARCH FOR DEVICES > locate

the 7-digit serial number on the device label (DF II GO_xxxxxxx). Select device. When HOST shows BLUETOOTH PAIRING REQUEST and asks for configuration key, enter [000000]. The device appears in PAIRED DEVICES. Change the default passkey.

To UNPAIR, locate the device in BLUETOOTH configuration page on HOST, press the settings (gear) icon, press FORGET.

Ensure HOST Bluetooth LE is turned on and working. Disconnect any other connections to the device. On the HOST, install and configure the software. Ensure HOST software is configured to look for the device. The device transmits in GATT format. In START on HOST type BLUETOOTH and select BLUETOOTH AND OTHER DEVICE

SETTINGS. Locate the 7-digit serial number on device label. Press and hold the POWER BUTTON on device for 4 beeps until LED 4 starts flashing indicating Bluetooth pairing is in process. LED flashes once per second for up to 3 minutes. Press the ADD BLUETOOTH OR OTHER DEVICE button and launch ADD A DEVICE window. Under CHOOSE THE KIND OF DEVICE YOU WANT TO ADD select BLUETOOTH.

Locate the device called DF II GO-xxxxxxx. Enter configured passkey (000000) press the CONNECT button. After a short period CONNECTED appears. Press DONE. Change the default passkey.

To UNPAIR, select the device in BLUETOOTH AND OTHER DEVICE SETTINGS window and press the REMOVE DEVICE button.

DynaFlex II Go receives power from the USB-C port. The battery must be periodically recharged by connecting the device to a USB port or stand-alone USB charger. The device requires a USB power supply that can provide at least 500mA @ 5V.

• Powered Off Mode is the shipping and storage mode of the device. No external power is applied to the device through the USB cable or from the internal rechargeable battery.

• Active Mode is the device’s normal “awake” state when it is in use. In this mode, the device LED indicators are powered on, and the device is ready to receive commands from the host.

• To set the device from Active mode to Powered Off mode: remove power, and press and hold the power button for two beeps.

DynaFlex II Go has 4 LEDs that provide responses to the user for Power, Connection, Device Status, and Card Status. The Installation and Operation Manual has a more complete list of light signals.

The device does not have an on-screen configuration interface. However, it does have settings the HOST can change using commands.

Operator presses the Start transaction button on the HOST device. LED 1 and 2 will remain on. When a card is swiped, all four LEDs will turn on in sequence (1, 2, 3 then 4), followed by a long beep, indicating a successful transaction. Swipe the card with the magnetic stripe facing away from the face of the device. After a successful transaction, the device will return to the ready state.

Locate the insertion slot on the face of the device. Orient the chip card so the chip faces the face of the device. Insert the chip card into the slot, then push gently on the card until it stops. The operator presses the Start transaction button on the HOST device.

LED 1 and 2 will remain on. When a card is inserted, LEDs 1, 2 and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction.

Hold QR Code or barcode approximately 6 inches away from barcode reader. The operator presses the Start button on the HOST device. LED 1,2, and the BCR status light will be illuminated see. When a barcode is detected, only LED 1 will remain illuminated, the BCR status LED will be off, and a long beep will sound.

The operator presses the Start transaction button on the host device. LED 1 will remain on. When a card is presented within range of the contactless reader, LEDs 1,2,3, and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction. Tap the card or electronic payment device on the contactless landing zone, indicated by the EMVCo Contactless Indicator on the device’s face. The card or device’s antenna* must be centered over the contactless landing zone. Remove the card or electronic payment device from the contactless landing zone.

Users can take advantage of the OtterBox® uniVERSE® adaptor for easy sliding and connection to a wide range of mobile devices, including phones and tablets

FCC INFORMATION

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.

Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 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.

Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.

This Class B digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.

INDUSTRY CANADA (IC) RSS

This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.

Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes: (1) L’appareil ne doit pas produire de brouillage, et (2) L’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.

CUR/UR

This product is recognized per Underwriter Laboratories and Canadian Underwriter Laboratories 1950.

CE STANDARDS

Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for 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. The full text of the EU declarations of conformity is available at the following Internet addresses:

UL/CSA

This product is recognized per UL 60950 1, 2nd Edition, 2011 12 19 (Information Technology Equipment - Safety - Part 1: General Requirements), CSA C22.2 No. 60950 1 07, 2nd Edition, 2011 12 (Information Technology Equipment - Safety - Part 1: General Requirements).

ROHS STATEMENT

When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( Pb ).

PCI STATEMENT

PCI Security Standards Council, LLC (“PCI SSC”) has approved this PIN Transaction Security Device to be in compliance with PCI SSC’s PIN Security Requirements.

When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.

UKCA STATEMENT

Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (Wireless LAN and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Radio Equipment Regulations 2017 Directive S.I.2017:1206. The full text of the UKCA declarations of conformity is available at the following Internet addresses:

After creating an instance of the MTSCRA class in your custom software project, use the methods described in this section to communicate with SCRA device.

requestDeviceList

This method initiates the discovery of devices that are visible to the host using the specified connection interface. The DeviceListReceived() event will provide information regarding the available devices once the discovery process is completed.

public void requestDeviceList(MTConnectionType connectionType)

Parameters:

Return Value: None

This method sets the connection type of the device.

public void setConnectionType(MTConnectionType connectionType)

Parameters:

The following table shows the connection types supported by the various programming interfaces:

The following table shows the connection types supported by the various SCRA devices:

Return Value: None

This method sets the address of the device.

public void setAddress(string deviceAddress)

Parameters:

Return Value: None

This method sets the device ID.

public void setDeviceID(string deviceID)

Parameters:

Return Value: None

This method opens connection to the device. If you use the MagTek Universal Windows SDK and USB Card reader with PID 0011, please refer to section 2.5 How to remove POS HID Magnetic Stripe Reader.

public void openDevice()

Parameters: None

Return Value: None

This method closes the connection to the device.

public void closeDevice()

Parameters: None

Return Value: None

This method returns whether the device is connected or not.

public bool isDeviceConnected()

Parameters: None Return Value:

Return true if the device is connected. Otherwise, return false.

This method returns whether the device supports EMV or not.

public bool isDeviceEMV()

Parameters: None Return Value:

Return true if EMV is supported by the device. Otherwise, return false.

This method returns whether the device is an OEM device or not.

public bool isDeviceOEM()

Parameters: None Return Value:

Return true if device is OEM. Otherwise, return false.

Get stored masked tracks data. If decodable track data exists for a given track, it is located in the Masked Track Data field that corresponds to the track number. The length of each Masked Track Data field is fixed at 112 bytes, but the length of valid data in each field is determined by the Masked Track Data Length field that corresponds to the track number. Masked Track Data located in positions greater than indicated in the Masked Track Data Length field are undefined and should be ignored.

The Masked Track Data is decoded and converted to ASCII and then it is masked. The Masked Track Data includes all data starting with the start sentinel and ending with the end sentinel. Much of the data is masked; a specified mask character is sent instead of the actual character read from the track. Which characters are masked depends on the format of the card. Only ISO/ABA (Financial Cards with Format Code B) and AAMVA cards are selectively masked; all other card types are either entirely masked or sent totally in the clear. There is a separate masking property for ISO/ABA cards and AAMVA cards. See the ISO Track Masking property and the AAMVA Track Masking property for more information. See 99875475 for a description on how ISO/ABA and AAMVA cards are identified.

Each of these properties allows the application to specify masking details for the Primary Account Number and Driver’s License / ID Number (DL/ID#), the masking character to be used, and whether a correction should be applied to make the Mod 10 9 (Luhn algorithm) digit at the end of the number be correct.

public string getMaskedTracks()

Parameters: None Return Value:

Return stored masked tracks data string.

Flow Chart

Sample Transaction Flow Code

// #1

MTSCRA m_SCRA = new MTSCRA();

// Delegate the MTSCRA Events. 
m_SCRA.OnDisplayMessageRequest += OnDisplayMessageRequest;
.
// Assign parameters. 
byte timeLimit = 0x3C; 
byte cardType = 0x07; 
byte option = 0x00;
byte[] amount = new byte[] { 0x00, 0x00, 0x00, 0x00, 0x15, 0x00 }; 
byte transactionType = 0x00; // Purchase
byte[] cashBack = new byte[] { 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 }; 
byte[] currencyCode = new byte[] { 0x08, 0x40 };
byte reportingOption = 0x02; // All Status Changes

// Start transaction.
long result = m_SCRA.startTransaction( 
timeLimit,
cardType, 
option, 
amount,
transactionType, 
cashBack, 
currentCode, reportingOption);

// #2

protected void OnDisplayMessageRequest(obj sender, byte[] data)
{
    String message;

    // Get the message. 
    if (data != NULL)
    {
        message = System.Text.Encoding.UTF8.GetString(data);
    }

// A data size of 0 is an instruction to clear the display. 
if (data.Length == 0)
{
// Clear the display.
}
}

// #3

protected void OnUserSelectionRequest(object sender, byte[] data)
{
    /* data[0]	– selection type 
        data[1]	– timeout
        data[2..n] – remainder contains zero-terminated string items */

    // display/retrieve user selection.
    .
    // set status and selection result. 
    m_SCRA.setUserSelectionResult(status, selection);
}

// #4

protected void OnARQCReceived(object sender, byte[] data)
{
    /* data[0..1] – ARQC length
        data[2..n] – remainder contains the ARQC TLV object */


    // #4a Forward ARQC to Processor.
    
    /* An application function to forward the ARQC 
        to a Processor for approval. */
    proccesorResponse = sendARQCToProcesor(data);


    /* No need to send ARQC Response if transaction option 
        had enabled Quick Chip mode. */
    if (isQuickChipEnabled())
    {
        return;
    }


    // #4b Set Acquirer Response.

    // An application function to build Acquirer Response. 
    buildAcquirerResponse(processorResponse);

    // Set Acquirer Response.
    m_SCRA.setAcquirerResponse(response);

}

// #5

protected void OnDisplayMessageRequest(obj sender, byte[] data)
{
    String message;

    // Get the message. 
    if (data != NULL)
    {

        message = System.Text.Encoding.UTF8.GetString(data);
    }

    // A data size of 0 is an instruction to clear the display. if (data.Length == 0)
    {
        // Clear the display.
    }
}

// #6

protected void OnTransactionResult(obj sender, byte[] data)
{
    /* data[0]	– Signature Required 
        data[1..2] – Batch Data length
        data[3..n] – remainder contains the Batch Data TLV object */

    // Parse the TLV from data[].
    .
    // Abstract Approval status from TLV tag “DFDF1A”.
    .
    // Abstract Signature Required status from TLV tag data[0].
    .
}

The DynaFlex II SCR uses the shared DynaFamily Multi-Interface Card Reader Platform (MMS) command set. This manual is a device-scoped map into the API & Command Reference with the sections this device relies on linked below.

In this manual

• --> How the SCR protects data and manages keys: DUKPT (3DES→AES), MAC, KSNs, encryption/decryption, and the PCI requirements like the 24-hour reset and device lock.

• --> The SCR's PCI PTS POI security policy, certifications, and the regulatory documentation for deployment.

• -->Working with contactless cards and tags — NFC/MIFARE pass-through and the supported card technologies (NTag, Classic, DESFire, Plus).

This function retrieves the track decode status after a cardholder swipes a card.

Parameters: None

Return Value:

Hex string, each 2 digits represent one track’s decode status, where the left most 2 digits are for Track 1.

• “00” = Success

• "01” = Error or not decodable

Setup for XCode Project

To add the MTSCRA SDK libraries to a custom software project in the XCode development environment, follow these steps:

1. Download the MTSCRA Demo app from MagTek.com.

2. Open your custom software project in XCode.

3. Open the MTSCRA Demo app folder in Finder.

4. Open the Lib subfolder.

5. Include the following files in your custom software project within XCode:

   1. libMTSCRA.a

   2. MTSCRA.h

6. Ensure the library search paths are set up correctly.

7. If you are writing an app that will connect to Bluetooth LE devices, see the additional steps section 3 Important Information About Bluetooth LE.

8. Clean, build, and run your custom software project to make sure the library imported correctly.) In your custom software, create an instance of MTSCRA. For examples, including how to register delegate functions in your app for callbacks, see the source code included with the MTSCRA Demo app and / or Appendix C Code Examples .

9. Begin using the features provided by the MTSCRA object’s methods. For details about these methods, see section 4 MTSCRA Functions

• Add the following files to project, and setup the bridge header folder in build settings.

  1. MTSCRA.H

  2. MTSCRA-Bridge.h
• Add libMTSCRA.a, in build phases->Link Binary with libraries, click ‘+’, then select Add Files and browse to libMTSCRA.a.

• Add libc++.tbd in build phases->Link Binary with libraries, click ‘+’, then type “c++” in the filter area and pick libc++.tbd.

• After adding those two libraries, this will be in the project.

• Add the external accessory protocols into info file. In the screen shot, it adds iDynamo5 and iDynamo6 with default protocols. Add your custom protocol if different.

getCardEncodeType

Retrieves the card encode type.

public string getCardEncodeType()

Parameters: None Return Value:

String representing the card encode type.

Card Encode Type

This is a string value which indicates the type of encoding that was found on the card. The following table defines the possible values.

Retrieves data field count.

public int getDataFieldCount()

Parameters: None

Return Value:

Data field count

Retrieves SHA-x hash code.

public string getHashCode()

Parameters: None Return Value:

String representing SHA-x hash code.

Retrieves device configuration.

public string getDeviceConfig(string configType)

Parameters:

configType can be one of:

• 8180: Send TLV Version on Power Up

• 8181: Send Discovery on Power Up

• 8280: Send Card name

• 8281: Send Card IIN

Return Value:

String representing device configuration.

Retrieves encryption status. This two-byte Binary field contains the Encryption Status. The Reader Encryption Status is sent in big endian byte order. Byte 1 is the least significant byte. Byte 1 LSB is status bit 0. Byte 2 MSB is status bit 15.

public string getEncryptionStatus()

Parameters: None Return Value:

String representing decryption status as a 2-byte binary field.

• Bit 0 = DUKPT Keys exhausted (1=exhausted, 0=keys available)

• Bit 1 = Initial DUKPT key Injected, always set to One (Primary DUKPT Key)

• Bit 2 = Encryption Enabled, always set to One

• Bit 3 = Reserved (always set to zero)

Retrieves firmware version.

public string getFirmware()

Parameters: None

Return Value:

String representing firmware version.

Retrieves MagTek device serial number.

public string getMagTekDeviceSerial()

Parameters: None

Return Value:

String representing MagTek device serial number.

Retrieves response data.

public string getResponseData()

Parameters: None

Return Value:

String representing response data.

Retrieves response type.

public string getResponseType()

Parameters: None

Return Value:

String representing response type. For Audio Reader, always “C101”.

Retrieves the value of the specified tag.

public string getTagValue(string tag, string data)

• Parameters: None

  • tag

    • Tag to search for

  • data

Return Value: String representing tag value.

• When calling functions startScanningForPeripherals or openDevice, the application should make sure bleReaderStateUpdated has received a device status and that the most recent status was OK , otherwise the device will not be able to connect, and iOS will not throw any error if Bluetooth is not ready.

• Starting in iOS 13, app projects must specify the Privacy Usage Description for Bluetooth by NSBluetoothAlwaysUsageDescription in the info.plist file. file. Accessing Core Bluetooth without the usage descriptions will cause a runtime crash. For backward compatibility with older versions of iOS, define NSBluetoothAlwaysUsageDescription as well.

This section gives the format of the data for the Online Processing Result / Acquirer Response message. This request is sent to the reader in response to an ARQC Message notification from the reader. The output is controlled by Property 0x68 – EMV Message Format. There are currently 2 selectable formats: Original and DynaPro. It is a TLV object with the following contents.

Original format:

F9<len>/* container for ARQC Response data */ 
    DFDF25 (IFD Serial Number)<len><val> 
    FA<len>/* Container for generic data */
        70<len>/* Container for ARQC */ 
                8A<len> approval
                Further objects as needed...

DynaPro format:

F9<len>/* container for MAC structure and generic data */ 
    DFDF54 (MAC KSN)<len><val>
    DFDF55 (Mac Encryption Type><len><val> 
    DFDF25 (IFD Serial Number)<len><val> 
    FA<len>/* Container for generic data */
            70<len>/* Container for ARQC */ 
                    8A<len> approval
Further objects as needed... (ARQC padding, if any, to be a multiple of 8 bytes)
CBC-MAC (4 bytes, use MAC variant of MSR DUKPT key that was used in ARQC request, from 
message length up to and including ARQC padding, if any

Custom software can use the sendCommandToDevice method to send direct commands to the devices. This section provides information about commonly used commands.

Discovery

To send a Discovery command to device, use:

public void sendCommandToDevice(string command)

Parameters: Use “C10206C20503840900” as command string for audio readers.

Return Value:

The following device information will be retrieved.

Device SN, internal: Device serial number created by chip manufacturer. Use getDeviceSerial method to retrieve data.

Device SN, MagTek: Device serial number created by MagTek. Use getDeviceSerialMagTek method to retrieve data.

Device Firmware Part Number: Device firmware part number. Use getFirmware method to retrieve data.

Device Model Name: Device model name. Use getDeviceName method to retrieve data. Device TLV Version: Device TLV version. Use getTLVVersion method to retrieve data.

Device Part Number: Device part number. Use getDevicePartNumber method to retrieve data. Capability - MSR: 0 = No MSR, 1 = MSR. Use getCapMSR method to retrieve data.

Capability - TRACKS:

• 0 = Supported tracks: None.

• 1 = Supported tracks: Track1.

• 2 = Supported tracks: Track2.

• 3 = Supported tracks: Track1, Track2.

Use getCapTracks method to retrieve data.

Capability - MagStripe Encryption: 0 = No Encryption, 1 = TripDES DUKPT. Use getCapMagStripeEncryption method to retrieve data.

Every exchange with the DynaFlex II Go— the commands you send and the responses and notifications it returns — uses the standard Multi-Interface Card Reader Platform (MMS) message format. This section defines how requests, responses, notifications, and file messages are framed and parsed. The format is the same across DynaFamily readers and is documented once in the shared reference.

This page provides resources for MagTek's MMS (MagTek Messaging Schema) Dyna device family, which includes secure card readers and PIN pads that communicate using the MMS command set. These devices support reading magnetic stripe, EMV® Contact Chip, EMV Contactless, NFC Mobile Wallets, Non-payment NFC technologies, and 1D/2D barcodes. Here you will find documentation covering device communication protocols, developer tools, and configuration guides for various Dyna device models.

These sections detail a variety of information on OIDs, codes, tips & taxes and more.

System Status Information - Property Group 2.3.1.nnn

getKSN

Get stored key serial number. This 10-byte Binary field contains the DUKPT Key Serial Number used to encrypt the encrypted fields in this message. This 80-bit field includes the Initial Key Serial Number in the leftmost 59 bits and a value for the Encryption Counter in the rightmost 21 bits. If no keys are loaded, all bytes will have the value 0x00.

public string getKSN()

Parameters: None Return Value:

Return stored key serial number.

getDeviceName

Get device model name.

public string getDeviceName()

Parameters: None

Return Value:

Return device model name.

clearBuffers

Clears buffered data retrieved from the reader.

public void clearBuffers()

Parameters: None

Return Value: None

Retrieves battery level.

public long getBatteryLevel()

Parameters: None Return Value:

Battery Level (0 to 100)

Retrieves swipe count.

public long getSwipeCount()

Parameters: None

Return Value:

Long value representing swipe count. If the value is less than zero, it indicates the device does not support tracking of the number of card swipes.

Retrieves MagnePrint Capabilities.

public string getCapMagnePrint()

Parameters: None Return Value:

String representing MagnePrint capabilities:

• 0 = No MagnePrint,

• 1 = Short MagnePrint,

• 2 = Long MagnePrint

Retrieves MagnePrint Encryption Capabilities.

public string getCapMagnePrintEncryption()

Parameters: None Return Value:

String representing MagnePrint Encryption capabilities:

• 0 = No Encryption,

• 1 = Same as MagStripe (8122), other values TBD.

If absent, the default value is 1.

Retrieves MagneSafe 2.0 Encryption Capabilities.

public string getCapMagneSafe20Encryption ()

Parameters: None

Return Value:

String representing MagneSafe 2.0 Encryption Capabilities. 0 = Not supported, other values TBD.

Retrieves MagneStripe Encryption Capabilities.

public string getCapMagStripeEncryption()

Parameters: None Return Value:

String representing MagStripe Encryption Capabilities. 0 = No Encryption, 1 = TDES DUKPT / PIN Variant, other values TBD

Retrieves MSR Capabilities. public string getCapMSR() Parameters: None

Return Value:

String representing MSR Capabilities. 0 = No MSR, 1 = MSR.

This page provides comprehensive documentation for the iDynamo 5 Gen III secure card reader authenticator (SCRA), including developer guides, user manuals, and security policies to support integration and operation across iOS, Android, and Windows platforms.

Welcome to the resource hub for the iDynamo 5 Gen III, a compact and versatile secure card reader (SCR) designed for modern point-of-sale (P2PE) environments. It reads ISO-standard magnetic stripe cards and offers universal connectivity across iOS, Android, and Windows platforms via USB (Keyboard, HID, iAP2). This section provides all the documentation, software, and developer tools you need to successfully integrate, manage, and support the iDynamo 5 Gen III.

The DynaProx is a next-generation, EMV Contactless, and NFC Contactless reader from MagTek, designed for original equipment manufacturers (OEMs) and developers building secure payment, access control, and identification solutions. It combines the controller and antenna in a small form-factor, and is available in two models: the standard DynaProx for EMV Contactless, and NFC transactions, and the DynaProx BCR which includes a camera for reading 1D/2D barcodes. The device is engineered with the MagneSafe® Security Architecture, meeting requirements for contactless EMV 3.0 and PCI PTS POI 6.x, and supports triple DEA and AES-256 encryption with DUKPT key management to safeguard sensitive payment data.

Key capabilities

• Contactless (NFC) card and mobile wallet acceptance — tap-to-pay, no contact slot or magnetic stripe

• SRED point-to-point encryption at the moment of read (TDES / AES DUKPT)

• NFC/MIFARE pass-through and NFC card emulation (DynaCast)

• Compact contactless reader for attended checkout, transit, and access control

• PCI PTS POI–approved SCRA for attended acceptance (no PIN entry — see the DynaFlex II PED for PIN debit)

Retrieves TLV version.

public string getTLVVersion()

Parameters: None

Return Value:

String representing TLV version as a two-byte hex string.

Retrieves track decode status. This is a one-byte value, which indicates the status of decoding track 1. Bit position zero indicates if there was an error decoding track 1 if the bit is set to one. If it is zero, then no error occurred. If a track has data on it that is not noise, and it is not decodable, then a decode error is indicated. If a decode error is indicated, the corresponding track data length value for the track that has the error will be set to zero and no valid track data will be supplied.

public string getTrackDecodeStatus()

Parameters: None Return Value:

Track Decode Status. Consists of three 2-byte hex values representing the decode status for tracks 1, 2, and 3 (respectively from left to right). Values are:

To develop an iOS app using the MTSCRA SDK, follow the setup steps in section 2 How to Set Up the MTSCRA SDK, then create an instance of the MTSCRA object in your software project, then call the functions described in this chapter to communicate with the device. For sample code that demonstrates how to use these functions, see the contents of the MTSCRA Demo folder included with the SDK.

Generally, these functions will run in one of two modes:

• Asynchronous functions will return data using the event handlers (callback functions) defined in section 5 MTSCRA Delegate Methods.

• Synchronous functions will return requested data immediately in the function’s return value. If the requested data is not available immediately, synchronous calls will generally block until a specified wait time has elapsed.

Most calls that wait for input from the user will run in the asynchronous mode.

The DynaFlex II PED is a PCI PTS v6.x PED, a certified PIN Entry Device from MagTek, designed to meet the security demands of modern payment, banking, and point-of-sale applications. It supports a wide range of payment methods, including magnetic stripe, EMV® Contact Chip, EMV Contactless, and NFC Contactless payments, as well as 1D/2D barcode scanning. The device features a touchscreen for PIN entry, manual card data entry, and signature capture, and connects to Windows and Android host devices via USB and Windows, iOS, Linux, and Android via WebSocket or MQTT. The official MagTek DynaFlex II PED support page is a central hub containing all the resources you'll need. There you can find detailed product brochures, compliance documentation, software development kits (SDKs) such as the MagneFlex Powder API, comprehensive programmer’s manuals, and helpful resources including FAQs and instructional videos.

Key capabilities

• Contact, contactless (NFC), and magnetic stripe card reading in one device

• SRED point-to-point encryption at the moment of read (TDES / AES DUKPT)

• PIN entry on a secure PIN pad for PIN debit and cardholder verification

• Full color touch display for on-screen prompts, cardholder selection, and signature capture

• NFC/MIFARE pass-through and NFC card emulation (DynaCast)

• Optional barcode reader (BCR) for scanning outside a transaction

• PCI PTS POI–approved SCRA for attended, countertop acceptance

4.31 getCapMSR

This function gets the MSR capability of the device. For more information, see D99875483 – Track ID Enable Property.

(NSString *) getCapMSR

Parameters: None Return Value:

Return MSR Capability bit masking.

• 0 – Decodes standard ISO/ABA cards only

• 1 – Decodes AAMV and 7-bit cards also

If this flag is set to 0, only tracks that conform to the ISO format allowed for that track will be decoded. If the track cannot be decoded by the ISO method it will be considered to be in error.

• 00 – Track Disabled

• 01 – Track Enabled

• 10 – Track Enabled/Required (Error if blank)

This function gets the device’s capability for encrypting track data.

Return Value:

• “1” = Available

• “0” = Unavailable.

This function gets information about the device’s tracks capability.

Parameters: None

Return Value: A hex string for the track capability. See Track ID Enable Property in D99875475.

This function retrieves the card expiration date after a cardholder swipes a card.

Parameters: None

Return Value: String containing the card expiration date

This function gets the last 4 digits of the card account number (PAN) after a cardholder swipes a card.

Parameters: None

Return Value: String containing the last 4 digits of the PAN

This function gets the issuer identification number (IIN) of the card number after a cardholder swipes a card.

Parameters: None

Return Value: String containing the IIN

This function gets the cardholder name after a cardholder swipes a card.

Parameters: None

Return Value: String containing the cardholder name, for example, “John Wayne”.

This function gets the length of the PAN after a cardholder swipes a card.

Parameters: None

Return Value: Length of card number or PAN

This function retrieves the card’s service code after a cardholder swipes a card.

Parameters: None

Return Value: String containing the card’s service code

This function retrieves the part number and revision of the device’s firmware.

Parameters: None

Return Value: String containing firmware part number and revision.

This section gives the format of the data the device uses to do completion processing. The output is controlled by Property 0x68 – EMV Message Format. There are currently 2 selectable formats: Original and DynaPro. It is a TLV object with the following contents.

Original Format:

FE<len>/* container for generic data 
    */ DFDF25(IFD Serial Number)<len><val> 
    FA<len>/* container for generic data */
        F0<len>/* Transaction Results */
            F1<len>/* container for Status Data */
            … /* Status Data tags */
                DFDF1A - Transaction Status (See DFDF1A descriptions) 
                DFDF1B - Additional Transaction Information (always 0) 
                DFDF52 - Card Type Used

            F2<len>/* container for Batch Data */
            … /* Batch Data tags defined in DFDF17 */
            …/* Note: Sensitive Data cannot be defined in DFDF17*/

            F3<len>/* container for Reversal Data, if any */
            … /* Reversal Data tags defined in DFDF05 */
            …/* Note: Sensitive Data cannot be defined in DFDF05*/

            F7<len>/* container for Merchant Data */
            … /* < Merchant Data tags */

            F8<len>/* container tag for encrypted data */ 
                DFDF56(Encrypted Transaction Data KSN)<len><val> 
                DFDF57(Encrypted Transaction Data Encryption Type)<val>

            FA<len>/* container for generic data */ 
                DF30(Encrypted Tag 56 TLV, T1 Data)<len><val> 
                DF31(Encrypted Tag 57 TLV, T2 Data)<len><val> 
                DF32(Encrypted Tag 5A TLV, PAN)<len><val> 
                DF35(Encrypted Tag 9F1F TLV, T1 DD)<len><val> 
                DF36(Encrypted Tag 9F20 TLV, T2, DD)<len><val> 
                DF37(Encrypted Tag 9F61 TLV, T2 CVC3)<len><val>
                DF38(Encrypted Tag 9F62 TLV, T1,PCVC3)<len><val> 
                DF39(Encrypted Tag DF812A TLV, T1 DD)<len><val> 
                DF3A(Encrypted Tag DF812B TLV), T2 DD<len><val> 
                DF3B(Encrypted Tag DFDF4A TLV, T2 ISO Format)<len><val> 
                DF40(Encrypted Value only of DFDF4A, T2 ISO 
                Format)<len><val>

DFDF1A Transaction Status Return Codes

• 0x00 = Approved

• 0x01 = Declined

• 0x02 = Error

• 0x10 = Cancelled by Host

• 0x1E = Manual Selection Cancelled by Host

• 0x1F = Manual Selection Timeout

• 0x21 = Waiting for Card Cancelled by Host

• 0x22 = Waiting for Card Timeout

• 0x23 = Cancelled by Card Swipe

• 0xFF = Unknown

DynaPro Format:

Welcome to the resource hub for the Tap to Pay on iPhone API, a software-based solution that transforms a compatible iPhone into a secure contactless payment terminal. Leveraging the iPhone’s built-in NFC technology, it allows merchants to accept all forms of in-person contactless payments, including physical debit and credit cards, Apple Pay, and other digital wallets, without any additional hardware. Available through the MagTek Virtual Reader iOS SDK, this API is designed for developers to integrate directly into their own payment applications. This section provides all the documentation, software, and developer tools needed to successfully integrate, manage, and support the Tap to Pay on iPhone API within your iOS ecosystem.

Tap to Pay on iPhone API Support

For more help

The DynaFlex II Go is a portable secure card reader authenticator (SCRA) that reads contact chip, contactless (NFC), and magnetic-stripe cards in a compact, handheld device. It encrypts cardholder data at the point of read (SRED) and connects over USB or Bluetooth LE — suited to both mobile and countertop acceptance. It uses the shared Dyna-family MMS command set, so everything you build against it is documented in the and linked below.

• Contact, contactless (NFC), and magnetic stripe card reading in one device

• SRED point-to-point encryption at the moment of read (TDES / AES DUKPT)

This function retrieves the SDK revision number.

Parameters: None

Return Value: String containing the SDK revision number.

This function retrieves a list of available Bluetooth LE devices. After calling this function to locate the device you wish to connect to, use setAddress to tell the library which device you want to connect to. Use stopScanningForPeripherals to stop the scan.

Parameters: None

Return Value: An array of peripherals

This function stops the scanning of available Bluetooth LE devices.

Parameters: None Return Value: None

This function sets device’s address for Bluetooth LE devices.

Parameters:

To connect DynaMAX or eDynamo to a host with Windows 8.1 or higher and Bluetooth 4.0 hardware that supports Bluetooth LE, follow these steps:

• If you are using an external Bluetooth adapter, install any required drivers and connect it to the host.

• On the host, install and configure the software you intend to use with DynaMAX or eDynamo:

  1. Make sure the host software is configured to look for the device on the proper connection.

This function retrieves the card’s encrypted MagnePrint, for readers that support MagnePrint.

Parameters: None

Return Value: String containing the card’s encrypted MagnePrint.

This function retrieves the card MagnePrint status. For more information, see D99875475. Only available on iDynamo; it will return an empty string in audio reader.

Parameters: None Return Value:

Return stored MagnePrintStatus string.

This function retrieves the device serial number.

Parameters: None

Return Value: String containing the device serial number.

This function returns the MagTek serial number of the currently opened device.

Explore MagTek’s magnetic stripe readers, ranging from check readers to OEM swipe modules and USB peripherals. Resources here include product datasheets, SDKs for Windows, iOS, Android, and Linux, configuration utilities, and troubleshooting guides. Whether you’re deploying a single reader or integrating at scale, this page helps you get the most from your magnetic stripe hardware.

MMS notifications are the asynchronous messages the DynaFlex II PED reader sends while a transaction is running, reporting progress, state changes, and completion. Find the Notification Group you are looking for below and follow the links in the table to jump to a specific notification.

From Transactions - Source 0x01nn

MMS notifications are the asynchronous messages the DynaFlex II Go reader sends while a transaction is running, reporting progress, state changes, and completion. Find the Notification Group you are looking for below and follow the links in the table to jump to a specific notification.

From Transactions - Source 0x01nn

The DynaFlex II SCR is a compact, countertop secure card reader authenticator (SCRA) that reads contact chip, contactless (NFC), and magnetic-stripe cards and encrypts cardholder data at the point of read (SRED). It connects over USB and uses the shared DynaFamily MMS command set, so everything you build against it is documented in the API & Command Reference and linked below.

Key capabilities

• Contact, contactless (NFC), and magnetic stripe card reading in one device

• SRED point-to-point encryption at the moment of read (TDES / AES DUKPT)

• NFC/MIFARE pass-through and NFC card emulation (DynaCast)

• Optional barcode reader (BCR) for scanning outside a transaction

• Compact countertop secure card reader authenticator (SCRA)

• PCI PTS POI–approved SCRA for attended acceptance (no PIN entry — see the DynaFlex II PED for PIN debit)

Working with contactless cards and tags on the DynaFlex II SCR, the supported card technologies (NTag, MIFARE Ultralight, Classic, DESFire, Plus), how pass-through works, and NFC card emulation (DynaCast). This is shared DynaFamily content, documented once in the guide.

Pass-through Commands

How the DynaFlex II SCR protects cardholder data and manages keys. These are shared DynaFamily concepts, documented in the Guides Section:

Security & Key Guides

This page provides an overview of MagneSafe V5 Secure Card Reader Authenticators (SCRA), a family of encrypted card-reading devices that use MagnePrint® technology, strong encryption, and mutual authentication to securely capture, authenticate, and transmit cardholder data for payment and identity applications.

MagneSafe V5 SCRAs

For all DynaWave documentation, including programmer’s manuals, the technical reference manual, software/SDKs, and warranty info, please visit the official DynaWave Support Page:

DynaWave Support

For more help

These sections detail a variety of information on OIDs, codes, tips & taxes and more.

For all DynaPro Mini documentation, including programmer’s manuals, the technical reference manual, software/SDKs, and warranty info, please visit the official DynaPro Mini Support Page:

To connect via an interface listed in the Type box follow these steps:

• Connect the device to the USB port of the Windows PC.

• Launch the MTNET Demo, select USB as the device type in the Type list box, and press the Scan button to display a list of available devices.

• Select the Device ID and press the Connect button to open the device.