1 of 100

iDynamo 5 Gen III

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.

Get Started with My Device

Find Developer Resources & APIs

Download Software & Utilities

Review Compliance & Security Documents

Documentation

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.

Introduction

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.

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.

MTSCRA Class Methods

MTSCRA Class Methods - 21 - 30

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.

Get device model name.

public string getDeviceName()

Parameters: None

MTSCRA Class Methods - 31 - 40

Retrieves Track Capabilities.

public string getCapTracks()

Parameters: None Return Value:

String representing Track Capabilities:

Bit 0 = 1 / Track 1 supported,

Enums/Interfaces

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();

Commands

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.

Appendix B ARQC Message Format

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

Appendix C ARQC Response Message Format

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:

How to Connect to MTNET Demo

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.

How to use the MTNET OEM Demo via USB Interface

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

How to Set Up the MTSCRA SDK

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

Download the MTSCRA Demo app from MagTek.com.
Open your custom software project in XCode.
Open the MTSCRA Demo app folder in Finder.

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.

MTSCRA Functions

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.

MTSCRA Function - 4.21 - 4.30

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.

MTSCRA Function - 4.41 - 4.50

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

MTSCRA Delegate Methods

After issuing the methods in section 3 Important Information About Bluetooth LE, the MTSCRA SDK libraries will call these Delegate methods (callback functions) to provide the requested data and / or a detailed response. For details about data received by these functions, see the Programmer's Manual (COMMANDS) for the specific device with which you are communicating.

For details about registering Delegate methods, see the demo application included with the SDK.

Properties

Introduction

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 an Android device via the Audio/Headset Interface, Bluetooth, Bluetooth LE, or USB.

About the MagTek SCRA Demo

The MagTek SCRA Demo, available from MagTek, provides demonstration source code and a reusable MTSCRA library that provides developers of custom software solutions with an easy-to-use interface for Dynamag, DynaMAX, eDynamo, uDynamo, aDynamo, BulleT, mDynamo, DynaWave, tDynamo, iDynamo 6, DynaGlass, and iDynamo 5 (Gen III) readers. Developers can include the MTSCRA library in custom branded software which can be distributed to customers or distributed internally as part of an enterprise solution.

Nomenclature

The general terms “device” and “host” are used in different, often incompatible ways in a multitude of specifications and contexts. For example “host” may have different meanings in the context of USB communication than it does in the context of networked financial transaction processing. In this document, “device” and “host” are used strictly as follows:

Device refers to the reader device that receives and responds to the command set specified in this document.
Host refers to the piece of general-purpose electronic equipment the device is connected or paired to, which can send data to and receive data from the device. Host types include PC, laptops, tablets, smartphones, and even test harnesses. In many cases the host may have custom software installed on it that communicates with the device. When “host” must be used differently, it is qualified as something specific, such as “USB host.”

Development Environment: Eclipse 4.3 and above or Android Studio 3 and above.

Android Operating System: 4.4.2 and above

How to Set Up the MTSCRA Library for Projects

To add the MTSCRA library to a custom software project in the Eclipse development environment, follow these steps:

Create or open your custom software project in Eclipse.
Copy the following JAR file to the libs subfolder of your software project: mtscra.jar
Ensure your project settings are set up correctly.
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, see the source code included with the MagTek SCRA Demo project and/or the Code Examples section in this document.
Depending on the connection types supported, the project should include the uses-features and uses- permissions as specified in the table below in its AndroidManifest.xml file. For examples, see the AndroidManifest.xml included with the MagTek SCRA Demo project

MTSCRA Class Methods

MTSCRA Callback Messages

Commands

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

To send a command to device, use:

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.

Appendix A Code Examples

Open Device

Close Device

Get Connection Status Of Device

Receiving Card Data From Device

Send Command To Device

MTSCRA Functions

MTSCRA Delegate Methods

MagneFlex Browser WEB API Resources

How to Set Up

How to Set Up Headset Interface on Windows PC on Windows PC

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

