These documents provide instructions for using the browser-based MagTek Demo Applications to configure and test MagTek devices

These demos provide an interactive web-based demonstration for MagneSafe V5 Secure Card Reader Authenticators (SCRA), showing how to integrate JavaScript with EMV and NFC-capable devices in Chromium-based desktop browsers.

Web-based Demos

This document provides instructions for using the browser-based MagTek Demo Applications to configure and test MagTek devices, including MMS devices, specifically the DynaFlex family (including DynaFlex, DynaFlex Pro, DynaFlex II, DynaFlex II PED, DynaFlex II Go and DynaProx, models).

The Demo Applications enable comprehensive testing of a wide array of capabilities, including core payment functions like EMV chip and NFC transactions, MSR reading, barcode scanning, and PIN entry. Note that feature support is dependent on your specific device model. For instance, the DynaFlex II PED model supports PIN entry, manual card entry, and signature capture functionalities.

• CRITICAL REQUIREMENT: For USB connected devices, these demos require a Desktop, Chromium Browser Only!

The MagTek Demo Applications rely on Web HID functionality for USB connected devices, which is not supported by mobile browsers (iOS/Android). You must use a desktop-based Chromium browser (like Google Chrome, Microsoft Edge, or Opera) for the demos to function correctly when using a USB connected device.

Demo Application Home Page

Upon opening the Web HID Demo home page, the Main Page is displayed. This page serves as the central menu and is organized into the following categories:

• MMS Devices – DynaFlex I/II device types and DynaProx (EMV, NFC, Barcode, PIN and MSR)

• V5 Devices – iDynamo, eDynamo, mDynamo, tDynamo (EMV, NFC and MSR)

• V5 MSR/Manual Entry – MSR swipe devices such as Dynamag and DynaPAD

• V5 (SRED) Devices – iDynamo 5 Gen III (MSR)

Each section provides a corresponding demo page with user interface elements for connecting a device, issuing commands, and reviewing results see Figure 1.

Figure 1 - Demo Application Home Page

The MMS product family includes the following devices:

• DynaFlex/DynaFlex Pro

• DynaFlex II/DynaFlex II PED

• DynaFlex II GO

• DynaProx

Devices in this family generally support EMV, NFC, barcode, MSR, and PIN functionality, though specific features vary by model. The Demo Application connects through methods including USB HID, WebSocket (WSS), MQTT, or Bluetooth Low Energy (BLE), depending on the connection method enabled on your device.

This checklist provides a summary of the steps required for configuring and running a demo with your device.

• Prepare Device: Power on the device (if there is a power button) and connect it via USB, Wi-Fi, MQTT, or BLE.

• Open Demo Application: Launch the Web HID Demo in a desktop Chromium browser.

• Configure Host App: Be sure to enter RMS, WebSocket, MQTT, and Contactless parameters prior to using the various demos.

• Device Provisioning: If using WSS or MQTT, provision the device's network and security settings (as outlined in Section 3)

• Open Session: Select Open and confirm a successful connection.

• To test your setup and connection, choose a command (e.g., Start EMV ALL), paste command data if necessary, and select Send Command.

• View Results: Swipe, insert, or tap a card, and observe the transaction log for the response and confirmation.

This page provides an interactive web-based demonstration for MagTek MMS Dyna devices, showing how to communicate with Secure Card Reader Authenticators (SCRA) using multiple interfaces—including WebHID, MQTT, WebSocket (WSS), WebSerial, and WebBLE—for flexible, real-time device integration and testing.

Web-based Demo

This page provides centralized access to configuration guides, security certificate setup instructions, source code resources, and supporting documentation required to successfully deploy, secure, and integrate MagTek readers, using JavaScript and a wide array of web-based demos and related communication workflows.

Web-based Demos

This page acts as a central navigation hub, consolidating all interactive browser-based demonstrations for MagTek devices. It provides essential links to demos for devices such as MMS Dyna products and V5 card readers, all within a structured documentation environment. The hub is designed to help developers quickly access the specific demo suite they need, facilitating efficient testing and integration of MagTek devices in Chromium-based desktop browsers.

See MagTek readers in action and start from working code. This section collects runnable demos and sample code — including a browser-based demo you can try without installing anything — to validate your setup and give you a starting point for your own integration.

