Products is the directory of MagTek reader hubs. Find your device to reach its quickstart, its firmware, downloads, and compliance, and its links into the shared guides and command reference and other support materials.

​​DynaFamily (MMS Dyna Devices)

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 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.

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

Connect via USB Interface

• 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.

• Pair the device to the Windows PC.

• Launch the MTNET Demo and select either Bluetooth LC, Bluetooth LE EMV, or Bluetooth LE EMVT ass the device type in the devices. Type list box, press the Scan button to display a list of available devices.

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

• Pair the device to the Windows PC.

• Launch the MTNET Demo and select Serial button to display type in the Type list box, press the Scan button to display a list of available Ports

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

Secure Card Reader Authenticator

Programmer’s Manual ( .NET/Universal Windows )

REGISTERED TO ISO 9001:2015

MagTek I 1710 Apollo Court I Seal Beach, CA 90740 I Phone: (562) 546-6400 I Technical Support: (888) 624-8350 www.magtek.com

Copyright © 2006-2025 MagTek, Inc. Printed in the United States of America

Information in this publication is subject to change without notice and may contain technical inaccuracies or graphical discrepancies. Changes or improvements made to this product will be updated in the next publication release. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of MagTek, Inc.

MagTek® is a registered trademark of MagTek, Inc. MagneSafe® is a registered trademark of MagTek, Inc. iDynamo™, and uDynamo are trademarks of MagTek, Inc.

eDynamo™, Dynamag, and DynaMAX are trademarks of MagTek, Inc.

The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by MagTek is under license.

Microsoft®, Windows® and .NET® are registered trademarks of Microsoft Corporation.

EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC. The Contactless Indicator mark, consisting of four graduating arcs, is a trademark owned by and used with permission of EMVCo, LLC.

All other system names and product names are the property of their respective owners.

Table 1.1 Revisions

IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO THE ADDRESS ON THE FRONT PAGE OF THIS DOCUMENT, ATTENTION: CUSTOMER 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. LICENSEE MAY NOT COPY, MODIFY, OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT. Licensee

may not decompile, disassemble, or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with, bypass, or alter any security features of the software or attempt to do so.

TRANSFER: Licensee may not transfer the Software or license to the Software to another party without the prior written authorization of the Licensor. If Licensee transfers the Software without authorization, all rights granted under this Agreement are automatically terminated.

COPYRIGHT: The Software is copyrighted. Licensee may not copy the Software except for archival purposes or to load for execution purposes. All other copies of the Software are in violation of this Agreement.

TERM: This Agreement is in effect as long as Licensee continues the use of the Software. The Licensor also reserves the right to terminate this Agreement if Licensee fails to comply with any of the terms, conditions, or restrictions contained herein. Should Licensor terminate this Agreement due to Licensee's failure to comply, Licensee agrees to return the Software to Licensor. Receipt of returned Software by the Licensor shall mark the termination.

LIMITED WARRANTY: Licensor warrants to the Licensee that the disk(s) or other media on which the Software is recorded are free from defects in material or workmanship under normal use.

THE SOFTWARE IS PROVIDED AS IS. LICENSOR MAKES NO OTHER WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Because of the diversity of conditions and PC hardware under which the Software may be used, Licensor does not warrant that the Software will meet Licensee specifications or that the operation of the Software will be uninterrupted or free of errors.

IN NO EVENT WILL LICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE, THE SOFTWARE. Licensee's sole remedy in the event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.

GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void, or unenforceable, that provision shall be removed from consideration under this 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.

ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT HE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS, AND RESTRICTIONS, AND AGREES TO BE BOUND BY THEM. LICENSEE ALSO AGREES THAT THIS AGREEMENT SUPERSEDES ANY AND ALL VERBAL AND WRITTEN COMMUNICATIONS BETWEEN LICENSOR AND LICENSEE OR THEIR ASSIGNS RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT.

QUESTIONS REGARDING THIS AGREEMENT SHOULD BE ADDRESSED IN WRITING TO MAGTEK, INCORPORATED, ATTENTION: CUSTOMER SUPPORT, AT THE ADDRESS LISTED IN THIS DOCUMENT, OR E-MAILED TO

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.

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 section gives the format of the ARQC Message delivered in the ARQC Message notification. 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:

FD<len>/* container for generic data */ 
    DFDF25(IFD Serial Number)<len><val> 
    FA<len>/* container for generic data */
        <tags defined by DFDF02 >
            . Note: Sensitive Data cannot be defined in DFDF02
            .
        DFDF4D(Masked T2 ICC Data) 
        DFDF52 - Card Type Used
        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>

DynaPro Format:

The Value inside tag DFDF59 is encrypted and contains the following after decryption:

                FC<len>/* container for encrypted generic data */
                                <tags defined by DFDF02 >
                                .

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.

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:

This document provides instructions for software developers who want to create custom software solutions that communicate with DynaMAX, eDynamo, aDynamo, iDynamo, uDynamo, kDynamo, sDynamo, tDynamo, iDynamo 5 Gen II, iDynamo 5 Gen III, or iDynamo 6 connected to an iOS host via audio connector or Bluetooth LE. It is part of a larger library of documents which includes:

• MagneSafe V5 Programmer’s Reference (Commands)

• DynaMAX Programmer's Manual (Commands)

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:

• 0x00 = Approved

• 0x01 = Declined

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.

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:

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.

This document provides instructions for software developers who want to create software solutions that include a MagTek Secure Card Reader / Authenticator (SCRA) device connected to a Windows PC, Windows tablet device or Windows Phone mobile device.

About MTSCRA Library

Custom Windows software installed on a host PC can communicate with MagTek SCRA devices via the Audio/Headset Interface, Bluetooth, Bluetooth LE, or USB using the MTSCRA library.

The supported platforms for .NET projects include Windows 7, Windows 8/8.1, and Windows 10. The

.NET project should contain references to these files: MTSCRANET.dll and MTLIB.dll.

For Universal Windows projects, the supported platforms include all Windows 10 devices. The Universal/Windows Store project should contain references to MTSCRAUWP.dll file.

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

Important Information About Bluetooth LE

• 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.

• Make sure device is in pairing mode. If not, press and hold the button for 3 seconds until the blue light blinks, and then release the button.

• Set device type and connection type.

• Wait for callback bleReaderStateUpdated(), and then call startScanningForPeripheral().

• Wait for onDeviceList() callback. Here you can call getDiscoveredPeripherals().

• Select the device in the list.

• Open the device you want to connect.

• Library will pair the device. After inputting passcode, device is ready to use.

The DynaFlex Family resource hub provides documentation, software, and developer tools for a line of PCI PTS POI certified Secure Card Reader Authenticators (SCRAs) designed for modern, omni‑channel payment environments. The family includes the base DynaFlex, the DynaFlex Pro with a color touchscreen display, and the DynaFlex BCR with barcode scanning, all of which accept magnetic stripe, EMV® contact chip, EMV contactless, and NFC contactless payments (Apple Pay®, Google Pay™, Samsung Pay®) along with 1D/2D barcode scanning. Connectivity options include USB, Bluetooth® LE, and 802.11 wireless networking, all backed by MagTek’s MagneSafe® Security Architecture with AES‑256 encryption and DUKPT key management.

4.11 clearBuffers

This function clears the SDK library’s local cache of card swipe data.

(void) clearBuffers

Parameters: None

Return Value: None

4.12 listenForEvents

This function sets a callback function to notify when the device has card data to send to the host or when the device state changes. See example in Open Device code example.

(void) listenForEvents:(UInt32)event

Parameters: Event

Return Value: None

This function retrieves masked card track data after a cardholder swipes a card. Only available on iDynamo/uDynamo; other devices will return an empty string.

Parameters: None

Return Value:

Return stored masked track data string. Tracks are delimited with start and end sentinels.

This function retrieves masked track 1 data after a cardholder swipes a card.

Parameters: None

Return Value: Return stored masked track1 data string.

This function retrieves masked track 2 data, if any, after a cardholder swipes a card.

Parameters: None

Return Value: Return stored masked track2 data string.

This function retrieves masked track 3 data, if any, after a cardholder swipes a card.

Parameters: None

Return Value: Return stored masked track3 data string.

This function retrieves masked PAN data, if any, after a cardholder swipes a card.

Parameters: None

Return Value: Return stored masked PAN data string.

This function retrieves the card’s track 1 data in encrypted format after a cardholder swipes a card.

Parameters: None

Return Value: String containing encrypted track 1 data.

This function retrieves the card’s track 2 data in encrypted format, if any, after a cardholder swipes a card.

Parameters: None

Return Value: String containing encrypted track 2 data.

This function retrieves the card’s track 3 data in encrypted format, if any, after a cardholder swipes a card.

Parameters: None

Return Value: String containing encrypted track 3 data

Document Number: D99875568-133

REGISTERED TO ISO 9001:2015

MagTek I 1710 Apollo Court I Seal Beach, CA 90740 I Phone: (562) 546-6400 I Technical Support: (888) 624-8350

Copyright © 2006 – 2025 MagTek, Inc. Printed in the United States of America

INFORMATION IN THIS PUBLICATION IS SUBJECT TO CHANGE WITHOUT NOTICE AND MAY CONTAIN TECHNICAL INACCURACIES OR GRAPHICAL DISCREPANCIES. CHANGES OR IMPROVEMENTS MADE TO THIS PRODUCT WILL BE UPDATED IN THE NEXT PUBLICATION RELEASE. NO PART OF THIS DOCUMENT MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS, ELECTRONIC OR MECHANICAL, FOR ANY PURPOSE, WITHOUT THE EXPRESS WRITTEN PERMISSION OF MAGTEK, INC.

MagTek®, MagnePrint®, and MagneSafe® are registered trademarks of MagTek, Inc. Magensa™ is a trademark of MagTek, Inc.

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

IMTCardData

public interface IMTCardData