Connect the device to the headset jack of the Windows PC.
Open the Windows Control Panel.
Open Sound
Select the Playback tab.S
Select the playback device that is connected to the SCRA device (for example, Speakers and Headphones).
Press the Properties button to launch the (device name) Properties tab.
Select the Levels tab
Set the volume to maximum. See Figure 3-1 for an example.
Select the Recording tab.
Select the headset interface that is connected to the SCRA device (for example, Headset Mic).
Press the Properties button to launch the (device name) Properties tab.
Select the Levels tab.
Turn any boost settings or other special volume settings completely off (for example, set Microphone Boost ) to 0.0dB). See Figure 3-2 for an example.
If the (device name) Properties window has and Enhancements tab, select it.
Make sure all checkboxes in the Enhancements tab are turned off. See Figure 3-3 for an example.
If the (device name) Properties window has an Effects tab, select it
If the Enhancements tab has a Disable System Effects checkbox, turn it ON. Turn all other effects off. See Figure 3-4 for an example.

Figure 3-1 Device Volume Level Set to 100

Figure 3-2 Microphone Boost Turned Off

Figure 3-3 Enhancements Turned Off

Figure 3-4 Effects Turned Off

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

Connect the device to the headset jack of the Windows Phone.
Adjust the audio output to the maximum level using the physical volume buttons of the Windows Phone.

To add the MagTek SCRA libraries to a .NET project in Microsoft Visual Studio, follow these steps:

Create or open your .NET project in Visual Studio.
Copy the following DLL files from the MTNETDemo folders to the library folder of your software project:
1. MTDevice.dll

In order to use the MagTek USB card readers with PID 0011, follow these steps:

Open Device Manager
Right Click on MagTek MagneSafe Magnetic Stripe Reader Device
Select Update Driver Software .

Select Browse My Computer for driver software .

Select Let me pick from a list of device drivers on my computer .

Select HiD-Compliant Device then click Next.

Windows will pop up a message saying successfully updated your driver. Click to finish.

MTSCRA Class Methods.

To add the MagTek SCRA libraries to a Universal Windows project in Microsoft Visual Studio, follow these steps:

Create or open your Universal Windows project in Visual Studio.
Copy the following DLL file from the SDK library folder to the library folder of your software project:
1. MTSCRAUWP.dll

In order to use the MagTek USB card readers with PID 0011, follow these steps:

Open Device Manager
Right Click on MagTek MagneSafe Magnetic Stripe Reader Device .
Select Update Driver Software .

Select Browse My Computer for driver software .

Select Let me pick from a list of device drivers on my computer .

Select Let me pick from a list of device drivers on my computer.

Select HiF-Compliant Device then click Next.

Windows will pop up a message saying successfully updated your driver. Click Close to finish.

The Critical Path from 3DES/TDEA DUKPT to AES DUKPT Encryption

DEVELOPER GUIDE

When is the right time to transition to AES DUKPT and what needs to be considered?

INITIAL CONSIDERATIONS

A Brief History

Since the 1970s the electronic payments and secure banking communities have strived to provide their customers with greater convenience, faster speeds, and improved security for electronic transactions. Throughout this timeline, the Open Standards Community, comprised of the International Standards Organization (ISO) and the American National Standards Institute (ANSI-X9), have led the way with the development of numerous security standards that have provided an open platform for proper implementation of accepted encryption and authentication methods. This platform was further augmented in 2007 when the PCI Security Standards council adopted these standards and provided a superset of additional guidance and requirements for PCI DSS.

Collectively, the Open Standards and PCI Security Standards communities have provided a trusted foundation for guiding the global implementation of accepted security methods for Electronic Payments and Secure Banking.

Paramount amongst these security standards has been defining the use of encryption and authentication technologies for the protection of customer PINs and payment data.

TDEA ENCRYPTION WITH DUKPT KEY MANAGEMENT

Since 1998, the use of Triple DES (3DES), also known as Triple Data Encryption Algorithm (TDEA), in combination with DUKPT Key Management (Derived Unique Key Per Transaction) has been the gold-standard for protection of PINs and payment data. To its credit, the TDEA DUKPT platform continues to serve its community well and has never yet suffered a “real world” security compromise.

That said, numerous universities and security labs have conducted research and published data that suggests the security capabilities of TDEA DUKPT may soon be challenged (and surpassed) by security threats from advanced computing platforms that will brute-force calculations at ever faster speeds (e.g., quantum computers). These threats may soon provide a viable path for attackers to “crack” the TDEA DUKPT level of security. To mitigate these threats, stronger encryption and authentication methods are required.

In anticipation of increased security threats to the TDEA DUKPT platform, the Open Standards community released a new set of improved security standards in 2017 that support AES DUKPT. (Reference: ANSI X9.24-3) The AES DUKPT standards provide a pathway to improved security features that are significantly stronger and more resistant to brute-force attacks. Specifically, these standards use the AES algorithm (Advanced Encryption Standard) in conjunction with an updated DUKPT specification. AES-128 DUKPT and AES-256 DUKPT are the new standards.