This page provides access to interactive browser-based demonstrations for the iDynamo 5 Gen III, a secure card reader authenticator (SCRA) that uses MagTek's MagneSafe V5 (SRED) architecture. The demos show how to communicate with the device using WebHID for direct USB connections in Chromium-based desktop browsers, as well as MQTT for network communication via a local client application. These tools are designed to help developers quickly test device functionality and understand the integration process.

March 2026

Document Number: D998200713-100

REGISTERED TO ISO 9001:2015

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

INFORMATION IN THIS PUBLICATION IS SUBJECT TO CHANGE WITHOUT NOTICE. MAGTEK CANNOT BE HELD LIABLE FOR ANY USE OF THE CONTENTS OF THIS DOCUMENT. ANY CHANGES OR IMPROVEMENTS MADE TO THIS PRODUCT WILL BE INCLUDED IN THE NEXT PUBLICATION RELEASE. IF YOU HAVE QUESTIONS ABOUT SPECIFIC FEATURES AND FUNCTIONS OR WHEN THEY WILL BECOME AVAILABLE, PLEASE CONTACT YOUR MAGTEK REPRESENTATIVE.

MagTek®, MagnePrint®, and MagneSafe® are registered trademarks of MagTek, Inc. Magensa™ 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 of 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.

Google Play™ store, Google Wallet™ payment service, and Android™ platform are trademarks of Google LLC.

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.

These instructions detail the operational steps once all necessary configurations (Section 2) are complete. If connecting via USB HID, the steps listed in section 2 can be skipped.

HID MMS Demo (Direct USB HID)

The Human Interface Device (HID) protocol enables driverless plug-and-play connectivity for your device via USB.

• Ensure the device is powered on and connected via USB.

• If this is the first time, you may have to pair the device in the Chromium browser, which involves granting the website permission via a pop-up prompt.

• From the Demo Application, select Open, and choose the appropriate device. A green check mark confirms the device is successfully opened.

• From the command dropdown menu, select a command such as DynaFlex: START EMV ALL.

• Select Send Command to execute the action.

• Insert or tap a test card and monitor the transaction log for the response.

Figure 3 - HID MMS Demo

Message Queuing Telemetry Transport (MQTT) is a lightweight messaging protocol commonly used for Internet of Things (IoT) applications. It provides efficient, reliable communication between devices and applications, even in environments with limited connectivity. IMPORTANT: DynaFlex II PED is the only device that supports native MQTT. All other Dyna Devices must use the HID MQTT Device Client.

Key characteristics include:

• Publish/Subscribe model – Devices publish data to a central broker; applications subscribe to receive data.

• Low overhead – Messages are compact and efficient, suitable for embedded systems.

• Real-time updates – Events such as card insertions are transmitted immediately to the Demo Application.

• Cross operating system and cross browser connectivity: MQTT ensures seamless interaction because it is platform-agnostic, meaning devices running Windows, Linux, macOS, or embedded OS, and applications running in different browsers, can all connect and exchange messages reliably.

Within the HID MQTT Device Client and MQTT MMS Demo, this protocol enables MagTek MMS devices (e.g., Dyna Family Devices) to securely communicate via MQTT across operating systems.

Figure 4 - MQTT Geographic Map

Figure 5 - MQTT MMS Demo

• Configured Device – Identifies the active device.

• Status Indicator – A green check mark indicates a successful connection.

• Options – Auto Start, EMV, NFC, and MSR session checkboxes.

• Command Data – Field for entering or pasting hexadecimal command data.

The command above, and others can be selected from the pulldown menu. The Choose File button allows the user to upload custom commands from a file. This screen also confirms device recognition, command formatting, and connectivity prior to further testing.

The HID MQTT Device Client acts as a communication gateway that transforms your locally connected MagTek device (via USB HID) into a remote asset. This allows other applications to access the device securely via the MQTT protocol. IMPORTANT: DynaFlex II PED is the only device that supports native MQTT which means it does NOT need to use the HID MQTT Device Client.

• Power on and connect the device via USB.

• Open the HID MQTT Device Client page.

• Select Open within the client.

• Scan the QR code or select the provided link to open the separate MQTT Device Demo Application.

Figure 6 - HID MQTT Device Client

