1 of 100

Card Readers

This section covers MagTek’s complete family of card readers, from compact OEM modules to rugged handheld devices. Use the links below to dive into specific categories including: MMS Dyna Devices, MagTek Virtual Readers, and MagneSafe V5 SCRAs. Here you’ll find product manuals, technical specifications, firmware updates, and integration guides to help you select, configure, or build solutions around MagTek reader technology.

Card Readers

Product

Description

MagTek Virtual Reader iOS SDK

Tap to Pay on iPhone API

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.

MagneSafe V5 SCRAs

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

MagneSafe V5 SCRAs

Product

Description

Programmer’s manuals, software/SDKs, and compliance documents for the iDynamo 6 secure card reader authenticator that accepts magnetic stripe, EMV contact, and optional NFC contactless payments.

iDynamo 6

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

tDynamo (Gen I, II)

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:

DynaWave

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

DynaPro Mini

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

uDynamo

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

Magnetic Stripe Readers

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

iDynamo 5 (Gen I,II)

iDynamo 5 (Gen I,II) has reached the end-of-life status. The part numbers affected include all iDynamo 5 (Gen I,II) devices:

Part numbers:

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

iDynamo 5 (Gen I,II) Support

For more help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

📧 Email:

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.

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.

MTSCRA Class Methods

MTSCRA Class Methods - 21 - 30

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.

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

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

Commands

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

To send a Discovery 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.

Device SN, MagTek: Device serial number created by MagTek. Use getDeviceSerialMagTek 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:

DynaPro Format:

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

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:

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

DynaPro format:

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

Appendix D Batch Data Format

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

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.

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

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.

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.

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:

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

MTSCRA Class Methods

MTSCRA Callback Messages

MTSCRA Functions

MTSCRA Interfaces

1.1 MTCardData

@interface MTCardData : NSObject

- (id)initWithCardData:(NSString*)cardData;