AES-128 uses crypto keys that are 128-bits in length and AES-256 uses crypto keys that are 256-bits in length. Both are far more secure than the existing TDEA DUKPT implementation that uses crypto keys that provide only 112-bits of key strength.

In the world of cryptography, each additional bit represents an order-of-magnitude improvement in security. The larger AES key sizes represent a significant improvement in encryption protection from attackers. In addition, the AES algorithm itself provides numerous security improvements for faster calculation speeds and reduces the possibilities of crypto-analysis side-channel attacks.

In addition to stronger AES encryption, CMAC (cipher-based message authentication code) authentication enhances the security of sensitive data. In this context, CMAC authentication is the cryptographic process of validating that the encrypted sensitive data has not been manipulated or altered from its original form. The authentication process begins within the trusted hardware reader device, where prior to AES encryption, the sensitive clear-text data has a cryptographic CMAC calculation applied to it using a secret MAC key. This results in a unique 6-digit CMAC checksum that is unique to the sensitive data.

The sensitive data is then AES encrypted within the hardware reader device and the CMAC checksum is included with the encrypted data packet that is transferred to a trusted decryption host. Upon receipt at the trusted decryption host, the sensitive data is both decrypted and CMAC validated to confirm that clear-text sensitive data is still in its original form and without alteration or compromise.

Combined, the use of AES DUKPT encryption in combination with CMAC data authentication provides a powerful “one-two punch” that ensures sensitive data remains protected and intact.

Planning your Roadmap

TDEA DUKPT is in its twilight era and needs to be replaced by the more secure AES DUKPT platform. The benefits of doing so are improved security and higher confidence that financial transaction data will remain safe for now and into the future.

To stay ahead of potential threats, PCI has been encouraging the electronic payments community to begin the migration from TDEA DUKPT to AES DUKPT to protect both PIN and payment data. Although no mandates have been made, the threat landscape is expanding, and the urgency to migrate towards more secure encryption is accelerating.

WHAT DATA DO I NEED TO PROTECT? WHAT PROTECTION SHOULD I USE?
- Ideally, to meet PCI DSS requirements, it is necessary to protect sensitive PAN (Personal Account Number) payment data and/or PIN (Personal Identification Number) data so that the clear-text sensitive data is never stored, transmitted, or available within the merchant’s payment systems. To do this, it is recommended to use AES DUKPT to protect this sensitive data.
IS THERE A REQUIREMENT TO AUTHENTICATE DATA?

After determining the data that needs to be protected and the best protection method, the next step is to determine how to build out the complete ecosystem including the customer environment, hardware, and services.

WHAT HARDWARE DO I NEED?
- To move to AES DUKPT encryption, you will need a card reader / PIN entry device (PED) that is specifically rated and approved to support AES DUKPT operations. Check the data sheet of your device or speak with the product support team from your vendor. Ideally, the device should be a “PCI Approved” device rated as “PCI 6.x” (or higher) and list AES support.
DO I NEED NEW KEYS?

Transitioning from TDEA DUKPT to AES DUKPT requires a plan and trusted partners. MagTek and Magensa have a complete solution of integrated hardware, services, and support to make this migration simple, fast, and painless. Partner with us today and let us show you how to migrate to a higher-security AES DUKPT platform that provides maximum data protection for your customers and your business.

Programmer's Manual (Android) Demo

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

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. MagnePrint® is a registered trademark of MagTek, Inc. MagneSafe® is a registered trademark of MagTek, Inc. Magensa™ is a trademark of MagTek, Inc.

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

mDynamo™, DynaWave™, and tDynamo™ 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.

Google Play™ store and Android™ platform are trademarks of Google Inc.

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.

Revisions

SOFTWARE LICENSE AGREEMENT

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.

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

MTSCRA Functions - 1 - 10

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 MTSCRA Demo how to use these functions, see the contents of the 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 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.

address Parameters:

Return Value: None

This function opens a connection to the device.

To use this function to connect to a Bluetooth LE device, the app should follow these steps:

Call startScanningForPeripherals to find the device you want to connect to.
Call setAddress to tell the library which device you want to connect to.
Make sure your app’s bleReaderStateUpdated function most recent status is was OK .

After calling this function, call isDeviceOpened to make sure the device was successfully opened.

Parameters: None Return Value:

YES = Success
NO = Error