The MQTT Geographic Map displays device location and status for connected units, see Figure .

The MQTT Configuration page provides controls and parameters necessary for device operation over MQTT.

• Device Status Panel – Displays device information (model, name, IP address, SSID) and records configuration progress.

• Controls – Includes Open, Save Config, Reset Device, Close, and Clear.

• Wi-Fi Settings – SSID and password configuration.

• MQTT Credentials – Org Node, username, and password for broker authentication.

Figure 7 - MQTT Configuration

This interface is used to configure secure communication with WebSocket transport using TLS or mTLS. Functions include:

• Network Settings – Get DHCP and Set SSID.

• Wi-Fi Setup – Retrieve or assign SSID and password credentials.

• Certificate and Trust Management – Load TLS/mTLS certificates, verify certificates, and generate or sign Certificate Signing Requests (CSR).

  • For NonTLS connection,

Figure 8 - WebSocket Certificate and Trust Configuration

When using WSS (WebSockets over SSL/TLS) with DynaFlex devices, the following technical considerations are critical for IT teams to ensure reliable and secure communication.

The default SSL certificate pre-installed on DynaFlex devices is uniquely generated for each device and tied to a hostname in the format df-[SerialNumber] (e.g., df-1234567). This certificate is used to establish the WSS connection.

• SSL/TLS certificates are literal. The browser (or any WebSocket client) validates that the hostname used in the connection URL exactly matches the certificate's Subject Name or Subject Alternative Name (SAN). If the URL uses wss://df-1234567/ but the network appends a domain suffix (e.g., df-1234567.office.lan), the browser will reject the connection as insecure because the names do not match.

• IP addresses cannot be used. Connecting via wss://192.168.1.50/ will trigger a SAN missing error because the certificate is issued to a name, not an IP address.

Therefore, the network must be configured to resolve the short hostname (e.g., df-1234567) to the device's IP address. The following options are available:

• Option A: Global Search Suffix (Recommended) Configure the DHCP server to add a Connection-Specific DNS Suffix (via DHCP Option 15/119). This allows client computers to automatically map the short name to the device without manual DNS entries. Action: Add your local domain to the DHCP option list so that df-[SerialNumber] resolves correctly.

• Option B: The "Trailing Dot" Override If DNS search suffixes are misconfigured or polluted, you can force the browser to look for the bare hostname by appending a trailing dot to the URL. Standard URL: wss://df-12345678/ (the OS may append the domain) Forced URL: wss://df-12345678./ (the trailing dot forces an exact hostname lookup)

• Option C: CNAME or A-Record in Local DNS For networks with a central DNS server, create a static entry. Action: Create a forward lookup zone with an A record (or CNAME) for df-[SerialNumber] pointing to the device's static IP address.

The WSS connection relies on a server certificate installed on the device. As of this writing, the demo application signs certificates with a validity period of 13 months. After expiration, any WSS communication will fail silently due to browser security policies—no manual override is possible for WebSocket connections.

• Best Practice: Certificates must be replaced before they expire. A certificate update strategy must be employed when deploying devices in production using WSS.

• Renewal Process: Use the WSS Certificate and Trust page to generate a new Certificate Signing Request (CSR) and load a renewed certificate. Refer to the steps for loading TLS trust and resetting the device.

• Monitoring: Implement monitoring to alert administrators when certificate expiration is approaching (e.g., 30 days prior).

By adhering to these hostname resolution and certificate lifecycle guidelines, you ensure uninterrupted and secure WSS communication with your DynaFlex devices.

This page provides access to browser-based Web HID demonstrations for MagneSafe V5 magnetic stripe (MSR) devices, showing how to communicate with Secure Card Reader Authenticators (SCRA) like Dynamag using Chromium-based desktop browsers for non-EMV transaction testing.

Web-based Demo

For devices using MQTT or WebSocket (WSS), configuring your host application and provisioning the device itself is mandatory to establish a successful secure connection. If connecting via USB HID, all steps listed in section 2 can be skipped.

Before using MQTT or WebSocket (WSS), configuration is required. From the Demo Application Home Page, select Misc. → Configuration for the Demos.

Figure 2 - Miscellaneous Configuration and Documentation Pages

Configuring the Demo and Provisioning Your Device

