All pages
Powered by GitBook
1 of 13

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Installation

Open your browser and navigate to the URL below.

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

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

  • Double-click the setup.exe

Click the Install button.

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

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

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.

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.

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

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.

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

  • 10

    May 2021

    Initial Release

    Table 0.1 - Revisions

    Purpose of the document

    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!

    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.

    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.

    RMS Videos

    feedback@magtek.com
    RMS Videos

    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.

    Key Configuration

    Update Key

    EMV Configuration

    Update Tags and CAPKs

    Update Firmware

    Load Images

    RMS MMS Sample Code

    Configuration Update

    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

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

    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.

    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.

    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

    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.

    EMV Tags/CAPKs Update

    Firmware app

    For details on the RMS API see: https://rmsv2.developer.magtek.com

    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.

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

    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

    /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

    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:

    Onboarding

    Benefits

    Requirements

    Building RMS Sample Code

    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_mms_config_update
    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:
    Selected Configuration 1 Updating Configuration... Configuration: Mask4Zero4 CommandsToDevice (1)
    Name: LeadingUnmaskedCharacters Command:
    SENDCOMMAND,AA0081040110D111841BD11181072B06010401F609850101890BE109E2 07E205E103C30104
    CommandsToDevice (2)
    Name: PANMaskedCharacter
    .
    .
    .
    Configuration Mask4Zero4 has been updated.
    $ sudo ./rms_mms_firmware_update
    $ cd Sample
    $ make
    {
    “rms_server”: “https://svc1.magensa.net”, 
    “api_key”: “MTPublic...”,
    “profile_name”: “MagTek_Production”
    }

    RMS SCRA Sample Code

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

    $ sudo ./rms_scra_config_update
    • 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.

    EMV Tags/CAPKs Update

    Firmware 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

    Linux Sample Code Manual

    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.

    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

    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 .

    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.

    100

    May 11, 2026

    Initial release.

    Table – Revisions

    SOFTWARE LICENSE AGREEMENT

    TERMS, CONDITIONS, AND RESTRICTIONS

    SUPPORT@MAGTEK.COM