This function closes the connection to the currently opened device. After calling this function, call isDeviceOpened to make sure the device was successfully closed.

Parameters: None

Return Value:

YES = Success
NO = Error

This function reports whether any compatible devices are connected to the host.

Parameters: None

Return Value:

YES = host is connected to a device
NO = host is not connected to a device

This function retrieves device opened status, which changes on successful completion of a call to startScanningForPeripherals or closeDevice.

(BOOL) isDeviceOpened

Parameters: None Return Value:

YES = Device is opened
NO = Device is not opened

This function sends a direct command to device. See D99875475 MagneSafe V5 Programmer’s Reference (Commands) for details about available commands and syntax.

Parameter

Return Value:

0 = Success
9 = Error
15 = Busy

This function retrieves card data from a string separated by ‘|’ after a cardholder swipes a card. The host software should call it in response to the trackDataReadyNotification callback.

Parameters: None

Return Value:

A null terminated hex string for Card Data, Field separated by ‘|’.NULL value for failed.

Fields:

Device ID, Device Serial Number, Card Swipe Status, CardEncode Type, Track 1 Decode Status, Track 2 Decode Status, Track 3 Decode Status, MagnePrint Status, Track 1 Length, Track 2 Length, Track 3 Length, Masked Track 1 Length, Masked Track 2 Length, Masked Track 3 Length, MagnePrint Length, Card Data, Masked Card Data, DUKPT Session ID, DUKPT Key Serial Number, First Name, Last Name, PAN, Month, Year, Track 1 Data, Track 2 Data, Track 3 Data, Masked Track 1 Data, Masked Track 2 Data, Masked Track 3 Data, MagnePrint Data

Appendix D Enums

Error Codes

ERROR_SUCCESS = 0

ERROR_TIMEOUT = 1

ERROR_DEVICE_NOT_OPEN = 5

ERROR_INVALID_PARAMETER = 6

ERROR_DEVICE_COMMUNICATION_ERROR = 7

ERROR_OTHER_ERROR = 9

ERROR_BUSY = 15

ERROR_DATA_IS_NOT_EXIST = 16

ERROR_NOT_SUPPORT = 17

ERROR_UNKNOWN = 255

MAGTEKAUDIOREADER = Audio readers aDynamo, uDynamo.

MAGTEKIDYNAMO = iOS 30-pin and Lightning readers iDynamo.

MAGTEKDYNAMAX = Bluetooth LE reader DynaMAX.

MAGTEKEDYNAMO = Bluetooth LE reader eDynamo

MAGTEKUSBMSR = USB on OSX Only

MAGTEKKDYNAMO = Lightning EMV reader kDynamo

MAGTEKTDYNAMO = Bluetooth LE reader tDynamo

MAGTEKDYNAWAVE= DynaWave

MAGTEKMDYNAMO = mDynamo

MAGTEKIDYNAMO_G3 = USB-C

iDynamo 5 Gen III MAGTEKNONE

TRANS_STATUS_OK = Transaction succeeded.

TRANS_STATUS_START = Reader started sending data.

TRANS_STATUS_ERROR = Reader failed sending data.

TRANS_EVENT_OK = Transaction succeeded.

TRANS_EVENT_ERROR = Reader failed sending data.

TRANS_EVENT_START = Reader started sending data.

TLV_OPSTS = Operation Status

TLV_CARDSTS = Card Information

TLV_TRACKSTS = Card tracks status

TLV_CARDNAME = Cardholder name

TLV_CARDIIN = Card issuer identification number

TLV_CARDLAST4 = Last four digits of PAN number

TLV_CARDEXPDATE = Card Expiration date

TLV_CARDSVCCODE = Card service code

TLV_CARDPANLEN = Length of the PAN

TLV_ENCTK1 = Encrypted track 1

TLV_ENCTK2 = Encrypted track 2

TLV_ENCTK3 = Encrypted track 3

TLV_DEVSN = Device serial number

TLV_DEVSNMAGTEK = Device serial number created by MagTek

TLV_DEVFW = Device firmware version

TLV_DEVNAME = Device model name

TLV_DEVCAPS = Device capabilities

TLV_DEVSTATUS = Device status

TLV_TLVVERSION = Firmware TLV version

TLV_DEVPARTNUMBER = Device part number

TLV_CAPMSR = Magstripe capabilities

TLV_CAPTRACKS = Track capabilities

TLV_CAPMAGSTRIPEENCRYPTION = Magstripe encryption capabilities