Step 1: Configure Host Application Settings

Configure the Demo Application by supplying the necessary API keys and server addresses.

• From the Home Page, select Misc. → Configuration for the Demos.

• Enter and save the required settings.

  • RMS Options: Enter the Magensa API key and service URL

  • WebSocket Options: Provide the WebSocket server address.

  • MQTT Options: Specify the Org Node, broker address, client ID, and user credentials.

  • Contactless Options: Adjust timing parameters for NFC operations.

The separate MQTT Configuration page is used to provision your physical device with its Wi-Fi credentials and MQTT broker details.

• Connect your device via USB HID.

• Open the MQTT Configuration demo page.

• Select Open to connect to your device.

• Use the Wi-Fi Settings section to enter the device's SSID Name and SSID Password.

• Connect the host PC to the same wireless network that your DynaFlex II PED device will be connected to.

• Open this page using a Chromium Browser

• Plug in the device via USB cable

• Click Misc and click WSS Certificate and Trust Config

• Click Open button

• Select DynaFlex II PED and Click Connect.

• Enter Wireless Network SSID and password, then click Set SSID

• If you want to connect via non-secure TLS connection, press Load NoTLS Trust, and press Reset Device

• If you want to configure via secure TLS, press Load TLS Trust, then press Get & Sign CSR, then Press Reset Device

• By clicking on the MAGTEK Logo on the top of the page, go back to the Miscm Menu and press Configuration for the Demos option

• Enter device host name under WebSocket Options, for Non-secure TLS, just put ws://device-hostname, for TLS secure connections, enter wss://device-hostname (example wss://df-1234567)

• Click Save

• Go back to home page and press MMS Devices for EMV, NFC, BCR and PIN, then press WSS Device Demo

• Allow other devices on your local network

• Click on Open which will all open the connection to the device:

• The terminal should display a green dot indicating successful connection:

This interface invokes callback functions to receive data and/or a detailed response. To register for the event(s), call the setSystemStatusCallback() function with the name of a class that implements the ISystemStatusCallback interface.

OnError

This event is called when an error occurs with the connection with the MQTT broker.

Prototype

void OnError(
    ErrorType error, 
    String details);

Parameters

Return Value: None

Create an instance of the IDeviceConfiguration using IDevice.getDeviceConfiguration. Then use the function calls described in this chapter.

configType

This property is for the configuration type.

Byte configType;

Return Value:

• 0x01 = Device Settings

• 0x02 = Device Information

OidAndValue

This property is for the Object ID and value.

NSData* OidAndValue;

Return Value:

The OID and value.

This function is for reading and setting the device OID properties.

Return Value:

OID property value.

How to use the EMVConfiguration Console

The following instructions are for using the MTUSDK Test console on a Linux operating system. In these examples, lines are removed and replaced with “. . .” for brevity.

BIN File

To send an individual BIN configuration file to the device follow these steps.

• After the name of the console, enter:

[cfg.bin] Name of the .bin file
-t	File type (excel or bin)
-i	File Id number. 8 digit file id.
        00000000	TERMINAL
        00000100	PROCESSING
        00000200	ENTRYPOINT
        00000300	CA KEYS
        00000500	AMEXDRL

-d	Device path. Optional if using USB. 

Example: Terminal configuration bin file

$ sudo ./emvconfiguration cfg00000000.bin –t bin –i 0000000000

• Then press Enter key. The result is shown similar as below.

Connect to usb progress (33)
    progress (66)
    progress (100)
    result (0)
send file – 00000000 successfully

• The console exits afterwards.

To send an Excel configuration file to the device follow these steps. Excel may contain one or multiple configurations.

• After the name of the console, enter:

Example: Excel configuration file

• Then press Enter key. The EMVConfiguration console will connect to Magensa Remote Services, send the excel content for conversion into .bin format, and then send each .bin file to the device.

The result is shown similar as below.

• The console exits afterwards.

Create an instance of the DeviceInformation from Idevice.getDeviceInfo. Then use the function calls described in this chapter.

deviceModel

This property returns the model name of the device.

NSString* deviceModel;

Return Value:

Returns the model name of the device.

deviceName

This property returns the name of the device.

NSString* deviceName;

Return Value:

Returns the name of the device.

deviceSerial

This property returns the serial number of the device.

NSString* deviceSerial;

Return Value:

Returns the serial number of the device.

initWithName

This function initializes an instance of DeviceInfo.

Universal SDK Documentation (.NET/Windows)

The .NET edition of the MagTek Universal SDK (MTUSDK), giving developers a single managed interface for connecting to and controlling MagTek card readers and PIN pad devices — including the DynaFlex family — from Windows .NET applications. The complete API reference is available as a PDF download below.

In This Section

Need More Help

SDKs & Tools

SDKs & Tools is where you find the libraries and utilities for building against MagTek readers — the client-side code that talks to a device, plus the tools that help you develop, test, and manage one. Where the API & Command Reference defines the command set itself, the SDKs wrap it for your platform so you aren't composing raw messages by hand. Start here to pick the right SDK for your platform and integration model.

In This Section

This interface invokes a callback function to receive data and/or a detailed response. To use, a class must implements the IConfigurationCallback Delegates interface.

This event is called when certain asynchronous IDeviceConfiguration operations need to have a MAC included with the request.

Manual Part Number: DD998200579-100

REGISTERED TO ISO 9001:2015

Copyright © 2006 – 2024 MagTek, Inc.

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

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

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

DynaProx™, DynaFlex Pro™, and DynaFlex II PED™ 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.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Ubuntu® is a registered trademark of Canonical Ltd.

These instructions are for preparing Google Wallet Smart Tap VAS (value-added service) transactions.

• Configure the mobile device for Google Wallet Smart Tap Pass.

• Load the LTPK protection key (Long Term Private Key) into the MagTek device.

• Upload a Public Key to the Google Pay & Wallet Console for the issuer account associate with the Google Wallet Pass.

MTUSDKNET API will invoke the callback function in this chapter to provide the requested data and/or a detailed response. To delegate the event, call the subscribeAll function with the name of a class that implements the IEventSubscriber Delegates interface.

OnEvent handles all event types. The eventType parameter defines which event is triggered.

This document provides instructions to use the MTUSDK EMVConfiguration Console. The console sends either a .BIN file or contents of an Excel file to the device. BIN files are directly send to the device. Excel files are processed by Magensa Remote Services web service. The resulting BIN data is sent to the device.

This document is part of a larger library of documents designed to assist Secure Card Readers implementers, which includes the following documents available from MagTek:

• D998200570 MAGTEK UNIVERSAL SDK PROGRAMMER'S MANUAL ( LINUX )

• D998200489 DYNAPROX PROGRAMMER'S MANUAL ( COMMANDS )

This document is intended to describe onboarding for Selectable Card Data Encryption (SCDE) available on DynaFlex II GO devices. This feature is intended to allow the user to view card data outside of a transaction scenario. It is accessible using the MagTek Reader Management System (RMS) Application available in the Apple App Store.

The feature will work only with the RMS iOS app compatible with iPhone, iPad, and iPod touch, iPad OS.

• iOS Application (PN 1000009755)

• Compatible with Bluetooth Low Energy (BLE) connected readers, as well as WLAN enabled readers.

This interface invokes callback functions to receive data and/or a detailed response. To register for the event(s), call the setMQTTDeviceStatusMonitoring() function with the name of a class that implements the IMQTTDeviceStatusCallback interface.

This event is called when a device is connected to the MQTT broker.

MTUniversal API will invoke the callback function in this chapter to provide the requested data and/or a detailed response. To delegate the event, call the subscribeAll() function with the name of a class that implements the IEventSubscriber interface.

OnEvent() handles nearly all event types. The eventType parameter defines which event is triggered.

To view or download any of the documents mentioned in this manual, visit

D998200595 - DYNAFLEX II GO SECURE CARD READER AUTHENTICATOR INSTALLATION AND OPERATION MANUAL

D998200681 - MAGTEK READER MANAGEMENT SYSTEM (RMS), IOS APPLICATION, INSTALLATION AND OPERATION MANUAL

D998200383-DYNAFLEX PRODUCTS THREE-WAY SECURE CARD READER AUTHENTICATORS PROGRAMMER'S MANUAL (COMMANDS)

