Only this pageAll pages
Powered by GitBook
1 of 43

Services

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

TokenExchange

TokenExchange is MagTek’s cloud-based, PCI-DSS certified tokenization service that removes sensitive data—like credit card PANs or PII—from your environment by replacing it with dynamically generated, vaultless tokens. Accessed via REST APIs, the service supports three token types: Payment Tokens (for eCommerce, card-on-file, and standard payment operations like Sale or Refund), Transaction Tokens (which create secure, tokenized payment links or QR codes for invoicing and remote collections), and PII Tokens. Built on the MagneSafe Security Architecture, tokens are created using AES/3DES encryption within an HSM and a DUKPT key management scheme, and are resilient against quantum computing attacks. The service is recommended for resellers, VARs, ISVs, and developers using the Magensa Payment Protection Gateway (MPPG) or Decrypt and Forward (DaF) service. 

The official MagTek TokenExchange support page is a central hub containing all the resources you'll need. There you can find product brochures (including the MagTek Hardware and Magensa Gateway Solutions Product Catalog, the Magensa Services Overview, and the Magensa TokenExchange brochure), programmer’s manuals covering Tokenization operations with sample SOAP requests/responses and the Token v2.0 REST API, developer documentation for the TokenExchange Connect client‑side JavaScript, API specifications and integration guides for MPPG v3 and v4, developer manuals for PayPal/Venmo and in‑app Apple Pay/Google Pay, as well as a comprehensive FAQ section and instructional videos.

TokenExchange Support

Web Demo

Description

Support Page

The support page contains downloadable software and instruction manuals.

Need More Help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email: support@magtek.com

  • 📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

Documentation Feedback:

Help us improve this documentation!

feedback@magtek.com

Videos

Videos

Glossary

  • DES - Data Encryption Standard

  • DUKPT – Derived Unique Key per Transaction

  • KSN – Key Serial Number

  • PCI DSS – Payment Card Industry Date Security Standard

  • SCRA – Secure Card Reader Authenticator

  • Security Level – MagneSafe level of security

  • Triple DES/3DES – Triple Data Encryption Standard

  • CAPK – Certification Authority Public Key

  • LMB – Locked Magensa Bundle

  • MPK/MPK2 – Magensa Production Keys, KSID 9070020 and 90700500

Videos

Qwantum Secure Cards

Qwantum Secure Cards are physical credentials from MagTek's Qwantum Media division that serve as uncloneable authentication tokens for high-security applications. These cards contain no PAN, PII, or other sensitive data, making them inherently privacy-safe while generating a unique and dynamic Qwantum Authentication Code (QAC) each time they are swiped through a MagTek Qwantum-enabled reader. The QAC, combined with AES-256 encryption and CMAC authentication, ensures that fraudulent copies are impossible and that each transaction is securely verified in real time. Qwantum Secure Cards are available in various shapes and materials and can be used for physical access control, logical access to systems and websites, loyalty and coupon programs, closed-loop payments, identity verification, and as part of the Qwantum Private Messaging service for encrypting and decrypting sensitive data. When paired with the Qwantum ASIC, these cards provide a tamper-resistant authentication layer that works across both magnetic stripe and digital environments.

The official MagTek Qwantum Secure Cards support page is a central hub containing all the resources you'll need. There you can find product brochures (including the Qwantum Card Brochure, Qwantum Brief Overview, and MagTek Hardware and Magensa Gateway Solutions Product Catalog), white papers covering Qwantum Media Solutions and Qwantum Private Messaging use cases and operation, and an overview document explaining how Qwantum Private Messaging delivers "Privacy as a Service". At this time, software downloads, an FAQ section, and instructional videos are not listed on the support page.

Videos

RMS Videos

Qwantum Private Messaging

Qwantum™ Private Messaging is an app that delivers "Privacy as a Service". This powerful new service of MagTek, lets individuals and businesses use public communication channels or storage systems to send or save sensitive material simply and quickly by privatizing the material.

The official Qwantum Services support page is a central hub containing the resources you'll need. There you can find product brochures (including the Qwantum Media Solutions overview), technical specifications for the various card and token form factors, white papers covering Qwantum authentication technology, and ordering information for blank or pre‑encoded media. At this time, software downloads, programmer's manuals, an FAQ section, and instructional videos are not listed on the support page.

Magensa

Magensa is MagTek's cloud-based payment protection gateway that secures sensitive data and processes transactions across in-person, online, and mobile channels using advanced tokenization, dynamic encryption, and authentication services. On this page, developers and integrators can explore detailed documentation and code examples for key Magensa offerings, including API documentation, code samples in multiple languages, developer guides covering EMV acceptance and Level 3 certification, and links to portals for merchants and resellers to manage accounts, view transactions, and generate reports.

Appendix A - Glossary of Terms

  • API – Application Programming Interface

  • EMV –Europay, MasterCard® and Visa®

  • KSN - Key Serial Number

  • MUT - MagTek Update Token

  • SDK – Software Developer’s Kit

  • SN - Serial Number

  • UIK - Unique Identifier Key

  • Force update – Supplying Version:0 in the web API call. Otherwise RMS determines of update.

Overview

The MagTek Reader Configuration Gen II Program is an application designed to leverage the MagTek RS3 web services, for secure key injection and device configuration of DynaFlex family devices.

By running the MagTek Reader Configuration Gen II Program, the user can configure their device and load keys in a secure environment.

Windows System Requirements:

  • Windows 10 Operating System or newer

  • USB Port

***Not All Configuration Options are available to all SCRAs

Configuration Options available are determined—

  • By the type of device being used

  • By the Configuration Options provided by MagTek

***Key Loading via a Bluetooth wireless interface is not supported. This affects any wireless MagneSafe reader. Key injection for wireless readers must be done via USB using the MagTek Reader Configuration Gen II Program.

***Certain COMMANDS require a reset of the device

  • Please see the individual device’s Programmer’s Manual for affected Commands

Qwantum Secure Cards

An interactive browser-based demonstration for MPPG/Unigate. The demos show various use cases with and without using MagTek readers.

A client‑side JavaScript library from MagTek that enables secure, browser‑based tokenization of sensitive payment data before it ever reaches your servers.

A cloud-based web service where encrypted data from MagTek readers is sent to Magensa for secure, centralized decryption

A PCI-DSS certified cloud gateway service that acts as a secure "wrapper," allowing developers to safely deliver payloads of any format to any destination.

Documentation and demo code to help you integrate Apply MobilePay.

Support and information for older Magensa services.

Reference Section

Information Available

Account Management

Magensa's Account Management API allows Resellers to manage their merchants' account. The goal is to provide an API that parallels the current Reseller Portal UI.

Magensa API Documentation and Code Demos

Need More Help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email:

Qwantum Private Messaging

Videos

Videos

Login

  • The Login box will appear.

  • Enter your User Name, Password and Customer Code provided to you by MagTek.

  • Checking the Save Login Credential will cache the user’s credentials to streamline future login.

  • Press LogIn.

For certain “no charge” configuration related functions, the Public Account can be used by pressing the “Use Public Account” button.

Videos

Videos

Linux Sample Code Manual

Manual Part Number: D998200733-100

REGISTERED TO ISO 9001:2015

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.

MagneSafe Security Architecture

The MagneSafe® Security Architecture (MSA) is MagTek's core digital identification and authentication framework, designed from the ground up to safeguard consumers and their personal data in payment, access, and other high-value electronic transactions. Exceeding standard PCI regulations, MSA integrates multiple layers of defense: strong encryption, secure tokenization, counterfeit detection, tamper recognition, data relevance and integrity, and dynamic digital transaction signatures—all working together to validate and protect each component of a transaction. This architecture is supported across the entire payment ecosystem, including MagTek terminals, devices from Verifone, Hypercom, and Ingenico, ATMs, PCs, and mobile platforms like iOS and Android.

The official MagTek MagneSafe Security Architecture support page is a central hub for key documentation and updates. There you can find a comprehensive White Paper ("Overview and Industry") that explores the security challenges in the payment industry and how MSA addresses them. While there are no software downloads, FAQs, or videos available at the moment, the page includes an RSS feed you can subscribe to for notifications on the latest software, SDKs, APIs, and demo programs related to MSA.

Apple MobilePay

This page will help merchants and developers to integrating Apple Pay into an iOS app (In-App) or web app (In-Web). The Apple Pay tokens produced from the merchant's app will be processed through Magensa Payment Protection Gateway (MPPG v4/v3).

Reader Configuration Gen II Installation and Operation Manual

Manual Part Number: D9982000480-10

REGISTERED TO ISO 9001:2015

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

MagneSafe® is a trademark of MagTek, Inc.

Wedget