TLV_KSN = KSN

TLV_CMAC = CMAC

TLV_SWPCOUNT = Swipe count

TLV_BATTLEVEL = Battery level

TLV_CFGTLVVERSION = TLV version

TLV_CFGDISCOVERY = Discovery

TLV_CFGCARDNAME = Card name

TLV_CFGCARDIIN = Card issuer identification number

TLV_CFGCARDLAST4 = Card last 4 PAN

TLV_CFGCARDEXPDATE = Card expiration date

TLV_CFGCARDSVCCODE = Card service code

TLV_CFGCARDPANLEN = Card PAN length

TLV_MSKTK1 = Masked Track 1

TLV_MSKTK2 = Masked Track 2

TLV_MSKTK3 = Masked Track 3

TLV_HASHCODE = Hash code

TLV_SESSIONID = Session ID

TLV_MAGNEPRINT = MagnePrint

TLV_MAGNEPRINT_STS = MagnePrint status

CAP_MASKING = Masking

CAP_ENCRYPTION = Encryption

CAP_CARD_AUTH = Card authorization

CAP_DEVICE_AUTH = Device authorization

CAP_SESSION_ID = Session ID

CAP_DISCOVERY= Discovery

BLE = Bluetooth LE

BLE_EMV = Bluetooth LE EMV

USB = Universal Serial Bus Lightning = Lightning

NONE = None

Connection

CommandMessageData

CardMessageData

BLERawMessage

DeviceInfo

RawDataMessage

OFF

RESETTING

DISCONNECTED

UNSUPPORTED

UNAUTHORIZED

UNKNOWN

MTSCRA Class Methods - 1 - 10

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:

Parameter

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.

Programmer's Manual (Android)

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

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. DynaGlass™ is a trademark 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.

Android™ is a registered trademark of Google Inc.

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

Table 0-1 – Revisions

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.

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 event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.

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

MTSCRA Class Methods - 11 - 20

getTrack1

Get stored track1 data. This field contains the encrypted track data for track 1.

public string getTrack1()

Parameters: None Return Value:

Return stored track1 data string.

getTrack2

Get stored track2 data. This field contains the encrypted track data for track 2.

public string getTrack2()

Parameters: None Return Value:

Return stored track2 data string.

getTrack3

Get stored track3 data. This field contains the encrypted track data for track 3.

public string getTrack3 ()

Parameters: None Return Value:

Return stored track3 data string.

Get stored masked track1 data.

public string getTrack1Masked()

Parameters: None Return Value:

Return stored masked track1 data string.

For an ISO/ABA card, the PAN is masked as follows:

The specified number of initial characters is sent unmasked. The specified number of trailing characters is sent unmasked. If Mod 10 correction is specified, all but one of the intermediate characters of the PAN are set to zero; one of them will be set such that last digit of the PAN calculates an accurate Mod 10 check of the rest of the PAN as transmitted. If the Mod 10 correction is not specified, all of the intermediate characters of the PAN are set to the specified mask character.
The Card Holder’s name and the Expiration Date are transmitted unmasked.
All Field Separators are sent unmasked.

For an AAMVA card, the specified mask character is substituted for each of the characters read from the card.

Get stored masked track2 data.

public string getTrack2Masked()

Parameters: None Return Value:

Return stored masked track2 data string.

For an ISO/ABA card, the PAN is masked as follows:

The specified number of initial characters are sent unmasked. The specified number of trailing characters are sent unmasked. If Mod 10 correction is specified, all but one of the intermediate characters of the PAN are set to zero; one of them will be set such that last digit of the PAN calculates an accurate Mod 10 check of the rest of the PAN as transmitted. If the Mod 10 correction is not specified, all of the intermediate characters of the PAN are set to the specified mask character.
The Expiration Date is transmitted unmasked.
All Field Separators are sent unmasked.

For an AAMVA card, the DL/ID# is masked as follows:

The specified number of initial characters are sent unmasked. The specified number of trailing characters are sent unmasked. If Mod 10 correction is specified, all but one of the intermediate characters of the DL/ID#PAN are set to zero; one of them will be set such that last digit of the DL/ID# calculates an accurate Mod 10 check of the rest of the DL/ID# as transmitted. If the Mod 10 correction is not specified, all of the intermediate characters of the DL/ID# are set to the specified mask character.
The Expiration Date and Birth Date are transmitted unmasked.
All other characters are set to the specified mask character.

Get stored masked track3 data.