Not sure where to start? MagTek offers different SDKs and interfaces depending on which reader you're building for and how you want to connect. This page points you to the right one; each links to its own documentation for the details.

Match your reader to its SDK:

Create an instance of the DeviceCapability, then use the properties described in this chapter.

This property returns true if the device is capable of automatically capturing a signature during a transaction.

Return Value:

Returns true if device is capable of automatically capturing a signature. Otherwise, returns false.

This property returns true if the device is equipped with a battery that preserves the internal clock when not powered by a host system or charging.

Return Value:

Returns true if device is equipped with a battery backed clock. Otherwise, returns false.

This property returns true if the device is equipped with display.

Return Value:

Returns true if device is equipped with a display. Otherwise, returns false.

To set up the MagTek Universal SDK library, download and install the MTUSDK available from MagTek.com.

To build out demo code, follow these steps:

1. Locate and copy the framework files to your project folder. iOS files is under folder ios-arm64 of the SDK package.

1. Click your project and select “General”. In the section “Frameworks, Libraries, and Embedded Content”, click “+”.

The Universal SDK is MagTek's cross-platform SDK for building against MMS (DynaFamily) readers. It wraps the MMS command set in native calls for each platform — handling connection, sending commands, and receiving responses and notifications — so you work in your language instead of composing raw messages. Choose your platform below; the command each call maps to is documented in the API & Command Reference.

To set up the MagTek Universal SDK library for Android, download the 1000007352 MagTek Universal SDK for MMS Devices (Android) available from MagTek.com.

To add the MT Universal libraries to a custom software project in Android Studio, follow these steps:

• Launch Android Studio.

• Copy the following AAR file to the libs subfolder of your software project: MTUSDK.aar

• 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 MTUSDK. For examples, see the source code included with the MagTek Universal 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 Universal Demo project.

To Run/Debug the sample code, follow these steps:

• In Android Studio, select File -> Open ...

• Select MTUSDKDemo project, click OK.

• Select Run -> Run app to run the sample code or select Run -> Debug app

These instructions are for preparing Apple VAS (value-added service) transactions.

Merchant ID and URL Slots

• Set the Apple VAS Merchant ID and URL property for each slot 1 to 6 using IDeviceControl --> setConfigInfo().

POS Capabilities

• Set the POS capabilities property using IDeviceControl à setConfigInfo().

Start Transaction

• Set the PaymentMethods to include PaymentMethod.AppleVAS.

• Set AppleVASMode to: VASMode.Single, VASMode.Dual, or VASMode.VASOnly.

• Set AppleVASProtocol to: VASProtocol.Full or VASProtocol.URL.

• Data from an Apple VAS (9F27 and 9F2A) is returned in separate Apple VAS slot containers.

• FE — var — VAS Data Container

  • FF01

User manuals for the browser tools you use to set up and manage QwantiFi readers. The QwantiFi Cloud Device Management tool configures a single reader over USB — its Wi-Fi, location, and QwantiFi connection — and the QwantiFi Cloud Dashboard is the fleet console for monitoring, inspecting, and managing every deployed reader across your merchant network. Use the device tool to bring a reader online, then the dashboard to operate the fleet.

In This Section

Universal SDK Documentation (Linux)

The Linux edition of the MagTek Universal SDK (MTUSDK), giving developers a single interface for connecting to and controlling MagTek card readers and PIN pad devices — including the DynaFlex family — from Linux host applications. The complete API reference is available as a PDF download below.

In This Section

Need More Help

Create an instance of the DeviceInfo from IDevice.getDeviceInfo(). Then use the function calls described in this chapter.

getModel

This function returns the model name of the device.

String DeviceInfo.getModel();

Return Value:

Returns the model name of the device.

getName

This function returns the name of the device.

String DeviceInfo.getName();

Return Value:

Returns the name of the device.

For the complete documentation index, see llms.txt. This page is also available as .

Classes

Reference for the individual classes in the MagTek Universal SDK — the data objects used to configure commands and read structured results back from the device. Entries are listed alphabetically across two pages, Classes A–I and Classes N–Z.

In This Section

Universal SDK Documentation (iOS)