/*!

@attribute cardIIN

@discussion cardIIN is 6 digits of the account, usually can help to identify the issuer

@property(nonatomic, strong) NSString *cardIIN;

/*!

@attribute cardData

@discussion track1 | track2 | track3

@property(nonatomic, strong) NSString *cardData;

/*!

@attribute cardLast4

@discussion last 4 digits of account, usually can help user to identify him/her self

@property(nonatomic, strong) NSString *cardLast4;

/*!

@attribute cardName @discussion card holder name

@property(nonatomic, strong) NSString *cardName;

@property (strong, nonatomic) NSString *cardLastName;

@property (strong, nonatomic) NSString *cardMiddleName;

@property (strong, nonatomic) NSString *cardFirstName;

@property(nonatomic, strong) NSString *cardExpDate;

@property(nonatomic, strong) NSString *cardServiceCode;

@property(nonatomic, strong) NSString *cardStatus;

@property(nonatomic, strong) NSString *responseData;

@property(nonatomic, strong) NSString *maskedTracks;

@property(nonatomic, strong) NSString *encryptedTrack1;

@property(nonatomic, strong) NSString *encryptedTrack2;

@property(nonatomic, strong) NSString *encryptedTrack3;

@property(nonatomic, strong) NSString *encryptionStatus;

@property(nonatomic, strong) NSString *maskedTrack1;

@property(nonatomic, strong) NSString *maskedTrack2;

@property(nonatomic, strong) NSString *maskedTrack3;

@property(nonatomic, strong) NSString *trackDecodeStatus;

@property(nonatomic, strong) NSString *encryptedMagneprint;

@property(nonatomic, strong) NSString *magneprintStatus;

@property(nonatomic, strong) NSString *deviceSerialNumber;

@property(nonatomic, strong) NSString *deviceSerialNumberMagTek;

@property(nonatomic, strong) NSString *encrypedSessionID;

/*!

@attribute deviceKSN

@discussion Key Serial Number for the card swipe

@property(nonatomic, strong) NSString *deviceKSN;

@property(nonatomic, strong) NSString *deviceFirmware;

@property(nonatomic, strong) NSString *deviceName;

@property(nonatomic, strong) NSString *deviceCaps;

@property(nonatomic, strong) NSString *deviceStatus;

@property(nonatomic, strong) NSString *tlvVersion;

@property(nonatomic, strong) NSString *devicePartNumber;

@property(nonatomic, strong) NSString *capMSR;

@property(nonatomic, strong) NSString *capTracks;

@property(nonatomic, strong) NSString *capMagStripeEncryption;

@property(nonatomic, strong) NSString *maskedPAN;

@property(nonatomic) long cardPANLength;

@property(nonatomic, strong) NSString *additionalInfoTrack1;

@property(nonatomic, strong) NSString *additionalInfoTrack2;

@property(nonatomic, strong) NSString *responseType;

@property(nonatomic) long batteryLevel;

@property(nonatomic) long swipeCount;

@property(nonatomic, strong) NSString *firmware;

@property(nonatomic, strong) NSString *tagValue;

@property(nonatomic) int magnePrintLength;

@property(nonatomic) int cardType;

@property(nonatomic, strong) NSString *cardExpDateMonth;

@property(nonatomic, strong) NSString *cardExpDateYear;

@property(nonatomic, strong) NSString *cardPAN;

@property(nonatomic, strong) NSString *track1DecodeStatus;

@property(nonatomic, strong) NSString *track2DecodeStatus;

@property(nonatomic, strong) NSString *track3DecodeStatus;

@property(nonatomic, strong) NSDate* timeStamp;

@property(nonatomic, strong) NSString* messageID;

@property(nonatomic, strong) NSString* msrDUKPTKeyInfo; // 16 bytes

@property(nonatomic, strong) NSString* mpDUKPTKeySerialNumber; // 0/20/24 @property(nonatomic, strong) NSString* mpDUKPTKeyInfo; // 16 bytes

@property(nonatomic, strong) NSString* macKeyInfo; // 16 bytes

@property(nonatomic, strong) NSString* macMessageLength;

@property(nonatomic, strong) NSString* mac;

@property(nonatomic, strong) NSString* tokenDUKPTKeyInfo;

@property(nonatomic, strong) NSString* tokenDUKPTKeySerialNumber;

@property(nonatomic, strong) NSString* encryptedQwantumDataBuffer;

@property(nonatomic, strong) NSString* qwantumStatus;

@property(nonatomic, strong) NSString* qwantumToken;

@property(nonatomic, strong) NSString* qwantumCardID;

@property(nonatomic, strong) NSString* customerMessageCode;

@property(nonatomic, strong) NSString* customerMessage;

@property(nonatomic) BOOL isQwantumCard;

@property(nonatomic) BOOL isQwantumBuffer;

@property(nonatomic) BOOL isCustomerMessage;

@property(nonatomic, strong) NSString* encryptedSCDE;

@property(nonatomic, strong) NSString* scdeDUKPTKeySerialNumber;

@property(nonatomic, strong) NSString* scdeDUKPTKeyInfo;

@property(nonatomic, strong) NSDictionary* allObjects;

@property(nonatomic, strong) NSArray<NSString*>* objectArray;

@end

Programmer's Manual (.Net) Demo Guide

Manual Part Number: D998200163-100

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. MagneSafe® is a registered trademark of MagTek, Inc. iDynamo™, and uDynamo are trademarks of MagTek, Inc.

eDynamo™, Dynamag, DynaMAX and DynaDip 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 0.1 - 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."

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 Function - 4.1 - 4.10

4.1 getSDKVersion

This function retrieves the SDK revision number.

(NSString *) getSDKVersion

Parameters: None

Return Value: String containing the SDK revision number.

4.2 startScanningForPeripherals

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.

(void)startScanningForPeripherals

Parameters: None

Return Value: An array of peripherals

4.3 stopScanningForPeripherals

This function stops the scanning of available Bluetooth LE devices.

(void)stopScanningForPeripherals

Parameters: None Return Value: None

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

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.

Parameters: None

Return Value:

YES = Device is opened
NO = Device is not opened

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

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

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

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.

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

Revisions

SOFTWARE LICENSE AGREEMENT

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.

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.

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

Programmer's Manual (.NET/PCL)

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

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.

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

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

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.

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

How to use the MagTek SCRA OEM Demo

This section describes how to use the MagTek SCRA OEM Demo on an Android host. Some peripherals are not included in every MagTek OEM device. Use each feature of the Demo accordingly.

Connecting to a MagTek SCRA OEM Device

Connect the MagTek SCRA OEM device to the Android host USB port using an OTG cable.
Press on MagTek SCRA OEM Demo to launch the app.

To start the process of connecting, press on Connect .

Select the appropriate peripheral connected to the MagTek SCRA OEM device’s SPI Port and UART Port, and then press on Connect .

Approve any prompts for allowing the app to access the USB device by pressing on OK .

To disconnect the MagTek SCRA OEM device, press the red X at the top of the app.

To begin the process of sending a command to the device, press on Send at the top of the app.

Select which interface the command is to be sent to:
- Board: Commands to the main board chip peripheral.
- UAER: Commands to NFC contactless peripheral.

Enter the command under Custom Command , then press on Send.

Sent commands and device responses are displayed similarly as below.

To clear the display, press on Clear at the top of the app.

To begin the process of starting an EMV transaction, press on EMV at the top of the app.

Select the transaction approval type:
- Approved: On for approval response code. Off for decline response code.
- Quick Chip: On to transact only an Acquirer Request Cryptogram (ARQC). Off to transact both ARQC and Acquirer Response Code (ARPC.

MagTek SCRA OEM devices and peripherals not equipped with batteries will need to have their time set on each USB connection to the Android host device. This step is needed only once until there is a power cycle or reset of the MagTek SCRA OEM device. Set the time according to which peripheral is to be used for the transaction:
- Set Time: For the main board chip transaction.
- Set Time [UART]: For NFC contactless transaction.

Select one of the card types for the transaction:
- Start Chip Transaction: for chip cards only.
- Start Contactless: for contactless only.

Present the card to the device.

Follow the prompts for selecting any languages and applications to complete the transaction. The result will be displayed similar as below.

To cancel a transacion, press EMV at the top of the app and press Cancel Transaction. A transaction may only be canceled before a card is presented.

This section describes the get, set, and commit commands for terminal configuration on the device.

Get – retrieves the terminal configuration.
Set – sets the terminal configuration. Changes do not remain after device power cycle or reset.
Commit – is used to store configuration changes to non-volatile memory to remain in place after a power cycle or reset.

To access the device’s terminal configuration, press at the top of the app and select Configuration.

To get the devices terminal configuration, select Get Terminal Config . The value will be displayed similar as below.

To set the devices terminal configuration, select Set Terminal Config . The value will be displayed similar as below. Setting the Terminal Configuration requires an authenticated message unique to each device, so in the MagTek SCRA OEM Demo the response will indicate an invalid serial number or invalid MAC.

To commit the devices terminal configuration, select Commit Config . The value will be displayed similar as below.

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.

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.

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:

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.

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.

setConnectionType

This method sets the connection type of the device.

public void setConnectionType(MTConnectionType connectionType)

Parameters:

Parameter

Description

connectionType

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

Return Value: None

This function when set to True instructs the SDK to automatically retry to connect to the Bluetooth LE reader upon pairing. If set to False, the Bluetooth LE reader will be disconnected after pairing. This function is set to False by default in the SDK, but MagTek highly recommends to set this flag to True in your application in order to make sure that you'll have a successful secure connection between Android OS and Bluetooth LE reader after the paring.

Parameters:

Return Value: None

This method sets the address of the device.

Parameters:

Return Value: None

This method sets the configuration parameters for the device.

Parameters:

Return Value: None

This method opens connection to the device.

Parameters: None

Return Value: None

This method closes the connection to the device.

Parameters: None

Return Value: None

This method returns whether the device is connected or not.

Parameters: None

Return Value:

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

This method returns whether the device supports EMV or not.

Parameters: None

Return Value:

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

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 D99875475 for the ISO Track Masking property and the AAMVA Track Masking property for more information. See D99875475 for a description on how ISO/ABA and AAMVA cards are identified.

Parameters: None

Return Value:

Return stored masked tracks data string.

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.

How to use the MagTek SCRA Demo

This section describes how to use the MagTek SCRA Demo on an Android host. Some peripherals are not included in every MagTek SCRA device, so use each feature of the Demo accordingly.

Connecting via USB OTG

This section describes how to use the MagTek SCRA Demo with a SCRA Device such as Dynamag, DynaMAX, eDynamo, mDynamo, BulleT, uDynamo, tDynamo, and DynaWave, iDynamo 5 (Gen III) connected to an Android host via USB OTG cable. Please note that the Android host must have USB OTG support to use this connection type.

Connect the MagTek SCRA device to the Android host USB port using an OTG cable.
Press on MagTek SCRA Demo to launch the app.

Connect a SCRA Device via USB OTG cable, then select USB in the menu.

If the device is Serial with a USB OTG cable, press on the device selector to the right of USB, then select Serial .

Press on Connect .

Approve any prompts for allowing the app to access the USB device by pressing on OK .

If you have a tDynamo device, press the icon and select Set MSR On to turn on the head.

Swipe a card to see the card data displays on the screen.
To disconnect the MagTek SCRA device, press the red X.

This section describes how to use the MagTek SCRA Demo with a SCRA Device such as Dynamag, DynaMAX, eDynamo, BulleT, and tDynamo connected to an Android host via USB OTG cable. Please note that the Android host must support Bluetooth and Bluetooth LE to use this connection type.

Connect the MagTek SCRA device to the Android host USB port using an OTG cable.
Press on the device selector and select either Bluetooth, BLE, BLE EMVT from the list.
- Bluetooth: for BulleT

Select the intended device from the list. Example shown below.

Press Connect to connect to the device.

The host will prompt to pair the device the first time the connection is established. Enter the pairing PIN and press OK .

After the Connection State changes to Connected , the device is ready.

To begin the process of sending a command to the device, press on the magnetic stripe card icon at the top of the app, then select SEND .

Enter a command, then press on SEND . An example is shown below with the response.

The selections other than SEND command are as follows.
- Clear: Clears the screen.
- Device Info: Returns information about the device.

To begin the process of starting an EMV transaction, press the chip card icon at the top of the app.

Select the transaction approval type:
- Approved: On for approval response code. Off for decline response code.
- Quick Chip: On to transact only an Acquirer Request Cryptogram (ARQC). Off to transact both ARQC and Acquirer Response Code (ARPC).

For MagTek SCRA devices not equipped with batteries, the devices must have their time set after a power up from the host. This is needed only once until the next power cycle or reset.
- Select Set Time. A response of all 0’s means the time was set.

Select Start Transaction and select each Transaction Types. Transaction types may be combined.
- Swipe: For magnetic stripe
- Chip: for chip.

Present the card to the device and follow the prompts for selecting any languages and applications to complete the transaction. The result will be displayed similar as below.

To cancel a transaction, press EMV at the top of the app and press Cancel Transaction . A transaction may only be canceled before a card is presented.

This section describes the get, set, and commit commands for terminal configuration on the device.

Get – retrieves the terminal configuration.
Set – sets the terminal configuration. Changes do not remain after device power cycle or reset.
Commit – is used to store configuration changes to non-volatile memory to remain in place after a power cycle or reset.

To access the device’s terminal configuration, press on the chip card icon at the top of the app and select Configuration.

To get the devices terminal configuration, select Get Terminal Config . The value will be displayed similar as below.

To set the devices terminal configuration, select Set Terminal Config . The value will be displayed similar as below. Setting the Terminal Configuration requires an authenticated message unique to each device, so in the MagTek SCRA OEM Demo the response will indicate an invalid serial number or invalid MAC.

To commit the devices terminal configuration, select Commit Config . The value will be displayed similar as below.

MTSCRA Class Methods - 51 - 61

getTLVVersion

Retrieves TLV version.

public string getTLVVersion()

Parameters: None

Return Value:

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

getTrackDecodeStatus

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

public string getTrackDecodeStatus()

Parameters: None Return Value:

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

00 = Track OK
01 = Track read Error
02 = Track is Blank

Retrieves SDK version.

public string getSDKVersion()

Parameters: None Return Value:

The version information of the SDK.

Send command to device.

public int sendCommandToDevice(string command)

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

This function starts an EMV L2 transaction for smart card.

public int startTransaction(
byte timeLimit,
byte cardType,
byte option,

Parameters:

Return Value:

0 = Success
9 = Error1
15 = Busy

This function sets the user selection result. It should be called after receiving the OnUserSelectRequest event which is triggered after the user makes a selection.

public int setUserSelectionResult(byte status, byte selection)

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

This function sends to the device the transaction decision from acquirer.

public int setAcquirerResponse(byte[] response)

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

This function cancels a transaction while waiting for the user to insert a card.

public int cancelTransaction ()

Parameters: None Return Value:

0 = Success
9 = Error
15 = Busy

Send extended command to device.

public int sendExtendedCommand(string command)

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

Retrieves features for the device.

public MTDeviceFeatures getDeviceFeatures()

Parameters: None

Return Value:

Retrieves power management value for the device.

public String getPowerManagementValue()

Parameters: None

Return Value: Returns the PM value associated with the device.

MTSCRA Function - 4.51 - 4.60

4.51 getBluetoothRSSI

This function will return the signal strength of Bluetooth LE devices.

(int)getBluetoothRSSI;

4.52 setUUIDString [DynaMAX/eDynamo Only]

This function sets the UUIDString for the Bluetooth LE connection.

(void) setUUIDString:(NSString *)uuidString

Parameters: UUID String of the device

Return Value: None

4.53 getConnectedPeripheral [DynaMAX/eDynamo Only]

This function gets the current connected peripheral (device).

(NSString *) getConnectedPeripheral

Parameters: None

Return value: Current connected device

4.54 getDiscoveredPeripherals [DynaMAX/eDynamo Only]

This function gets an array of DynaMAX/eDynamo devices connected to the host.

Parameters: None

Return Value: Array of DynaMAX/eDynamo devices.

Start EMV Transaction.

The device’s system date and time must be set prior to sending this command. Use sendExentedCommandSync() to set the date and time.

Devices without a battery-backed real time clock require the host to set the date and time using Extended Command 0x030C - Set Date and Time every time the device is power cycled or reset.
Devices that have a battery-backed real time clock (See Supported Devices) would typically have the date and time set at the factory.

(int) startTransaction:

(Byte)timeLimit cardType:

(Byte)cardType option:

(Byte)option amount:

(Byte*)amount transactionType:

(Byte)transactionType cashBack:

(Byte*)cashBack currencyCode:

(Byte*)currencyCode reportingOption:

(Byte)reportingOption

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

This function sets the user selection result. It should be called after receiving the onUserSelectRequest event which is triggered after the user makes a selection.

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

This function cancels a transaction while waiting for the user to insert a card.

Return Value:

0 = Success
9 = Error
15 = Busy

The library returns the status of this function in the delegate method onEMVCommandResult (EMV Device Only).

Parameters:

This function informs EMV device to process transaction decision from acquirer.

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

Send extended command to device. Command response is returned in the event message onDeviceExtendedResponseReceived.

Parameters:

Return Value:

0 = Success
9 = Error
15 = Busy

Send a synchronous command to device. Operation waits for the command to return.

Parameters:

Return Value: String containing the response data of the command.

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

Connection Types

iDynamo 5 Gen III connects to iOS products via a USB-C or Lighting to USB-C cable.

How to Use Apple iAP2 Connections

This section provides information about developing an iOS app that interfaces with the device via the Lightning or USB connector using iPod Accessory Protocol 2 (iAP2). For sample code and other supporting materials, see DYNAMAX / EDYNAMO / UDYNAMO / ADYNAMO / IDYNAMO / KDYNAMO / SDYNAMO / TDYNAMO SDK FOR IOS (WEB), available from MagTek.

To develop host software for an iOS host that connects to the device, you must know the following device properties, which are specified by the purchaser when ordering, and loaded by the manufacturer:

protocolString, also known as the SDK Protocol, usually in the form of a reverse DNS string unique to the host software developer or the device purchaser.

The host software project must include the protocolString in its .plist file before compiling. Spelling, including punctuation and capitalization, must exactly match the protocolString of the device.

The host software should initiate a connection to the device using the iOS SDK’s External Accessory Framework (for sample code, see Apple’s EADemo app). Upon establishing the connection, the host can begin exchanging data with the device.

This USB device conforms to the USB specification revision 2.0 and Human Interface Device (HID) class specification version 1.11. The device is set up as a full-speed, high-powered USB device that draws power from the USB bus. iDynamo5 Gen III identifies itself to the USB host with MagTek’s vendor ID 0x0801 and Product ID (PID) of 0x0020. All USB enumeration will include the device serial number.

HID reports used by the host can be divided into two types:

Feature Reports, which the host uses to send commands to the device and receive responses using Get Feature and Set Feature.
Input Reports are used by the device to send unsolicited notifications to the host when the device’s state changes, or to send asynchronous responses to the host when a command completes. The device commonly uses input reports when reporting card swipes, device events, or when a command takes more time for the device to process than is reasonable for the host to wait on a blocking call for the device to acknowledge completion.

A device in KB mode identifies itself to the USB host as a keyboard and transmits data to the host as ASCII as though it is being typed by a person on an actual keyboard. It does this by mapping each of the possible ASCII characters in the stream to keystrokes. To send an ASCII character to the host, the device looks up the ASCII character in the key and retrieves a combination of a single Key Usage which is a unique value assigned to every keyboard key, and a Key Modifier Byte and sends them to the host. The key modifier byte modifies the meaning of the key usage ID, by indicating whether any combination of the right or left Ctrl, Shift, Alt or GUI keys [as defined by Universal Serial Bus (USB) Device Class Definition for Human Interface Devices (HID)] are pressed at the same time as the key usage ID.

The device transmits ASCII 0 to 31 and 127 as their equivalent control code combinations. For example, for a carriage return value 13 (0x0D), the device appears to the host as a keyboard where a person very quickly presses and holds the Ctrl key, then presses the M key, then releases both keys.

When the keymap contains a Key Usage ID and Key Modifier Byte of 0xFF for the ASCII value the device wants to send, the device uses Alt ASCII code keystrokes instead of key map values, meaning it simulates holding down the Alt key on a keyboard and typing the three-digit decimal value of the ASCII character it wants to send. For example, to transmit the ASCII character ‘?’ (063 decimal in the ASCII table), the device sends keypad ‘0’ combined with the Left Alt key modifier, then keypad ‘6’ combined with the Left Alt key modifier, then keypad ‘3’ combined with the Left Alt key modifier.

Commands and Responses

Feature reports are used to send commands and receive responses, even when KB mode is active.

Notifications (RFU)

This section defines how the device communicates with the host over the USB HID interface.

The data transmitted in commands, responses, and notifications can be substantial, with a size limit of 64 kilobytes (64K bytes). However, the USB HID interface utilized by V5 restricts messages to 64 bytes. Therefore, to accommodate larger messages, we employ specific methods to segment them into multiple 64-byte packets. The segmentation approach varies depending on the message type to ensure compatibility with legacy V5. Below is the core structure of a USB HID packet.

The device makes data available to the host using one or more Input Reports over a USB Interrupt IN pipe. The host will poll the device at the configured Polling Interval to see if Input Reports are ready. The device must respond to polls with a USB NAK when no Input Reports are available.

Data Messages sent by the device use Input Report ID 0x01.
Notification Messages sent by the device use Input Report ID 0x02.

The host sends commands using a Set Feature Report and sends a Get Feature Report to the device to retrieve a synchronous response when appropriate. Feature reports use report ID 0x01.

The host should send both Feature Report types using the default Control pipe using a blocking call to the operating system’s native USB libraries. The device NAKs the Status page of a Set Feature Report until it finishes the requested operation, and if it does not respond, the operating system will generally time out and report failure. This method ensures that as soon as the device has fulfilled the command request embedded in the Set Feature Report, the host software can immediately call a follow-up Get Feature Report to retrieve the command.

In very rare cases, the host may simply send a Get Feature Report directly without a preceding Set Feature Report. The Commands documentation specifies these special cases if they exist.

Commands are sent to the device using USB Set Feature Reports using Report ID 1.

Sending commands to the device over a packeted interface (maximum parameter size is 64k (0xFFFF). Standard command format gets broken down into packets for interfaces that do not support unlimited length messages. This is compatible with the V5 extended command protocol.

The number ranges shown in packets assume the interface is USB with a maximum message size of 64 bytes.

The Command and Parameter Data length fields stay the same for all packets. Each packet will contain one segment of parameter data up to 52 bytes. The data offset indicates which portion of the parameter data is contained within this packet.

If the required Parameter Data is 52 bytes or shorter, the host can send the entire command using a single command packet. If the Parameter Data is longer than 52 bytes, the host should split the data into multiple packets of 52 or fewer bytes and send multiple command packets. Assuming 52-byte packets, the first packet the host sends should specify Data Offset = 0, the next packet should specify Data Offset = 52, and so on, until the host has sent all the Parameter Data. The device’s response to each packet contains either an extended command result code or a standard result code for the command that was sent:

A packet with Data Offset = 0 is considered the start of a new command. If there are still packets pending from a previous command, then that command is cleared, and all data received is erased.

The device will respond to packets with a 0x0B,0x00 when it expects additional packets (i.e., the length of parameter data received is less than the full parameter data length). When all data has been received, then the device will respond with a packet starting with 0x0A and include the response message for the command.

ACK Packet … Send next packet.

Result Code 0x0B - Protocol Request Pending indicates the device is buffering the incoming data and expects the host to send subsequent packets.

Error due to invalid or missing data or due to a timeout while the device is waiting for more packets.

Response messages are generated after executing a command and made available to the host as a feature report with the report ID set to 1. The host uses the USB Get Feature Report to receive the response or a portion. The following should be compatible with V5 extended responses.

After the host receives the initial response packet, it’s up to the host to collect the data and send 0x4A commands to get more response packets until all data has been received.

Notification messages with a data size longer than 52 bytes will need to be split into multiple packets to accommodate the USB HID interface. Notifications are made available to the host as one or more USB Input Reports with the report ID set to 2.

Data messages are another type of asynchronous communication and handled in the same manner as a notification, except the report ID is set to 1.

When connected to an iOS host, the device communicates over what appears to be a simple bidirectional serial line transferring binary data. To manage serial communications, we utilize an old method called SLIP (Serial Line Internet Protocol). This allows the addition of message control characters and a method to distinguish between control and data.

Each message is prefixed by a one-byte message type followed by a two-byte message length. The possible types are:

00 - Data (Data is ASCII text to be compatible with KB emulation output)
02 - Notification
04 - Response
05 – Command

Messages are framed before and after with a byte value of 0xC0. Because this value can also appear as part of the data message, a few 2-byte sequences are added to distinguish between control and data bytes. The sender modifies the outgoing data, and the receiver translates the incoming data back to the original message. Conversion can be done on the fly during the sending and receiving processes.

Assemble message.
Add message type and length to the beginning of the message.
Replace any bytes with value 0xDB with bytes 0xDB 0xDD.

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.

Card Readers

Card Readers

Tap to Pay on iPhone API

MagneSafe V5 SCRAs

MagneSafe V5 SCRAs

iDynamo 6

tDynamo (Gen I, II)

DynaWave

DynaPro Mini

uDynamo

Magnetic Stripe Readers

iDynamo 5 (Gen I,II)

iDynamo 5 (Gen I,II) Support

For more help

Introduction

About MTSCRA Library

MTSCRA Class Methods

MTSCRA Class Methods - 21 - 30

getKSN

getDeviceName

MTSCRA Class Methods - 31 - 40

Enums/Interfaces

Commands

Appendix B ARQC Message Format

Appendix C ARQC Response Message Format

Appendix D Batch Data Format

MTSCRA Functions

MTSCRA Delegate Methods

Properties

Introduction

How to Set Up the MTSCRA Library for Projects

MTSCRA Class Methods

MTSCRA Callback Messages

MTSCRA Functions

Introduction

About MTSCRA Library

MTSCRA Class Methods

Card Readers

Card Readers

iDynamo 6

Tap to Pay on iPhone API

Commands

MTSCRA Functions

MTSCRA Class Methods

MTSCRA Functions

MTSCRA Callback Messages

Properties

MTSCRA Delegate Methods

Discovery

For more help

iDynamo 6 Support

For more help

Tap to Pay on iPhone API Support

For more help

MagneSafe V5 SCRAs

MagneSafe V5 SCRAs

MTSCRA Class Methods - 21 - 30

getKSN

getDeviceName

iDynamo 5 (Gen I,II)

iDynamo 5 (Gen I,II) Support

For more help

Magnetic Stripe Readers

Appendix D Batch Data Format

MTSCRA Class Methods - 31 - 40

uDynamo

Appendix B ARQC Message Format

DynaPro Mini

DynaWave

tDynamo (Gen I, II)

Enums/Interfaces

Introduction

How to Set Up the MTSCRA Library for Projects

clearBuffers

getBatteryLevel

getSwipeCount

getCapMagnePrint

getCapMagnePrintEncryption

getCapMagneSafe20Encryption

getCapMagStripeEncryption