public string getTrack3Masked()

Parameters: None Return Value:

Return stored masked track3 data string.

For an ISO/ABA card, the PAN is masked as follows:

The specified number of initial characters are sent unmasked. The specified number of trailing characters are sent unmasked. If Mod 10 correction is specified, all but one of the intermediate characters of the PAN are set to zero; one of them will be set such that last digit of the PAN calculates an accurate Mod 10 check of the rest of the PAN as transmitted. If the Mod 10 correction is not specified, all of the intermediate characters of the PAN are set to the specified mask character.
All Field Separators are sent unmasked.
All other characters are set to the specified mask character.

For an AAMVA card, the specified mask character is substituted for each of the characters read from the card.

Supported on uDynamo only. This 128-byte Binary field contains the MagnePrint data. Only the number of bytes specified in the MagnePrint data length field are valid. The least significant bit of the first byte of data in this field corresponds to the first bit of MagnePrint data. If the Enable/Disable MagnePrint property is set to disable MagnePrint, this field will not be sent.

public string getMagnePrint()

Parameters: None

Return Value:

Return the MagnePrint data.

Supported on uDynamo only.

public string getMagnePrintStatus()

Parameters: None Return Value:

Returns the MagnePrint status.

This Binary field represents 32 bits of MagnePrint status information. Each character represents 4 bits (hexadecimal notation). For example, suppose the characters are: “A1050000”:

Usage Legend:

D = Direction
F = Too Fast
L = Too Slow
M = MagnePrint capable

This four-byte field contains the MagnePrint status. The MagnePrint status is in little endian byte order. Byte 1 is the least significant byte. Byte 1 LSB is status bit 0. Byte 4 MSB is status bit 31. MagnePrint status is defined as follows:

Bit 0 = MagnePrint-capable product (usage M)
Bits 1-15 = Product revision & mode (usage R)
Bit 16 = STATUS-only state (usage S)

If the Enable/Disable MagnePrint property is set to disable MagnePrint, this field will not be sent.

Get stored device serial number. This 16-byte ASCII field contains the device serial number. The device serial number is a NUL (zero) terminated string. So the maximum length of the device serial number, not including the null terminator, is 15 bytes. The device’s serial number can also be retrieved and set with the device serial number property explained in the property section of this document. This field is stored in non-volatile memory, so it will persist when the unit is power cycled.

public string getDeviceSerial()

Parameters: None Return Value:

Return stored device serial number.

Not suported on Audio Reader. This 8-byte Binary field contains the encrypted version of the current Session ID. Its primary purpose is to prevent replays. After a card is read, this property will be encrypted, along with the card data, and supplied as part of the transaction message. The clear text version of this will never be transmitted. To avoid replay, the application sets the Session ID property before a transaction and verifies that the Encrypted Session ID returned with card data decrypts to the value set.

public string getSessionID()

Parameters: None Return Value:

Return the Session ID

Programmer's Manual (iOS)

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

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.

IPAD® is a trademark of MagTek, Inc.

AAMVA™ is a trademark of AAMVA.

American Express® and EXPRESSPAY FROM AMERICAN EXPRESS® are registered trademarks of American Express Marketing & Development Corp.

D-PAYMENT APPLICATION SPECIFICATION® is a registered trademark to Discover Financial Services CORPORATION

MasterCard® is a registered trademark and PayPass™ and Tap & Go™ are trademarks of MasterCard International Incorporated.

Visa® and Visa payWave® are registered trademarks of Visa International Service Association.

ANSI®, the ANSI logo, and numerous other identifiers containing “ANSI” are registered trademarks, service marks, and accreditation marks of the American National Standards Institute (ANSI).

ISO® is a registered trademark of the International Organization for Standardization. UL™ and the UL logo are trademarks of UL LLC.

PCI Security Standards Council® is a registered trademark of the PCI Security Standards Council, LLC. 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.

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.

Apple Pay®, iPhone®, iPod®, Mac®, and OS X® are registered trademarks of Apple Inc., registered in the U.S. and other countries. iPad™ is a trademark of Apple. Inc. App Store^SM is a service mark of Apple Inc., registered in the U.S. and other countries. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple Inc. under license.

Microsoft®, Windows®, and .NET® are registered trademarks of Microsoft Corporation. All other system names and product names are the property of their respective owners.

Table 0-1 – Revisions

MagTek warrants that the products sold pursuant to this Agreement will perform in accordance with 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).