The MagTek Universal SDK for iOS gives iPhone and iPad apps one Objective-C/Swift interface to MagTek card readers and PIN pads, across SCRA, PIN pad (PPSCRA), and MMS-class devices such as the DynaFlex family. You find or create a device through CoreAPI, drive transactions and PIN, PAN, and signature requests through IDevice, control the display, barcode reader, and NFC through IDeviceControl, and receive card data, transaction status, and ARQC authorization requests through delegate callbacks. Supported transports include External Accessory (iAP2) for DynaFlex II Go, and WebSocket, secure WebSocket, and MQTT for DynaFlex II PED. This section is the API reference for those classes, delegates, data types, and enumerations, with appendices that walk through API usage and the EMV transaction flow.

In This Section

This document provides the instructions to update firmware into a MagTek DynaFlex or DynaProx device on a Windows PC via USB connection.

• A Windows 10 host with available USB port

• Microsoft .NET 4.6.1 and above.

• DynaFlex, DynaProx, or DynaFlex Pro

MTUSDKNET API will invoke the callback function in this chapter to provide the requested data and/or a detailed response. These events will be called in a class that implements the IConfigurationCallback Delegates interface.

This event is called when certain asynchronous IDeviceConfiguration operations need to be have a MAC included with the request.

Copy

MTUniversal API will invoke the callback function in this chapter to provide the requested data and/or a detailed response. To delegate the event, implements the MTUSDKDelegate interface.

Handles BLE Service and EA Service events. Use this to find a BLE device or EA accessory.

Supplementary reference material for the MagTek Universal SDK, including the full status-code list, a step-by-step API walk-through, the EMV transaction flow, and integration guidance for mobile-wallet value-added services (Apple VAS and Google Wallet Smart Tap).

The Reader Management System (RMS) lets you remotely manage, monitor, configure, and update deployed MagTek readers — keeping a fleet current from one place. RMS is a MagTek cloud service; its full documentation lives under Services.

Create an instance of the ConnectionInfo, then use the function calls described in this chapter.

This function returns the address of the device.

Return Value:

Returns the address of the device.

This function returns the type of connection Interface for the device.

Return Value:

Returns the MTU_ConnectionType

This function returns the type for the device.

Return Value:

Returns the MTU_DeviceType.

This function returns the type for the device.

The user must load the most current DynaFlex II GO firmware before beginning. Follow these steps to update your DynaFlex II GO Firmware:

From the Connect tab, ensure the Profile Name is set to SmartTab and Tap on the Device you want to connect to.

After Connecting a DynaFlex II GO to RMS, press the Device tab. To update device firmware, check the Firmware option only, and press the Update button. Only the updates that are checked will be loaded to the device. A prompt will appear asking the user not to manually turn off the screen, press OK .

The log will indicate:

• If current configurations are up to date,

Document Number: D998200695-100

REGISTERED TO ISO 9001:2015

Copyright © 2006 - 2025 MagTek, Inc.

INFORMATION IN THIS PUBLICATION IS SUBJECT TO CHANGE WITHOUT NOTICE. MAGTEK CANNOT BE HELD LIABLE FOR ANY USE OF THE CONTENTS OF THIS DOCUMENT. ANY CHANGES OR IMPROVEMENTS MADE TO THIS PRODUCT WILL BE INCLUDED IN THE NEXT PUBLICATION RELEASE. IF YOU HAVE QUESTIONS ABOUT SPECIFIC FEATURES AND FUNCTIONS OR WHEN THEY WILL BECOME AVAILABLE, PLEASE CONTACT YOUR MAGTEK REPRESENTATIVE.

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

DynaPro™ and DynaPro Mini™, are trademarks 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.

This is an example of how to manually convert a property OID in decimal format into a constructed TLV command data.

• ConfigType is the first number (node 6) to the left of the OID.

To construct the remaining nodes, logical OR as follows.

Result:

• Add Lengths to each node to include all lower nodes and data.

Limited Warranty

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

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.

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.

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

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.

This document provides instructions for software developers who want to create iOS software solutions that include MagTek devices connected to an iOS host. MagTek Universal SDK

(MTUSDK) incorporates MagTek SCRA and MagTek PIN Pad SCRA devices into one SDK. This document is part of a larger library of documents designed to assist MagTek device implementers.

The following are absolute prerequisites:

· DynaFlex Family Programmer’s Manual

About the MagTek Sample Code