{

public byte[] getData();

public String getMaskedTracks(); public String getTrack1();

public String getTrack2(); public String getTrack3();

public String getTrack1Masked(); public String getTrack2Masked(); public String getTrack3Masked(); public String getMagnePrint(); public String getMagnePrintStatus(); public String getDeviceSerial(); public String getSessionID();

public String getKSN();

public String getDeviceName(); public void clearBuffers(); public long getBatteryLevel(); public long getSwipeCount();

public String getCapMagnePrint();

public String getCapMagnePrintEncryption(); public String getCapMagneSafe20Encryption(); public String getCapMagStripeEncryption(); public String getCapMSR();

public String getCapTracks(); public long getCardDataCRC(); public String getCardExpDate(); public String getCardIIN(); public String getCardLast4(); public String getCardName(); public String getCardPAN(); public int getCardPANLength();

public String getCardServiceCode(); public String getCardStatus(); public int getDataFieldCount(); public String getHashCode();

public String getDeviceConfig(String configType); public String getEncryptionStatus();

public String getFirmware();

public String getMagTekDeviceSerial(); public String getResponseType();

public String getTagValue(String tag, String data); public String getTLVVersion();

public String getTrackDecodeStatus();

public String getTLVPayload();

public String getMessageID(); public boolean isQwantumCard(); public boolean isQwantumBuffer();

public boolean isCustomerMessage();

String getMSRDUKPTKeySerialNumber(); String getMSRDUKPTKeyInfo();

String getMPDUKPTKeySerialNumber(); String getMPDUKPTKeyInfo();

public String getTokenDUKPTKeySerialNumber(); public String getTokenDUKPTKeyInfo();

public String getQwantumStatus(); public String getQwantumToken(); public String getQwantumCardID();

public String getEncryptedQwantumDataBuffer(); public String getMACDUKPTKeyInfo();

public String getMACMessageLength(); public String getMAC();

public String getCustomerMessageCode(); public String getCustomerMessageText();

public String getEncryptedSCDE();

public String getSCDEDUKPTKeySerialNumber(); public String getSCDEDUKPTKeyInfo();

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)

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 page provides access to the essential software resources for developing with and managing the DynaFlex II PED secure card reader. Here you will find Software Development Kits (SDKs) for integrating the device into applications across Android, iOS, and Windows platforms. Additionally, you can download utility programs for device demonstration and configuration, as well as specialized browser applications and the Reader Management System (RMS) for remote, large-scale device management.

Firmware

This compliance documentation page provides the essential security and inspection guides required to maintain PCI PTS POI approval and ensure the physical integrity of DynaFlex II PED secure card readers before and after deployment.

Documents

Every exchange with the DynaFlex II SCR — 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 Dyna-family readers and is documented once in the shared reference.

Settings & Information - Group 0xD1nn

For all tDynamo (Gen I, II) documentation, including programmer’s manuals, the technical reference manual, software/SDKs, and warranty info, please visit the official tDynamo (Gen I, II) Support Page:

tDynamo (Gen I, II) Support

For more help

Retrieves Track Capabilities.

public string getCapTracks()

Parameters: None Return Value:

String representing Track Capabilities:

• Bit 0 = 1 / Track 1 supported,

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:

DynaPro format:

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.

Key Documents

Document Categories

This page provides access to the essential software resources for developing with and managing the DynaProx secure card reader. Here you will find Software Development Kits (SDKs) for integrating the device into applications across Android, iOS, and Windows platforms. Additionally, you can download utility programs for device demonstration and configuration, as well as specialized browser applications and the Reader Management System (RMS) for remote, large-scale device management.

Firmware

The following instructions detail how to use the MTNET Demo on Windows PC via USB interface. Same instructions apply to the other interface types.

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

• 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.

• Swipe a magnetic stripe card to read the card data.

• If you want to send a command to the device, enter the command in the command text box and press the Send button.

• To retrieve device information, press the Device Info button

• To set the MSR On for the device, press the Set MSR On button.

• To set the MSR Off for the device, press the SET MSR off button. Device will not send card data after swiping a magnetic stripe card but will during an EMV transaction.

• To configure the current PC date and time in devices which require a Date/Time be set after power up, press the Set Time button before performing an EMV transaction.

• To retrieve the battery level of the device, press the Battery button. Note: When powered by USB, the level returns as 100%.

• If you have an EMV device and want to read a chip card, select from the Transaction Types, Response, Options, Timeout, and then press the Start button to begin an EMV transaction

• If you want to cancel the EMV transaction, press the only work before the card is presented.

• To clear the screen, press the Clear button.

• To close the device, press the Disconnect button.

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

Security & Key Guides

To set up the headset interface on Windows PC to communicate with the MagTek SCRA device, follow these steps:

1. Connect the device to the headset jack of the Windows PC.

2. Open the Windows Control Panel.

3. Open Sound

To request a list of devices:

1. Create an MTSCRANET.MTSCRA object.

2. Set the connection type with setConnectionType().

3. Add a handler for OnDeviceList().

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.

• 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)

Working with contactless cards and tags on the DynaFlex II PED, 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.

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

This compliance documentation page provides the essential security and inspection guides required to maintain PCI PTS POI approval and ensure the physical integrity of DynaFlex II SCR secure card readers before and after deployment.