During the Warranty Period, should this product fail to conform to MagTek’s specifications, MagTek will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts and replacement products will be furnished on an exchange basis and will be either reconditioned or new. All replaced parts and products become the property of MagTek. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, unreasonable use, misuse, abuse, negligence, or modification of the product not authorized by MagTek. MagTek reserves the right to examine the alleged defective goods to determine whether the warranty is applicable.

Without limiting the generality of the foregoing, MagTek specifically disclaims any liability or warranty for goods resold in other than MagTek’s original packages, and for goods modified, altered, or treated without authorization by MagTek.

Service may be obtained by delivering the product during the warranty period to MagTek (1710 Apollo Court, Seal Beach, CA 90740). If this product is delivered by mail or by an equivalent shipping carrier, the customer agrees to insure the product or assume the risk of loss or damage in transit, to prepay shipping charges to the warranty service location, and to use the original shipping container or equivalent. MagTek will return the product, prepaid, via a three (3) day shipping service. A Return Material Authorization (“RMA”) number must accompany all returns. Buyers may obtain an RMA number by contacting MagTek Support Services at (888) 624-8350.

EACH BUYER UNDERSTANDS THAT THIS MAGTEK PRODUCT IS OFFERED AS-IS. MAGTEK MAKES NO OTHER WARRANTY, EXPRESS OR IMPLIED, AND MAGTEK DISCLAIMS ANY WARRANTY OF ANY OTHER KIND, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IF THIS PRODUCT DOES NOT CONFORM TO MAGTEK’S SPECIFICATIONS, THE SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT AS PROVIDED ABOVE. MAGTEK’S LIABILITY, IF ANY, SHALL IN NO EVENT EXCEED THE TOTAL AMOUNT PAID TO MAGTEK UNDER THIS AGREEMENT. IN NO EVENT WILL MAGTEK BE LIABLE TO THE BUYER FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF, OR INABILITY TO USE, SUCH PRODUCT, EVEN IF MAGTEK HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY.

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 OR IMPLIED, EXCEPT AS MAY BE STATED IN THIS AGREEMENT, AND MAGTEK DISCLAIMS ANY IMPLIED WARRANTY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

MAGTEK SHALL NOT BE LIABLE FOR CONTINGENT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES TO PERSONS OR PROPERTY. MAGTEK FURTHER LIMITS ITS LIABILITY OF ANY KIND WITH RESPECT TO THE PRODUCT, INCLUDING NEGLIGENCE ON ITS PART, TO THE CONTRACT PRICE FOR THE GOODS.

MAGTEK’S SOLE LIABILITY AND BUYER’S EXCLUSIVE REMEDIES ARE STATED IN THIS SECTION AND IN THE SECTION RELATING TO MAGTEK’S LIMITED WARRANTY.

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

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 event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.

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

DEMO SOFTWARE / SAMPLE CODE: Unless otherwise stated, all demo software and sample code are to be used by Licensee for demonstration purposes only and MAY NOT BE incorporated into any production or live environment. The PIN Pad sample implementation is for software PIN Pad test purposes only and is not PCI compliant. To meet PCI compliance in production or live environments, a third-party PCI compliant component (hardware or software-based) must be used.

Data Format

Multi-byte values like command and data lengths are always big-endian.

Message Types

Data

Data Messages are formed in response to a cardholder event such as swiping a card or pressing a button. These messages are formatted as a block of ASCII text and compatible with all interfaces.

Commands

Commands consist of a 2-byte command, a 2-byte Parameter Data Length, and Parameter Data as needed.

Table - Command Structure

Command

Parameter Data Len

Parameter Data

Responses consist of a 2-byte return code, a 2-byte response data length, and response data as needed.

Notifications consist of a 2-byte notification code, a 2-byte notification data length, and notification data when needed. They are sent asynchronously due to device events. They can also be used as delayed responses for commands that take longer to process.

Sentinels

Data for each card track is typically bracketed by a start and end sentinel. The sentinel characters can be changed by setting properties. The start sentinel can also indicate what format was used to encode the track.

[SS] Track Data [ES]

If a property value is set to 0, then no character will be sent.

Masking

The PAN field must always be partially masked. The device can be configured to expose the 0-8 leading characters and 0-4 trailing characters. The 8-digit limit for leading characters automatically drops to 6 for cards where the PAN length is less than 16 (e.g. American Express).

Properties 0x07 and 0x08 are used to configure PAN masking.