The sample code provides Swift demonstration source code and a reusable MTUSDK library that provides developers of custom software solutions with an easy-to-use interface for MagTek devices. Developers can distribute the MTUSDK library to customers or distribute internally as part of an enterprise solution.

Nomenclature

• Device refers to the MagTek devices that receives and responds to command set.

• Host refers to the piece of general-purpose electronic equipment the device is connected or paired to, which sends data to and receives data from the device. Host types include but not limited to PC and Mac computers, tablets, and smartphones. When “host” must be used differently, it is qualified as something specific, such as “USB host.”

• User in this document generally refers to the cardholder.

Tested operating systems:

• iOS 13 and above.

• Xcode 14 and above.

When connecting to the DynaFlex II PED device by WebSocket, a client certificate and its certificate chain must be installed on the iOS device.

The Root Certificate, Sub CA Certificate, and Client private key Certificate as referenced in document DynaFlex TLS Certificate Installation Manual. The client private key certificate (e.g. filename client.p12) must be accessible to the custom software that makes a secure WebSocket connection to the DynaFlex II PED.

After creating the certificates and transferring them in the iOS device, load the certificate chain into the iOS device by follow these steps. The certificate names shown here are for reference only.

1. Delete the previously installed certificates prior to beginning this procedure. If the certificate chain is current, skip this installation section. View the certificates by going to Settings à General à VPN & Device Management.

1. Copy the certificate chain to the iOS device. Touch the Root certificate DF-2-1_RootCA.pem to download to iOS device.

1. Go to Settings > General >VPN & Device Management > Select Root DF2-1

1. Select Install.

1. Enter Passcode.

1. Press Install twice.

1. Repeat the same steps above for the SubCA certificate Amce_SubCA.pem and for the Client certificate Client.p12. For Client, iOS will ask for an additional certificate password, enter the password used during the creation of the Client certificate when prompted, and then press Next.

1. Enable Certificates by going to Settings à About à Certificate Trust Settings

1. When building the custom app, the Client certificate must be loaded into the data member of CertificateInfo during the call to createDevice(). See below as an example to access the client certificate.

The following instructions are for Bluetooth pairing the DynaFlex II Go.

1. Place the device into Pairing Mode by pressing and holding the power button on device until 4 beeps and release the button. The 4th LED will blink green.

1. When in pairing mode and the first time connecting to device, the host will prompt for a pairing request. Enter the pairing code. The default code is "000000".

Create an instance of the ConnectionInfo using IDevice.getConnectionInfo(). Then use the function calls described in this chapter.

getAddress

This function returns address of the device.

String ConnectionInfo.getAddress();

Return Value:

Returns the address of the device.

getConnectionType

This function returns the type of connection Interface for the device.

ConnectionType ConnectionInfo.getConnectionType();

Return Value:

Returns the ConnectionType.

getDeviceType

This function returns the type for the device.

DeviceType ConnectionInfo.getDeviceType();

Return Value:

Returns the DeviceFeature.

This enum refers to a featured supported by the device.

This document provides instructions for software developers who want to create Android software solutions that include MagTek devices connected to an Android based host. MagTek Universal SDK (MTUSDK) incorporates MagTek SCRA and MagTek PIN Pad SCRA devices into one SDK. This document is part of a larger library of documents designed to assist MagTek device implementers, which includes the following:

The sample code provides Android demonstration source code and a reusable MTUSDK API library that provides developers of custom software solutions with an easy-to-use interface for MagTek devices.

Developers can distribute the MTUSDK API Library to customers or distribute internally as part of an enterprise solution.

• Device refers to the MagTek devices that receives and responds to command set.

This document provides instructions to use the OID Converter Console. It is part of a larger library of documents designed to assist Secure Card Readers implementers, which includes the following documents available from MagTek:

• D998200380 MAGTEK UNIVERSAL SDK PROGRAMMER'S MANUAL (MICROSOFT.NET)

• D998200383 DynaFlex Family Programmer’s Manual (COMMANDS)

The following instructions are for using the DynaFlex, DynaProx OID Converter Console on a Windows operating system.

The console app accepts 2 input parameters: OID & Command Data. The result is the data to pass to MTUSDK commands getConfigInfo() and setConfigInfo().

Blurb goes here.