Wedget™ is a developer tool and keyboard extension application for both iOS and Android mobile devices that simplifies card data acquisition from MagneSafe® Secure Card Reader Authenticators (SCRAs). Instead of requiring complex programming with a full SDK, Wedget allows developers to securely capture and process sensitive payment and ID card data by simply creating a standard text box in their application workflow. When the user selects the Wedget keyboard and presents a card, the extension acts as a bridge, parsing the data into a JSON format that the target application can then pass along to MagTek’s Magensa Services for processing. The application supports a wide range of MagTek devices, including the eDynamo and DynaFlex II Go..

The official MagTek Wedget support page is a central hub containing all the resources you'll need. There you can find product brochures (including the Wedget Brochure, the MagTek Hardware and Magensa Gateway Solutions Product Catalog, and the Magensa Services Overview), user manuals (such as the Wedget Installation and Operation Manual for both iOS and Android), and developer resources (including the Pursuing L3 Certification developer guide).

Qwantum Tokens & QMFA Wallet

MagTek’s Qwantum Platform is a next-generation tokenization and authentication framework designed to replace outdated security models with real-time, user-initiated, and cryptographically secure authentication of Qwantum Tokens. Qwantum Tokens can be used in place of legacy credentials and used for a specific purpose, such as granting access to a facility, to a website, to loyalty points, or stored value for coupons and closed-loop payments.

The platform supports both card-present and digital environments, offering a mobile-first, yet flexible approach to eliminate static credentials that contain personally identifiable information (PII), prevent fraud, while strengthening and modernizing access and identity management.

The Qwantum Platform is based on an extensive set of APIs, embedded circuits, hardware and services that have been integrated to generate powerful tokens, including advanced delivery options, lifecycle management, and redemption services, all backed by powerful Qwantum Multi-Factor Authentication or QMFA. The official MagTek Qwantum Platform support page is a central hub containing the resources you'll need. There you can find a product brochure, user manuals (including the QMFA Wallet Installation and Operation Manual for Android/iPhone and Apple Watch), and a white paper covering Qwantum Media Solutions. At this time, software downloads, a comprehensive FAQ section, and instructional videos are not listed on the support page.

Installation

Open your browser and navigate to the URL below.

  • Download the zip file and extract its contents to an accessible folder on a Windows computer

  • Double-click the setup.exe

Services

This page is the gateway to MagTek Services, a group of payment technologies that help process, secure, and support MagTek's payment hardware. MagTek's services include , a cloud-based payment protection gateway. is a group of digital security services that include a front-end decoder, tokenization and authentication frameworks, private messaging, and secure physical cards. is a cloud-based platform for remotely managing fleets of MagTek payment devices.

Support >

Support >

📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    MMPG/Unigate
    TokenExchange Connect
    Decrypt
    Decrypt & Forward
    Apple MobilePay
    Archive
    support@magtek.com
    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.

    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.

    Rev Number
    Date
    Notes

    100

    May 11, 2026

    Initial release.

    IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO THE ADDRESS ON THE FRONT PAGE OF THIS DOCUMENT, ATTENTION: CUSTOMER SUPPORT.

    MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the "Software."

    LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products. LICENSEE MAY NOT COPY, MODIFY, OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT. Licensee may not decompile, disassemble, or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with, bypass, or alter any security features of the software or attempt to do so.

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

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

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

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

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

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

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

    GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void, or unenforceable, that provision shall be removed from consideration under this Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of the State of California and shall inure to the benefit of MagTek, Incorporated, its successors or assigns.

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

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

    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.

    Linux Sample Code Manual

    Table – Revisions

    SOFTWARE LICENSE AGREEMENT

    TERMS, CONDITIONS, AND RESTRICTIONS

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

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

    Rev Number
    Date
    Notes

    10

    May 2021

    Initial Release

    The information contained herein is confidential and proprietary to: MagTek, Inc.

    1710 Apollo Court Seal Beach, CA 90740 562-546-6400

    The purpose of this document is to provide a description of how to use the MagTek Reader Configuration Gen II Program for Remote Configuration and Key Injection for MagneSafe devices. This application is provided to MagTek Customers. Certain functions are No Charge and other functions are billable events. Please refer to the executed Remote Services Agreement and Pricing Schedule A.

    Information in this document is subject to change without notice. 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.

    Table 0.1 - Revisions

    Purpose of the document

    Web Demo

    Description

    The support page contains downloadable software and instruction manuals.

    MagneSafe Security Architecture Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Web Demo

    Description

    Wedget is a developer tool/extension to simplify card data acquisition for mobile browsers and native applications for MagneSafe® secure card reader authenticators (SCRAs)

    Wedget Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Qwantum MFA

    Click the Install button.

    After the installation is complete, launch Reader Configuration Gen II.

    https://www.magtek.com/Content/SoftwarePackages/1000008207.zip

    Go to this page to view real‑time service health, incident history, and maintenance updates for QwickCards.

    Service Page

    Description

    MagTek's cloud-based payment protection gateway that secures sensitive data and processes transactions across in-person, online, and mobile channels using advanced tokenization, dynamic encryption, and authentication services.

    A group of digital security services including ASIC, a front-end decoder for magnetic stripe card reader systems, tokenization and wallet functions, a private messaging app, and physical secure cards.

    MagTek's cloud‑based platform for remotely managing fleets of MagTek payment devices. RMS enables merchants, ISVs, and integrators to monitor device health, push firmware updates, manage EMV configuration files, and perform diagnostics.

    Reference Section

    Information Available

    Magensa Services Status

    Go to this page to view real‑time service health, incident history, and maintenance updates for Magensa.

    Service Status Pages

    Magensa
    Qwantum
    Reader Management Services

    MagTek Service Pages

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Web Demo

    Description

    Mobile Payments (Apple Pay)

    Documentation and demo code to help you integrate Apply MobilePay.

    Web-based Demos

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    Overview

    This document provides instructions to use the RMS Sample Code. Combining MagTek Linux SDK and web API calls to the Reader Management System (RMS) web service, the sample code assist in setting configurations, key injection, updating EMV Tags/CAPKs, and updating firmware for MagTek readers. The sample code is parsed into a collection of CLI apps (command line interface).

    • Configuration app

    • EMV Tags app

    • Firmware app

    For details on the RMS API see:

    This sample code is built with a public RMS Profile. MagTek will provide the necessary Profile configurations and authorization Web API Keys if requested.

    The MagTek Reader Management System (RMS) provides several key benefits for merchants and businesses, these include:

    • Centralized Management: RMS allows for the remote management and configuration of MagTek readers across multiple locations from a single platform. Merchants can update firmware, keys, terminal settings, and CAPKs without manual intervention, reducing time, cost, and effort.

    • Enhanced Security: RMS supports compliance with industry standards, such as PCI DSS, by ensuring secure payment card transactions and protecting sensitive customer data. It enables a secure process for keeping readers up to date with the latest firmware and configurations.

    • Efficient Updates: RMS automates firmware updates and maintenance, allowing merchants to push updates remotely. This ensures all devices run the latest firmware, enhancing system reliability and reducing the need for manual updates.

    The following packages are needed on the Linux host to build the sample code. Other dependencies are included in the makefile.

    • make

    • cmake

    • g++

    • Unzip the package.

    • Go to Sample folder:

    • Build the sample code using:

    Various libraries and folders are generated. The two folders used for RMS Sample code are:

    Folder
    Description

    Each sample code folder contains an account credential for access to RMS. This is by default configured for general public use. When accessing RMS for a custom profile, reassign the values as needed in the files:

    RMS MMS Sample Code

    1

    Go to the folder: rms_mms and open a terminal.

    2

    Connect the reader to a USB port.

    3

    Decrypt

    Magensa Decrypt is a PCI-DSS-certified cloud service that performs centralized decryption of data captured by MagTek MagneSafe readers — returning decrypted card data, MagnePrint scores, and transaction IDs without that sensitive data ever touching your own environment. It handles anything a MagneSafe reader encrypts, from full card swipes to individually encrypted fields, and is frequently paired with the Decrypt & Forward (DaF) service to route decrypted payloads on to third-party endpoints. Use the references below to explore the Decrypt web service and related MPPG payment operations, grab sample code from GitHub, or open the support hub for manuals, brochures, FAQs, and videos.

    Account Management

    Magensa's Account Management API allows Resellers to manage their merchants' account. The goal is to provide an API that parallels the current Reseller Portal UI.

    Support >

    feedback@magtek.com

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    Support Page
    support@magtek.com

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    Support Page
    support@magtek.com

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    QwickCards Status
    Magensa
    Qwantum
    Reader Management Services
    support@magtek.com

    System Reporting: RMS offers reporting capabilities to track firmware versions and device settings, providing detailed insights by serial number for firmware, terminal, and CAPK updates in both production and test environments.

  • Scalability and Flexibility: RMS is scalable to meet the needs of businesses, whether for a single store or multiple locations.

  • Cost Savings: Automating reader management with RMS reduces the need for on-site visits, lowering maintenance costs and minimizing downtime. Centralized control streamlines administrative tasks, boosting operational efficiency.

  • Improved Customer Experience: Efficiently managed payment readers reduce transaction errors and delays, improving customer satisfaction and loyalty, which positively impacts business reputation and revenue.

  • /rms_mms

    For DynaFlex readers: DynaFlex II PED, DynaFlex II Go, DynaProx, DynaFlex Pro, DynaFlex SCRA

    /rms_scra

    For V5 readers: mDynamo, tDynamo, Dynamag, Dynawave, iDynamo 6, eDynamo, DynaPad

    Onboarding

    Benefits

    Requirements

    Building RMS Sample Code

    https://rmsv2.developer.magtek.com
    $ cd Sample
    $ make
    {
    “rms_server”: “https://svc1.magensa.net”, 
    “api_key”: “MTPublic...”,
    “profile_name”: “MagTek_Production”
    }

    Enter command below. Enter password if prompted. This is for device port access.

    $ sudo ./rms_mms_config_update
    4

    A list of available configurations is returned. List depends on the firmware ID and RMS Profile. Example:

    Device Serial Number:B568DAF
    Main Firmware ID:1000009714-AB3-PCI Response Code:200
    ResultCode: 0 Result: Success
    Configurations Available: 3
    1: Mask4Zero4
    2: SCDEEnableNameExpirationDateServiceCode
    3: Mask8Asterisk4_DynaFlex
    Enter '1'...'3' to update configuration.
    To force update configuration, enter '*' before the number ('*1'...'3').
    Enter '0' to exit:
    5

    At the prompt, select a configuration by entering its number listed to its left. A sequence of commands are downloaded from RMS and sent to the reader. Status of the configuration is shown as updated or failed and the end of the sequence.

    Selected Configuration 1 Updating Configuration... Configuration: Mask4Zero4 CommandsToDevice (1)
    Name: LeadingUnmaskedCharacters Command:
    SENDCOMMAND,AA0081040110D111841BD11181072B06010401F609850101890BE109E2 07E205E103C30104
    CommandsToDevice (2)
    Name: PANMaskedCharacter
    .
    .
    .
    Configuration Mask4Zero4 has been updated.
    6

    Whenever a configuration reports is up to date, it may be redone by entering *N, where N is the configuration. Example: *1

    1

    Go to the folder: rms_mms and open a terminal.

    2

    Connect the reader to a USB port.

    3

    Enter command below. Enter password if prompted. This is for device port access.

    4

    The parameters for the firmware update is as follows:

    5

    Example for updating MAIN firmware.

    6

    If an update is available, the change note for the update is shown. Below that, a confirmation to update is shown. Enter y to update.

    7

    A sequence of commands are downloaded from RMS and sent to the reader. Status of the update is shown as finished or failed and the end of the sequence.

    Configuration Update

    EMV Tags/CAPKs Update

    Integration guide and MPPG operations for accepting Apple Pay both in-app (iOS) and in-web (via TokenExchange Connect), including merchant-ID and domain-verification setup.

    Integration guide and the MPPG ProcessGooglePay operation for accepting Google Pay in a mobile app, from wallet setup through submitting the payment token.

    Create a customized payment request that returns a payment URL, QR code, and a WebSocket token for real-time status; customers pay through an MPPG hosted page by manual entry or digital wallet.

    Accept PayPal and Venmo via QR code (QRC) — read as clear text or as encrypted data from a MagTek QR-capable reader — with Sale, Void, and Refund supported through MPPG.

    API Section

    Description

    GitHub makes it easier to access sample code, use the Magensa Bluetooth Playground, access the utility package for TokenExchange, and so much more.

    API Section

    Description

    The Magensa Decrypt support hub — programmer's manuals (including the Decrypt 3.0 API guide and MICR decryption), product brochures, multi-language code samples, FAQs, and instructional videos.

    API Section

    Description

    Decrypt

    Decrypt APIs

    Magensa's core decryption web service (SOAP): send data encrypted by a MagTek MagneSafe reader and get it back decrypted. Three operations cover card swipes, arbitrary data blocks, and MAC generation.

    Decrypt GitHub

    Decrypt Support Page

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Web Demo

    Description

    Account Management

    Endpoints in this folder support reseller merchant account discovery and transaction reporting.

    Lookup

    Web-based Demos

    This demonstrates how to perform a simulated vending transaction for an EMV Sale using a MagTek card reader and MPPG/Unigate.

    ​Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Archive

    This archive page provides access to historical and reference documentation for legacy Magensa web services, security architectures, and integration tools, including decryption services, payment gateways, tokenization, remote device management, and browser-based middleware that help developers securely process transactions and manage MagTek hardware.

    Archive Services

    Service

    Description

    A developer tool and keyboard extension application for both iOS and Android mobile devices that simplifies card data acquisition from MagneSafe® Secure Card Reader Authenticators (SCRAs).

    Decrypt & Forward

    Magensa Decrypt & Forward (DaF) is a PCI-DSS-certified cloud gateway that acts as a secure "wrapper": it decrypts data captured by a MagTek MagneSafe reader, injects the decrypted card fields into a payload of your choosing, and forwards the request to any third-party endpoint on your behalf — even one with no decryption service of its own. Built on the MagneSafe Security Architecture with L3-certified hardware, TDEA/AES encryption, and DUKPT key management, it handles every major payment type — magstripe, EMV contact and contactless, NFC wallets like Apple Pay and Google Pay, QR codes, gift cards, and more — and is certified with the major US processors, giving ISVs and integrators a single integration point that speeds time to market and shrinks PCI scope. Use the references below to explore the DaF API and related payment operations, grab sample code from GitHub, or open the support hub for manuals, brochures, developer guides, and videos.

    Decrypt & Forward APIs

    API Section

    Description

    Remote Services Support

    MagTek Remote Services is a cloud-based device management platform from Magensa that enables organizations to remotely configure, update, and maintain MagTek payment readers already deployed in the field. Traditionally, updating encryption keys or firmware on a device required physically removing it from the payment environment and shipping it back to the factory—a costly and time-consuming process that led to significant downtime. MagTek Remote Services eliminates this need by allowing administrators to perform remote key injection, device configuration, firmware updates, EMV tag and CAPK loading, and even run batch scripts—all from a central location without ever touching the terminal. The platform is built on top of the MagTek Reader Management System (RMS), a suite of applications and source code that automates configuration and updates across large, geographically distributed fleets of MagTek readers.

    Remote Services is available in three versions:

    • RS2, which supports legacy devices such as the uDynamo, iDynamo 5, cDynamo, eDynamo, DynaMAX, tDynamo, kDynamo, iDynamo 6, MICRSafe, and the DynaPro family.

    • RS3, which supports the newer DynaFlex and DynaProx product lines.

    • RMS, which supports a broader range including the DynaFlex II PED, DynaFlex II SCR, DynaFlex II Go, and DynaProx. MagTek’s Key Injection Facility and Magensa’s Remote Key Injection services are PCI PIN compliant and undergo regular external audits to maintain Attestation of Compliance.

    The official MagTek Remote Services support page is a central hub containing all the resources you'll need. There you can find product brochures (including the Magensa Remote Services brochure, the MagTek Hardware and Magensa Gateway Solutions Product Catalog, and the Magensa Services Overview), programmer’s manuals and API references (including the Magensa Web Services Remote Services Operations Manual for both PPSCRAs and SCRAs, as well as the MICRSafe Remote Services Reference Manual), software downloads and configuration tools (including the MagTek Reader Configuration Program for Windows ClickOnce, Android, and iOS devices, which leverages Remote Services 2 and 3 web services), user manuals and installation guides (covering the Remote Services App for configuration and key injection, as well as the Virtual Terminal user manual), a comprehensive FAQ section, and instructional videos.

    RMS SCRA Sample Code

    • Go to the folder: rms_scra and open a terminal.

    • Connect the reader to a USB port.

    • Enter command below. Enter password if prompted. This is for device port access.

    Videos

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    Mobile Payments (Apple Pay)
    Mobile Payments (Google Pay)
    Payment Request
    PayPal/Venmo
    Magensa Decrypt GitHub
    Support Page
    support@magtek.com

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    support@magtek.com

    A list of available configurations is returned. List depends on the firmware ID and RMS Profile. Example:

    • At the prompt, select a configuration by entering its number listed to its left. A sequence of commands are downloaded from RMS and sent to the reader. Status of the configuration is shown as updated or failed and the end of the sequence.

    • Whenever a configuration reports is up to date, it may be redone by entering *N, where N is the configuration. Example: *1

    • Go to the folder: rms_scra and open a terminal.

    • Connect the reader to a USB port.

    • Enter command below. Enter password if prompted. This is for device port access.

    • The sample code downloads the sequence of commands to update the EMV Tags and CAPKs available for the reader. Example:

    • Whenever a configuration result is: Configuration is up to date it may be redone by adding -f to force the update.

    • Go to the folder: rms_scra and open a terminal.

    • Connect the reader to a USB port.

    • Enter command below. Enter password if prompted. This is for device port access.

    • The parameters for the firmware update is as follows.

    • Example for updating MAIN firmware.

    • A sequence of commands are downloaded from RMS and sent to the reader. Status of the update is shown as finished or failed and the end of the sequence.

    • Whenever a firmware result is: Firmware is up to date. It may be redone by adding -f to force the update.

    Configuration Update

    EMV Tags/CAPKs Update

    Firmware Update

    $ sudo ./rms_mms_firmware_update
    rms_mms_firmware_update TYPE
        TYPE (type of firmware): MAIN|BOOT1|BLE|WLAN
    $ sudo ./rms_mms_firmware_update MAIN
    Firmware update is available.
    New Firmware: FIRMWARE, DYNAFLEX II GO MAIN APP PCI (COMMON KERNEL),
    Version AB3
    .
    .
    .
    Do you want to update the MAIN firmware? (y/N)
    Updating MAIN firmware...
    Beginning DYNAFLEX II GO MAIN APP PCI (COMMON KERNEL)
    Updating firmware... [1%]
    .
    .
    .
    [100%]
    result (0)
    Firmware update done.
    Saving Firmware Image - Please Wait... Wait for 30000 ms...
    Done waiting. Detecting device...
    Detecting Device: GetDeviceList Detecting Device: GetDeviceList > 0 Detecting Device: Found USB Device Device detected.
    Finished DYNAFLEX II GO MAIN APP PCI (COMMON KERNEL)
    $ sudo ./rms_scra_config_update
    Device Serial Number:000F423536413943343130323432344141 Main Firmware ID:000D31303030303039323734613032
    Response Code:200 ResultCode: 0 Result: Success
    Configurations Available: 5
    1: DataVariant
    2: Mask6Zero4
    3: EMVNotificationsBoth
    4: Mask8Zero2Mod10
    5: Mask8Asterisk4
    Enter '1'...'5' to update configuration.
    To force update configuration, enter '*' before the number ('*1'...'*5').
    Enter '0' to exit:
    Selected Configuration 1 Configuration: DataVariant Sending command [0900]
    Response: 000A9011880B56A9C4000001
    Sending command [1900]
    .
    .
    .
    Done Changing to DataVariant
    Configuration DataVariant has been updated.
    $ sudo ./rms_scra_emvtags_capks_update
    Device Response: 000D31303030303039323734613032 Main Firmware ID:000D31303030303039323734613032
    Device Response: 001F423536413531313130323232344141009014500B56A5110000005344C35C6F UIK:001F423536413531313130323232344141009014500B56A5110000005344C35C6F
    Get Terminal Config (0) Extended Command: 03060008010000FA03DFDF26 Extended Response: 000000180016FA820012DFDF260E4D414754454B2044454641554C54
    Result Code: 0000
    Value: 4D414754454B2044454641554C54
    Value String: MAGTEK DEFAULT DB Name: MAGTEKDEFAULT
    Get Terminal Config (1) Extended Command: 03060008010001FA03DFDF26 Extended Response: 03950000
    Get Terminal Config (2) Extended Command: 03060008010002FA03DFDF26 Extended Response: 03950000
    Get Terminal Config (3) Extended Command: 03060008010003FA03DFDF26 Extended Response: 03950000
    Get Terminal Config (4) Extended Command: 03060008010004FA03DFDF26 Extended Response: 03950000
    .
    .
    .
    Done Loading MagTek Default Contact Tags and CAPK Configuration MAGTEKDEFAULT has been updated.
    $ sudo ./rms_mms_emvtags_capks_update -f
    $ sudo ./rms_scra_firmware_update
    rms_scra_firmware_update TYPE
        TYPE (type of firmware): MAIN|BLE
    Firmware update is available.
    New Firmware: Main_1000009274 version A02 firmware
    .
    .
    .
    Do you want to update the MAIN firmware? (y/N)
    Updating MAIN firmware...
    Beginning mDynamo firmware Main 1000009274 version A02 firmware Updating firmware...
    .
    .
    .
    Sending command [94255A00044A6000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFF]
    Response: 0000
    Sending command [95015A] Response: 0000
    Sending command [0200]
    Response: 0000
    Wait for 15000 ms... Done waiting.
    Detecting device...
    .
    .
    .
    Device detected.
    Sending command [970100]
    Response: 0000
    Finished mDynamo Firmware-1000009274-A02 Update MAIN Firmware update completed.
    $ sudo ./rms_scra_firmware_update MAIN -f

    Magensa Payment Protection Gateway

    A unified, cloud‑based payment gateway that simplifies PCI compliance by providing a single, flexible interface for processing magstripe, EMV chip, contactless, and card‑not‑present transactions across multiple merchant processors.

    MagneFlex

    A suite of no‑royalty, free‑to‑distribute browser and middleware tools (Navy, Blue, Sky, Powder, Prism) that let developers integrate MagTek hardware with web and network applications without writing platform‑specific code or managing separate SDKs.

    MagneSafe Security Architecture

    An open, multi‑layer security foundation built on strong encryption (3DES/AES), DUKPT key management, tokenization, and MagnePrint authentication that protects cardholder data from the moment of swipe, dip, or tap while helping exceed PCI requirements.

    Remote Services Support

    A web service and virtual‑terminal capability that enables over‑the‑air remote key injection, configuration changes, firmware updates, and diagnostics for MagTek secure readers already deployed in the field, eliminating costly factory returns.

    TokenExchange

    A REST‑based tokenization service that creates and redeems secure tokens (Token, StoredToken, PaymentToken, InvoiceToken) for sensitive data, reducing the risk and compliance scope of storing primary account numbers and other confidential information.

    ​Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    Wedget

    Mobile Payments (Apple Pay)

    Setup and integration guide for accepting Apple Pay both in-app (iOS) and in-web (via TokenExchange Connect), including merchant-ID registration and domain verification.

    Mobile Payments (Google Pay)

    Setup and integration guide for accepting Google Pay in a mobile app, from business-profile setup through submitting the Google Pay token (ProcessGooglePay).

    Payment Request

    Create a customized payment request that returns a payment URL, QR code, and a WebSocket token for real-time status; customers pay through an MPPG hosted page by manual entry or digital wallet.

    Decrypt and Forward (DAF)

    The core Decrypt & Forward 4.0 web service: send encrypted MagneSafe data plus a target payload (SOAP or JSON), and Magensa decrypts it, injects card fields via replacement variables (e.g., {CCNum}), and forwards the request to any third-party service — processors, tokenization, gift cards, and more. v4.0 adds batched requests.

    API Section

    Description

    Magensa Decrypt and Forward GitHub

    GitHub makes it easier to access sample code for Decrypt & Forward v4, try the Magensa DaF Playground, and more.

    API Section

    Description

    Support Page

    The Magensa Decrypt & Forward support hub — programmer's manuals (including the DaF v4.0 Web Services API guide), product brochures and catalog, developer guides, an FAQ, and instructional videos.

    Decrypt & Forward GitHub

    Decrypt & Forward Support Page

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    Web Demo

    Description

    Support Page

    The support page contains downloadable software and instruction manuals.

    Remote Services Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    feedback@magtek.com
    feedback@magtek.com
    feedback@magtek.com

    Transaction Options

    The Device Information window will appear in the upper right corner of the application. It provides the following information about the attached DynaFlex device:

    • MagTek Protocol

    • Connection Type

    • Device Model

    • Serial Number

    • Firmware

    • Device and Serial Number

    • Device List displays a list of attached devices. please select the target device and proceed. The Rescan button updates the list of Target Devices visible to the MagTek Reader Configuration Gen II Program.

    • Open Device will open the reader.

    • Close Device will close the reader.

    The Key Configuration tab can be used to change a device’s key(s). It shows the Key(s) currently Loaded. DynaFlex family devices can have several types of keys injected or loaded. There is also a drop-down list of Key to Update. This drop-down list will show the KSID.

    To perform an Update Key, click on the Keys Loaded drop down list, and select the desired key slot.

    Click the Available Key to Update drop down list and choose the desired KSN.

    Click the Update Key button to inject the designated KSID into the designated key slot.

    The following message will appear Updating Key, Please Wait.

    The following message will appear after the Key is successfully injected.

    EMV Configuration allows the user to Load EMV tags (terminal and application settings) and CAPKs (certificate authority public keys). The file format is *.xlsx. Please contact MagTek for assistance with the desired information.

    Click the Browse button to locate the desired *.xlsx file.

    Once the file is selected, click the Update button to load the selected *.xlsx file.

    Device Configuration allows the user to Load Firmware and load image files.

    Click the Browse button to locate the desired *.bin file.

    Once the file is selected, click the Update button to load the selected *.bin file. Please note, this application will not load an older version of firmware than what is currently loaded, and it will also not overwrite the same version currently loaded. This tool can only be used to update to a newer revision of firmware. If you need assistance with older revisions, please contact your MagTek representative.

    Load Images allows the user to import as many as 4 custom images that can be displayed on DynaFlex Pro. The file format must be *.bmp and the file size must be 320 x 240 for Landscape and 240 x 320 for Portrait. Image Slot 0 is reserved for the default Welcome Screen and cannot be changed. Image Slots 1 – 4 are available to the user.

    Click the Browse button to locate the desired *.bmp file.

    Once the file is selected, click the Load Image button to load the selected *.bmp file in the Slot chosen.

    A message will display indicating the Image is being sent to the DynaFlex Pro. If successful, the following message will display.

    Next, press the drop down for “Select active image slot” and press the Set Image button.

    Press the Yes button to complete the process and rest DynaFlex Pro. After the reset, the selected image will display on screen.

    Magensa Payment Protection Gateway (MPPG)

    The Magensa Payment Protection Gateway (MPPG) is a PCI‑DSS certified cloud payment gateway service built on the MagneSafe® Security Architecture and designed to make PCI compliance easier, safer, and faster. It supports traditional payment transactions including Sale, Auth, Capture, Void, and Refund to integrated processor endpoints. MPPG accepts a comprehensive range of payment types: magnetic stripe, EMV contact and contactless, NFC mobile wallets (including Apple Pay® and Google Pay™), QR codes, barcodes, manual entry, invoicing, subscriptions, cards on file, in‑app payments, touch‑free and unattended payments, as well as PayPal and Venmo. It is built for ISVs, ISOs, VARs, resellers, and integrators who supply payment processing solutions that work with both encrypted and decrypted data. MPPG secures transactions across retail, healthcare, restaurant, hospitality, government, education, and transportation industries. The gateway is certified with L3 processors, and a single integration with Magensa provides access to multiple processor endpoints. Additional features include hosted payment pages and iFrames for e‑commerce and in‑app payments, touch‑free QR‑based pay‑at‑the‑table, payment request links, and cross‑merchant tokens for payment credentials on file.

    The official MPPG Service support page is a central hub containing all the resources you'll need. There you can find product brochures (including the MPPG overview brochure, the 2024 Hardware and Gateway Solutions Catalog, and the Magensa Services Overview); programmer's manuals covering the MPPG v4.0 API, Payment Request API, PayPal/Venmo API, and Google Pay/Apple Pay in‑app integration; user manuals for the Merchant Portal and Reseller Portal; developer guides for omnichannel development and L3 certification; sample code and developer sandbox tools on GitHub; XML/SOAP sample requests for both MPPG v3 and v4; white papers and use case studies (including Quantic, CryptoPay car wash, and laundromat); an RSS feed for software, SDKs, API, and demo program notifications; a Developer Portal with dedicated resources for Apple Pay, Google Pay, Payment Request, PayPal/Venmo, and Unigate MPPG v5+; a comprehensive FAQ section; and instructional videos.

    Web Demo

    Description

    Support Page

    Magensa delivers a Payment Protection Gateway, that makes PCI compliance easier, safer and faster with a flexible and safe way to conduct payment transactions

    Magensa Payment Protection Gateway (MPPG) Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    Key Configuration

    Update Key

    EMV Configuration

    Update Tags and CAPKs

    Update Firmware

    Load Images

    MagneFlex

    MagneFlex is a comprehensive suite of software integration tools from MagTek, designed to dramatically speed up time-to-market and reduce the complexities and headaches that come with payment device certification compliance. At its core, MagneFlex serves as a bridge that drives the hardware, interfaces with your POS application, and issues the commands to pack, parse, and send transaction data out for processing. Available as both a browser-based application and middleware,

    MagneFlex includes several variants to suit different development environments:

    • MagneFlex Navy is a full-function HTML browser for Windows that integrates device drivers to control MagTek payment devices from an HTML over HTTP(S) context.

    • MagneFlex Blue is a full-function browser for iOS app development, offering a fast track into the App Store and eliminating the need for plug-ins.

    • MagneFlex Sky is a full-function browser for Android app development, available on Google Play and the Amazon app store, also requiring no plug-ins and supporting optional white labeling.

    • MagneFlex Powder is a lightweight middleware application for Windows that provides an HTTP command API (receiving JSON calls mapped to the device's low-level command set) and can be launched as a Windows Service or a standalone executable.

    • MagneFlex Prism, a suite of interface developer tools that reduces the points of development by allowing you to build a single interface to just MagneFlex, rather than building separate interfaces to the hardware, the POS application, and the gateway.

    All MagneFlex tools come with no royalty or maintenance fees and are free to redistribute with your application. The official MagTek MagneFlex support page is a central hub containing all the resources you'll need. There you can find product brochures including MagneFlex Prism, the MagneSafe Secure Ecosystem overview, and the 2024 Hardware and Magensa Gateway Solutions Product Catalog; software downloads and documentation for MagneFlex Navy, Blue, Sky, and Powder; programmer's manuals and API references; developer guides for pursuing EMV L3 certification; and a comprehensive FAQ section with instructional videos.

    feedback@magtek.com

    Web Demo

    Description

    Support Page

    The support page contains downloadable software and instruction manuals.

    MagneFlex Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    TokenExchange Connect

    TokenExchange Connect is a client‑side JavaScript library from MagTek that enables secure, browser‑based tokenization of sensitive payment data before it ever reaches your servers. Part of the Magensa TokenExchange ecosystem, TokenExchange Connect allows merchants, ISVs, and developers to capture cardholder data directly from a web browser and exchange it for a PCI‑compliant, vaultless token—without requiring the underlying PAN to pass through the merchant's infrastructure. The library works by establishing a direct, encrypted connection between the end‑user's browser and Magensa's PCI‑certified TokenExchange service, where the card data is tokenized in real time. The resulting token can then be safely stored or transmitted to your application for subsequent payment operations (e.g., Sale, Auth, Capture) via the TokenExchange REST API or Magensa Payment Protection Gateway (MPPG). TokenExchange Connect supports all major web browsers, integrates easily with existing checkout forms, and helps reduce PCI DSS scope by eliminating inbound cardholder data handling. The service is ideal for e‑commerce websites, recurring billing portals, and any web‑based application requiring secure card capture.

    The official MagTek TokenExchange Connect support page is a central hub containing all the resources you'll need. There you can find product brochures (including the Magensa TokenExchange Connect overview), programmer's manuals and API references (covering the TokenExchange Connect JavaScript library and integration with TokenExchange v2.0), software downloads including the latest version of the TokenExchange Connect library and sample code, developer guides with step‑by‑step integration examples, a comprehensive FAQ section, and instructional videos.

    TokenExchange Connect Support Page

    feedback@magtek.com

    API Section

    Description

    Support Page

    The Magensa TokenExchange Connect support hub — programmer's manuals, product brochures, multi-language code samples, FAQs, and instructional videos.

    TokenExchange Connect

    Videos of Magensa Tokenization Services

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    MPPG/Unigate

    This page is your entry point for integrating with MPPG/Unigate, Magensa's API for omni-commerce payment processing across both card-present and card-not-present channels. Use the Unigate API reference below to explore transaction types, credentials, and processor responses in an interactive Postman collection, or open a web-based demo to watch the full flow in action — from a MagTek reader, through the browser, to the gateway and back — with or without physical hardware.

    feedback@magtek.com

    What Unigate is and how it works — a single, unified API that normalizes requests and responses across multiple processors and hardware, covering card, Apple Pay, and Google Pay payments via MPPG V5 or later.

    Get running quickly: copy the Postman collection, format your Pilot credentials as Basic Auth, and send your first EMV Sale or Authorize against your test account.

    Sample responses from each supported processor (Fiserv, TSYS, Worldpay, Heartland, EPX, Chase, Elavon), showing how status, date, and amount formats differ between them.

    Normalized Processor Response Fields

    A standardized response structure (added March 2025) that maps processor-specific fields to common keys, so you can consume results consistently without per-processor parsing.

    Transaction

    Initial financial requests to a processor (for example, Sale or Authorize), organized by entry method and payment type.

    Process a chip-card transaction (contact or contactless) using the EMV ARQC cryptogram read from a MagTek device.

    Charge a stored token — issued by the Tokenization service or returned from a prior transaction — in place of raw card data.

    Process a magnetic-stripe transaction from encrypted swipe data captured by a MagTek reader.

    Process a transaction from card data entered on the device's secure keypad.

    Process a card-not-present transaction from card data keyed into your application.

    Accept Apple Pay inside a native mobile app using the app's Apple Pay payment token.

    Accept Apple Pay on the web through Magensa TokenExchange Connect (TEC) for eCommerce checkout.

    Accept Google Pay using the wallet's encrypted payment token.

    Reference Transaction

    Follow-up actions against an existing transaction (for example, Capture, Refund, or Void), referenced by a prior transaction rather than new card data.

    Raise the approved amount on an existing authorization — common for bar tabs, hospitality, and other open checks.

    Add or change a gratuity on a previously authorized transaction before it settles.

    Settle a previously authorized transaction to collect the approved amount.

    Return funds to the cardholder for a prior transaction.

    Cancel a transaction before it settles, releasing the authorization hold.

    Retrieve the details and status of a prior transaction by reference.

    High-performance data-transfer service for DishOut and PAX terminal integrations.

    Accept contactless payments with Tap to Pay on iPhone (MPoC) — the iPhone acts as the reader, with no separate hardware.

    Web Demo

    Description

    This demonstrates how to perform an EMV Sale transaction with a MagTek card reader and MPPG/Unigate.

    This demonstrates how to perform a simulated vending transaction for an EMV Sale using a MagTek card reader and MPPG/Unigate.

    This demonstrates the flow of a wide array of transaction types using MPPG/Unigate.

    API Section

    Description

    Intended Audience

    Unigate API

    Who this documentation is for, and what to have ready — written for hands-on developers comfortable with REST APIs, with a Postman account for running the sample requests.

    Web-based Demos

    ​Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email:

    Qwantum

    Qwantum is MagTek's collection of next-generation digital security services including ASIC, a front-end decoder for magnetic stripe card reader systems, Qwantum Tokens, a tokenization and authentication framework, QMFA Wallet for wallet functions, a Private Messaging app, and Secure Cards, a service designed to produce physical security credentials that serve as uncloneable authentication tokens for high-security applications.

    Qwantum Sections

    Section

    Description

    A next‑generation Application Specific Integrated Circuit designed to serve as the secure front‑end decoder for magnetic stripe card reader systems.

    Qwantum Private Messaging

    Qwantum Private Messaging

    White Paper

    At Qwantum Private Messaging, our core vision is the belief that all people have a fundamental right to private electronic communications and data.

    PN D998200486 v.200 10/23

    MagTek, Inc. 1710 Apollo Court, Seal Beach, CA 90740 | p 562-546-6400 | | © Copyright 2021-2023

    (From the 4th Amendment of the Bill of Rights to the United States Constitution).

    📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

  • Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation! feedback@magtek.com

    ​​MMS Unigate Local Start

    This demonstrates how DynaFlex II PED can be used to initiate a Sale transaction using its touchscreen prompts and MPPG/Unigate.

    ​​Disclaimer

    Legal notifications

    Overview
    Quickstart guide
    Processor Responses
    EMV
    Token
    CardSwipe
    KeyPadEntry
    ManualEntry
    InAppApplePay
    TECApplePay
    GooglePay
    Incremental Authorization
    Tip Adjust
    Capture
    Refund
    Void
    Recall Transaction
    Slingshot (Disgout/PAX Users Only)
    AppleTapToPay Token
    ​​MMS Unigate Demo
    ​​MMS Unigate Vending Demo
    ​​Unigate Demo
    support@magtek.com
    Those few words say it all.

    People have a fundamental right to privacy.

    They should be free to communicate with one another and have confidence that their communications are secure, private, and only shared with intended parties.

    At Qwantum Private Messaging, our core vision is the belief that all people have a fundamental right to private electronic communications and data. To that end, we have developed a “Privacy as a Service” secure messaging platform that adheres to the fundamental principles of “Privacy”, “Integrity”, and “Authenticity”.

    With Qwantum Private Messaging you are assured that any messages you create will remain cryptographically secure, authenticated, and private.

    When the Internet was introduced in the mid-1990s, it brought forth a new platform that would forever change the way that people around the world would communicate and share information. It compressed time and distance, and allowed for more efficient distribution of information, ideas, and products. It crossed international boundaries and allowed people around the world to come together in business and social endeavors. More than anything, it brought forth hope that this new platform would provide all humanity with more freedom to communicate and share ideas, and to build a better and closer-knit world community for generations to come.

    We stood at the dawn of a new Digital Age.

    As the Internet platform launched and evolved, the technology landscape quickly changed. First generation technology companies such as Microsoft and Apple recognized that Internet browsers needed to become a core component of personal computer operating systems. “Explorer” and “Safari” browsers were born. Next, the search engines and email services arrived. New companies such as Yahoo!, AOL, and Google quickly became household names. Soon, email services such as Hotmail, Yahoo, AOL, and Gmail were available to all. As communications networks advanced, we experienced faster data speeds and gained access to Text Messages.

    The advent of mobile smartphones in 2007 led to a next generation version of the “personal computer” that you could carry with you. New mobile operating systems such as Apple iOS and Google Android emerged quickly and soon dominated the technology landscape. These platforms opened the door for “mobile apps” that supported banking, shopping, travel, and much more. Soon, social media apps such as Facebook, Twitter, and YouTube appeared and cemented themselves as cornerstones of our daily lives and social fabric.

    Along this path, we saw the emergence of what is now called “BigTech”. A collective core group of technology companies that seemingly have “perfect vision” to foresee the future and limitless financial resources to develop sophisticated hardware, operating systems, applications, and cloud services.

    Amazingly, they were (are) able to offer this advanced technology to the world “FREE of charge”. It seemed too good to be true.

    Initially, we provided our complete “trust” to these entities, assuming they were benevolent organizations that simply wanted to lead us on a path towards better technology and derive nominal profits via advertising revenues. It seemed reasonable… Provide the world with amazing technology for “free”, with the “price” being advertising messages. Sure, why not?

    However, over time, little by little, we saw this “trust” erode. We discovered that the communications and content that WE provided on these platforms were no longer “ours”; instead, it became “theirs”. THEY had the right to collect, store, and analyze our data indefinitely. If you closed your account, nothing was returned; all content was their property. Innocuous terms such as “analytics” were used to disguise analysis of our browsing and shopping patterns as well as tracking of our family, social, and business connections. Presumably, all of this was done to, “enhance our shopping experience”. Many people accepted this explanation without further thought. However, for some, the initial warning flags were raised that perhaps, “something was wrong.” Perhaps the “price” we were paying for this amazing technology was higher than we understood?

    In 2013, the Edward Snowden revelations shocked the world and revealed that not only were our governments involved with bulk electronic surveillance and snooping of our digital lives, but that they were often doing so with the direct collaboration and support from the BigTech companies that we initially trusted. For the first time, it became clear that our relationship with BigTech was not what we originally understood. What was once thought to be “conspiracy theory” was now established as fact. A significant truth was revealed. We ARE being spied upon by both our governments and BigTech. More concerning, we discovered that we are viewed as “The Product”. Our thoughts, ideas, business strategies, and viewpoints are being “harvested” and “analyzed”.

    This realization led to many questions:

    • How is this information being exploited?

    • Is this legal?

    • Is this moral?

    • What is the true “price” of this?

    • What is the potential danger of this?

    Given this knowledge, 2013 could have been a watershed moment for the citizens of the world to address our governments and the BigTech sector and attempt to resolve these issues together. Surely, there must be a “reasonable” path forward where we could agree upon a balance between privacy rights, national security, and BigTech commercial interests. Unfortunately, that dialogue never occurred and no “reasonable balance” was established. A golden opportunity was missed. Instead, we ignored the concerns that were clearly in front of us and blindly proceeded forward assuming that the situation would somehow resolve itself over time. Big mistake.

    As we fast forward from 2013 to 2021, the situation has not improved. In fact, it has become worse.

    We now live in a world where ALL our digital communications are permanently collected and stored by our governments. Any time they choose, our emails, texts, phone calls, photos, GPS locations, and much more can be retrieved and analyzed. Massive Data Centers such as the NSA’s facility in Utah are no longer hidden. They are now common knowledge and an example of the “collect it all” mentality that now pervades our world’s governments.

    Along the way, BigTech also adopted a “collect it all” mentality but were not constrained by legal statutes on how they used this information. After all, WE AGREED to the “terms and conditions” set by them. In exchange for “free” access to this amazing technology we “agreed” to provide access to all our activities, comments, information, photos, and documents. For all practical purposes, this became THEIR property and how this information was to be used or shared by them was none of our business. To make matters worse, BigTech furthered their scope of operations from simply performing “analytics” of OUR personal data, to that of becoming “judges” of “appropriate content”. In 2021, BigTech doesn’t just want to KNOW about you, they now want to LABEL you. And… if they deem appropriate, CENSOR you.

    Given the current state-of-affairs, George Orwell’s 1984 novel of a dystopian “Big Brother” society now reads more like a factual “documentary” than a fictionalized book. We NOW truly live in a society where ALL our digital communications ARE collected, analyzed, and acted upon. We have few controls over the entities that are collecting this information and little understanding of what they are doing (or intend to do) with it. This situation should be of concern to all individuals who value their “privacy rights” and freedoms.

    End of history lesson.

    Digital privacy is under attack from multiple fronts:

    • Criminal organizations and threat-actors that steal strategic business data or use ransomware to hold data hostage.

    • Governments that “collect everything”.

    • BigTech companies that “analyze everything”.

    No matter where you turn, the idea of digital privacy is threatened. Left unchecked, digital privacy will soon become an extinct concept.

    • It will become a “prehistoric fossil” that we can share with our grandchildren.

    • It will become a “relic” that we can reference when our future generations ask: “What was it like to have a confidential conversation?” HOW shall we answer them?

    Is this our future? No. It doesn’t have to be.

    Is there a better path forward? Yes. Digital Privacy can be preserved.

    Practically speaking, everything shared via electronic communications can be intercepted, collected, and analyzed by criminals, threat-actors, governments, and BigTech. The potential threats to Intellectual Property, Freedom of the Press, Medical Privacy, and Strategic Business interests are obvious.

    Given this reality and the reasonable assumption that a significant segment of our society still desires to retain and protect their fundamental privacy rights, there are only two viable paths forward to resolve or mitigate these matters:

    • Implement comprehensive legislation to protect the digital privacy of citizens (e.g., “Digital Privacy - Bill of Rights”) — Path 1 is beyond the scope of this document.

    • Utilize data encryption and authentication technologies to protect digital communications and data — Path 2 can be addressed with “Private Messaging” technologies.

    Citizens and businesses CAN utilize secure private messaging technology that protects them from the prying eyes of threat-actors, BigTech, and Governments. Digital privacy can be saved!

    The remainder of this document introduces Qwantum Private Messaging by MagTek and explains how and why it provides a superior communications platform that enables fast, reliable, and secure private messaging services for both citizens and businesses.

    We draw its name from the principles of quantum physics. Nothing in nature is inherently static. Change is nature’s rule. About 500 BC, the poet Heraclitus wrote, “No man ever steps in the same river twice…”. Following these observations and quantum dynamics, the Qwantum protection engine relies on constantly morphing, unpredictable, stochastic data obtained during the transaction. Statistical evaluation provides evidence of the token’s origin and provenance. Whether the token is obtained from a Qwantum Card or as a virtual derivative delivered by a QR code or NFC, the level of security is not diminished.

    At MagTek, we are in the authentication business. We provide means to ascertain the genuineness of people and things. In the payment world we authenticate payment devices and credentials. Beyond payment, we authenticate users, endpoints, documents, messages, forms, photos, works of art, keys, NFTs, and certificates. On the internet, we answer “Are you who you say you are?” “Has this document been altered?” “Is this an original photo?” “Is this signature acceptable?” When it comes to authentication, there is nothing artificial about our intelligence.

    We are also in the data protection business. We do this by means of encryption and tokenization. Encryption and tokenization expertise is in our DNA. In the 1970s we were among the first to implement DES for PIN calculation at ATMs and POS. We built the world's first encrypting card reader to protect PANs and Track data and were early adopters of DUKPT for key management. Presently, we implemented AES DUKPT using 256-bit keys. You will find these technologies in our Qwantum ASICs, Qwantum Heads, Qwantum Peripherals, and Qwantum Terminals.

    No other organization knows more about how to use authentication, encryption, and token substitution to do good.

    Qwantum Private Messaging is developed and operated by MagTek, Inc., of Seal Beach CA.

    MagTek was founded in 1972 and has a 50-year history as a pioneer, innovator, and leader in technologies related to financial card payments and electronic transaction security. MagTek is globally trusted by leading financial institutions, retail businesses, and government agencies to provide hardware, software, and cloud services for secure electronic authentication and data protection.

    Given the current state-of-affairs regarding digital privacy concerns, MagTek recognized the need to extend transaction security expertise to consumers and businesses. As a result, Qwantum Private Messaging was developed as a “Privacy as a Service” platform and formally launched to the consumer market in June 2021.

    Qwantum Private Messaging is organized as a club, so that it can grow and flourish by attracting like‑minded professionals that see value in privacy, do not intend to use the service for unscrupulous activities, have business needs to establish authenticity and integrity of documents and objects, and desire to trust with confidence those with whom they share sensitive information. The Club’s mission is to build a network of trust based on three timeless principles: Privacy, Integrity, and Authenticity.

    There are many “private messaging” services in the marketplace (e.g., WhatsApp, Signal). Despite claims of “security”, many rely on key generation and key storage within general-purpose devices (phones, PCs) that contain hardware and software backdoors and centralized data storage—attack points for exploitation. Qwantum recognizes that true digital security cannot rely exclusively on software and general-purpose devices.

    For proper security, a physical token is required that exists outside the digital domain, is guaranteed unique, cannot be replicated, and has dynamic properties that create unique data with each use. That physical token is the Qwantum Card. Separating the digital and physical domains, the Qwantum Card provides a basis for truly secure key generation and user authentication outside non‑secure general‑purpose computers. This is what makes Qwantum Private Messaging superior.

    The cornerstone of Qwantum Private Messaging security begins with the physical Qwantum Card.

    Each Qwantum Card provides a one-of-a-kind unique physical token that cannot be replicated or counterfeited. Each card is guaranteed unique based upon the quantum characteristics of the magnetic fields produced by random distribution of ferrous particles that comprise the Qwantum stripe. Just as each snowflake in nature is unique, so too is the quantum magnetic field associated with each Qwantum Card. This unique physical token literally is your “hardware key” to secure private communications. The unique physical properties of the Qwantum card are recognized in science and often referred to as a “PUF” (Physical Unclonable Function).

    In the world of traditional Quantum Physics, a PUF is defined as a “physical entity embodied in a unique physical structure, that is easy to evaluate but hard to predict or clone”.

    The Qwantum Card utilizes a magnetic field and its underlying ferrous particles as its “unique physical structure”. This structure is specifically defined and categorized as a “Magnetic PUF”.

    A Magnetic PUF results in a unique and dynamic magnetic field that changes with each use.

    The application of a Magnetic PUF as a trusted dynamic authentication token is formally recognized by the American National Standards Institute (ANSI) and is documented in the ANSI X9.122 security standard.

    The Qwantum Card is unique and dynamic.

    Based on traditional quantum physics, the Qwantum Card’s magnetic field is constantly in motion and changes dynamically each time it is used. These characteristics make it both a perfect authentication token and a random data generator that facilitates the generation of unique encryption keys.

    The Qwantum Card is anonymous.

    The data encoded on each Qwantum card is anonymous and contains only a generic serial number that provides no information about the card owner. Each Qwantum Club Member is assigned their own unique Qwantum Club card.

    The Qwantum Card is your physical “KEY” to security.

    Think of it as a one-of-a-kind “hardware key” that uses its PUF features to authenticate the user. It replaces the need for Usernames and Passwords that can be stolen and compromised. Simply glide the Qwantum card through the card reader and you are instantly authenticated. The magnetic PUF data is then used to facilitate the generation of a unique encryption key.

    Each use of the Qwantum Card creates both a dynamic authentication value for user authentication and random quantum data that is used to help generate a unique encryption key to protect the data.

    Together, the use of these physically generated security values forms the foundation for a secure private message that can be both authenticated and protected by AES-256 encryption.

    Think of the resulting encrypted message as a “self-encapsulated” private message token that remains secure no matter how or where it is stored. It is analogous to a virtualized “hardened bank vault” that cannot be opened or viewed by threat-actors. Even IF intercepted or stolen by threat-actors, the contents of the private message cannot be accessed or compromised.

    Using the dynamically and randomly generated data from each glide of the Qwantum Card, a unique AES-256 key is automatically created for each Qwantum Private Message.

    AES-256 encryption is a NIST-recognized symmetric-key algorithm for providing the highest-level non-military grade encryption available to the civilian sector. It is approved for use with “top secret” documents within the Federal Government.

    AES-256 uses 256-bit symmetric keys. This key space creates a range of numbers so large that no existing computer systems have the computational power to attempt a brute force attack. Unlike asymmetric keys used in PKI, large symmetric keys will remain resistant to future attacks from next-generation quantum-capable computers. (AES-256 is resistant to potential quantum computer attacks based on Shor’s or Grover’s algorithms.)

    This means that AES-256 encryption provides optimum data protection today and into the future.

    It means that Qwantum Private Messages and documents remain safe and secure no matter where they are stored or transmitted.

    With Qwantum Private Messaging the user never has to be concerned with anything related to cryptographic key generation, key storage, or key usage for encryption or decryption of private message data. All key management activities are automatically managed by the Qwantum Private Messaging service.

    Because of the dynamic properties of the Qwantum Card, a unique encryption key is generated for each private message. This is referred to as “UKPT” (Unique Key Per Transaction). The use of a unique key per message means that a threat-actor cannot simply compromise a single key and use it to attack “all” messages. Each message is uniquely encrypted and protected.

    Qwantum Private Messaging NEVER stores a Qwantum Club Member’s message data or encryption keys on our servers. EVER. Qwantum’s servers only provide a real-time “on-the-fly” service that authenticates each private message, encrypts/decrypts the message as required, and passes the message to an authenticated recipient. As soon as the message services are completed, ALL data and keys associated with that message are immediately and permanently erased. NO copies, records, or logs of the message or key are retained on Qwantum’s servers. PERIOD.

    The resultant encrypted files are only distributed to the Qwantum Club Member that created the message and to their designated recipients. Because they are encrypted under AES-256, they are safe and secure no matter where they are stored or transmitted.

    With Qwantum Private Messaging, ALL critical assets are distributed and never stored in a central location.

    • User Authentication is distributed, because each Qwantum Club Member has their own unique Qwantum Card. Since the card is a “physical” token, it cannot be “stolen” from the digital domain.

    • Key Generation is distributed because each encryption key is locally generated by Qwantum Club Members when they glide their Qwantum Card. There is no single location for threat‑actors to exploit.

    • Encrypted Messages and File Attachments are distributed and only exist within the possession of Qwantum Club Members that created them and the designated parties that received them.

    By using a distributed (rather than centralized) security architecture, Qwantum Private Messaging provides an enhanced security platform compared to other solutions. There is no central repository of encryption keys or message data. There is no single or centralized “attack point” for threat-actors to exploit. In short, there is nothing to steal.

    Qwantum Club Members are provided with “receipt notifications” that confirm secure delivery of private messages to intended parties and validate when the message was viewed. Optionally, for each private message, the sender may require geo-location of recipients for higher assurance that intended recipients received the message. For even higher security, the sender can mandate one-time Phone Codes that are texted or emailed to intended recipients. Together, these features allow the Qwantum Club Member to set the desired level of security and maintain a complete audit trail of who received messages and when. Because of the authentication technologies used, this audit system can be used to establish “non-repudiation” of message origination and receipt.

    If a Qwantum Club Member desires to send and receive Qwantum Private Messages from a mobile device without their Qwantum Card or reader, they can create a “Member Token”. The Member Token is stored on their mobile device and used as a replacement for their Qwantum Card.

    For security, the Member Token’s expiration is established by the member and can be set to “one-time use” or a pre-determined time period. For additional security, a one-time Phone Code is automatically dispatched to the member’s mobile number every time a Member Token is submitted for use.

    To send secure private messages to a non-club member, Qwantum Club Members use “Guest Tokens”. Workflow overview:

    • Create and send the secure private message as normal.

    • Generate a Guest Token and send it to the non-club recipient.

    • Optionally require a one-time Phone Code when the Guest Token is submitted.

    • Recipient inserts the Guest Token (and Phone Code if required) to decrypt the message.

    Guest Tokens can be restricted to decrypt a specific Private Message by Transaction ID, or configured to allow a non-club member to create a Private Message back to the Qwantum Club Member. Guest Tokens support advanced Message Options to pre-fill and lock Subject, To, CC, BCC, and to define Custom Field Lists (comma-separated; add * to require a field — e.g., First*,Last*,Phone*).

    These features enable unlimited customized private message templates.

    Qwantum Club Members can view reports of all active tokens they’ve issued, revoke individual tokens or all tokens, and manage them easily and securely.

    Qwantum Private Messaging supports both browser-based interfaces and local client apps.

    Browser-based interfaces support all leading browsers: Chrome, Safari, Firefox, Edge, Brave, Opera, and MagneFlex by MagTek.

    Access (example): https://privatemessaging.qwantummedia.com/ — plug a Qwantum card reader into a USB port (USB KBE or Keyboard Emulation) and you’re ready.

    Native apps (for users who prefer them) are available for Windows and iOS platforms and support MagTek USB HID/USB KBE, Apple Lightning, USB-C and BLE devices.

    • Windows app on Microsoft Store

    • iOS – Coming Soon

    Qwantum Club Members can create private messages and custom-form templates for secure sharing or local storage. Messages can be simple text or complex data (health forms, travel documents, legal documents). File attachments (Word, Excel, PowerPoint, PDF) are supported. When ready, all contents are securely encrypted via AES-256 unique-key encryption and encapsulated into a “virtual hardened bank vault”.

    During transit and storage, the secure private message remains protected and can only be opened by valid recipients who either possess a valid Qwantum Card or have a valid Guest Token. Messages cannot be viewed or altered in transit.

    In 1995 we entered the “dawn” of the Digital Age. In 2021 it is time to enter the “protect your privacy” era.

    We have learned that our “trust” in BigTech providers and Governments has been misplaced. Real-world threats from criminal organizations and threat-actors continue to expand and pose significant threats to our freedoms and security.

    For those who desire digital privacy, the burden is on each citizen and business to find a solution. As with most things, “security isn’t free”. There is a price that must be paid. It’s a question of who you can trust.

    Qwantum Private Messaging is committed to providing citizens and businesses around the world with trusted and reliable data security services that protect their data and communications via a convenient, easy-to-use platform that provides true value and peace of mind.

    You are formally invited to join the Qwantum Club!

    Within this community you will find a trusted platform for secure private messaging and file privatization.

    • A secure domain where your digital privacy rights are respected and protected.

    • A place to express yourself and share thoughts only with those you choose.

    You have a right to digital privacy. Defend it.

    To learn more, please visit Qwantum Private Messaging:

    https://privatemessaging.qwantummedia.com/

    Our Vision

    “The right of the people to be secure in their persons, houses, papers, and effects…”

    QwantumMediaSupport@magtek.com
    www.MagTek.com

    Digital Privacy – A Quick History Lesson

    Is There a Path Forward?

    Why Qwantum?

    Introducing Qwantum Private Messaging

    Qwantum Card

    Encryption

    Key Management

    Data Management

    Distributed Assets

    Audit Trail

    Member Tokens

    Guest Tokens

    Token Management and Reports

    Browser and App Interface Options

    Private Messages and Files

    Join the Qwantum Club!

    Qwantum Tokens & QMFA Wallet

    A tokenization and authentication framework designed to replace outdated security models with real-time, user-initiated, and cryptographically secure authentication of Qwantum Tokens

    Qwantum Private Messaging

    An app that delivers "Privacy as a Service". It lets individuals and businesses use public communication channels or storage systems to send or save sensitive material simply and quickly by privatizing the material.

    Qwantum Secure Cards

    Physical credentials from MagTek's Qwantum Media division that serve as uncloneable authentication tokens for high-security applications.

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-800-788-6835 (US) | +1-562-546-6616 (International)

    • 🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Official Site:

    • 💬 Developer Forum:

    Documentation Feedback:

    Help us improve this documentation!

    ASIC
    https://www.magtek.com
    https://forum.magtek.com

    Reader Management Services

    The Reader Management System (RMS) is MagTek's cloud service for remotely managing deployed card readers. From a single console — or through the RMS API — you can monitor device status and health, push configuration and key updates, and keep firmware current across an entire fleet, without handling each device in person. RMS is how you operate MagTek readers in the field at scale, after they're deployed.

    Applies to: RMS-supported MagTek readers.

    What you can do with RMS

    • Monitor your fleet — device status, health, and inventory across all your deployed readers.

    • Manage configuration — push settings and configuration to devices remotely.

    • Rotate keys and update firmware — keep devices current and compliant without physical access.

    • Automate with the API — integrate RMS into your own systems through its REST API.

    Videos on RMS setup and installation along with apps available for the system.

    Reference Section

    Information Available

    RMS Gen II Installation & Operation Manual

    Manual for the Reader Configuration Gen II Program, an application designed to leverage the MagTek RS3 web services, for secure key injection and device configuration of DynaFlex family devices.

    Linux Sample Code Manual

    Instructions to use the RMS Sample Code. Combining MagTek Linux SDK and web API calls to the Reader Management System (RMS) web service

    Original Support Page

    Everything else you need to support your Reader Management System

    RMS Support

    Need More Help

    Need Help?

    For additional support, please contact MagTek Support:

    Technical Support:

    • 📧 Email: support@magtek.com

    • 📞 Phone: 1-562-546-6800 (US)

    • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST

    Online Resources:

    • 🌐 Support Portal: developer.magtek.com

    Documentation Feedback:

    Help us improve this documentation!

    feedback@magtek.com
    RMS Videos

    Qwantum ASIC

    Qwantum ASIC is MagTek’s next‑generation Application Specific Integrated Circuit designed to serve as the secure front‑end decoder for magnetic stripe card reader systems. Building on the proven Triple‑Track Delta ASIC, the Qwantum ASIC adds support for the Serial Peripheral Interface (SPI) and significantly lower power demand, making it ideal for advanced, battery‑powered devices that require both card data decoding and Qwantum security features. The Qwantum ASIC is available as part of an OEM Integration Evaluation Kit, which includes a USB‑C port for power, a host microcontroller connection, two MSR connections, and a communication mode select pin.

    The official MagTek Qwantum ASIC support page is a central hub containing the resources you’ll need. There you can find the Technical Reference Manual for the OEM Integration Evaluation Kit, which describes how to integrate Qwantum Authentication enhanced data encryption technology into your magnetic stripe card reader systems, as well as a White Paper titled “Qwantum Media Solutions Overview and Industry” that provides an overview of Qwantum Media, a division of MagTek that supplies cards or tokens in various shapes and materials that cannot be cloned or altered and provide Qwantum Authentication Codes.

    Qwantum ASIC

    Support >
    Submit feedback