Data messages include DUKPT KEY information fields so the host can derive the correct decryption or MAC key.

Example:

Data messages will always be made up of ASCII text characters regardless of the interface for compatibility purposes. Text is used to address limitations when using keyboard emulation.

Any Field with no value will be empty between separator characters.

The device transmits an M002 message with three new data fields: Encrypted SCDE, KSN (SCDE) and DUKPT Key Info (SCDE) to the host instead of an M001 message when the following four conditions are satisfied. Selectable Card Data Encryption is enabled through Property 0x78.

Any of the defined property 0x78 bits are set to 1 (enabled),
Card Encode Type is ISO (a.k.a. financial card),
SCDE DUKPT key is injected or present in the device, and

If any one of the four conditions is not met, an M001 message will be returned to the host instead of an M002 message.

The encrypted SCDE field in the M002 message, [Encrypted SCDE], includes six data fields, field_1 ~ field_6. The six data fields are placed in a buffer prior to encryption. The selectable card data element starts with a field separator (FS) followed by a data field, and the last field separator is appended following the sixth data field (field_6) as shown below (total seven FS characters). The field separator used in the SCDE is the same FS used in the M001 or M002 message, which may be changed using Property 0x23.

Each data field in the SCDE is defined as follows.

The encrypted SCDE field in the M002 message is an encrypted blob holding six card data fields selected with Property 0x78 bits. If a defined bit is set to zero, the corresponding data field will be empty in the clear-text SCDE. The clear-text SCDE including enabled data fields will be encrypted with an SCDE DUKPT future key.

When all defined bits in the property 0x78 are set to zeros, the encrypted SCDE is disabled. As a result, the M001 message should be transmitted to the host instead of the M002 message.

Field Separation

This device uses configurable properties to define characters that get inserted into the message for parsing purposes. The simplest option is to have characters for start of message (SOM), end of message (EOM), and field separation (FS) only.

This is the message format for Qwantum cards, or for any card when Qwantum Mode is on.

This message is used when the device sends out encrypted data from the Secure Buffer.

This message is used when the device sends out when Qwantum Secure Data is empty.

iDynamo 5 Gen III

Get Started with My Device

Find Developer Resources & APIs

Download Software & Utilities

Review Compliance & Security Documents

Documentation

Introduction

MTSCRA Class Methods

MTSCRA Class Methods - 21 - 30

MTSCRA Class Methods - 31 - 40

Enums/Interfaces

IMTCardData

Commands

Discovery

Appendix B ARQC Message Format

Appendix C ARQC Response Message Format

How to Connect to MTNET Demo

How to use the MTNET OEM Demo via USB Interface

How to Set Up the MTSCRA SDK

Important Information About Bluetooth LE

Important Information About Bluetooth LE

MTSCRA Functions

MTSCRA Function - 4.21 - 4.30

MTSCRA Function - 4.41 - 4.50

MTSCRA Delegate Methods

Properties

Introduction

About the MagTek SCRA Demo

Nomenclature

How to Set Up the MTSCRA Library for Projects

MTSCRA Class Methods

MTSCRA Callback Messages

Commands

Appendix A Code Examples

Open Device

Close Device

Get Connection Status Of Device

Receiving Card Data From Device

Send Command To Device

MTSCRA Functions

MTSCRA Delegate Methods

MagneFlex Browser WEB API Resources

MTSCRA Delegate Methods

Properties

MTSCRA Class Methods

MTSCRA Class Methods

MTSCRA Functions

iDynamo 5 Gen III

Get Started with My Device

Find Developer Resources & APIs

Download Software & Utilities

Review Compliance & Security Documents

Introduction

Appendix C ARQC Response Message Format

MTSCRA Functions

About MTSCRA Library

How to Set Up the MTSCRA Library for Projects

MTSCRA Delegate Methods

MTSCRA Callback Messages

MagneFlex Browser WEB API Resources

Appendix B ARQC Message Format

Important Information About Bluetooth LE

Important Information About Bluetooth LE

Introduction

About the MagTek SCRA Demo

Nomenclature

Commands

Discovery

Documentation

MTSCRA Function - 4.21 - 4.30

MTSCRA Function - 4.41 - 4.50

MTSCRA Class Methods - 21 - 30

How to use the MTNET OEM Demo via USB Interface

How to Set Up the MTSCRA SDK

Commands

MTSCRA Class Methods - 31 - 40

How to Connect to MTNET Demo

SDK Contents

System Requirements

Enums/Interfaces