> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/services/~/revisions/hh8XuzI4i4H7MDrPcZQI/reader-management-system/documentation/ios-installation-and-operation-manual/overview.md).

# Overview

The MagTek Reader Management System (RMS) is a comprehensive application with specialized source code designed to streamline the configuration and update process for MagTek readers in enterprise environments. Its primary functions include firmware management, key injection, device configuration, and the loading and management of terminal, application settings, and Certificate Authority Public Keys (CAPKs) required for EMV contactless transactions.

## Purpose <a href="#id-1.1_purpose" id="id-1.1_purpose"></a>

The Reader Management System (RMS) application is designed to be compatible with all DynaFlex, DynaProx, and MagneSafe products available from MagTek.

* The main purpose of this app is to streamline the ability to load firmware, device configs, keys, Tags and CAPKs into a target reader or more importantly, a large quantity of geographically separated readers.
* The target files are 100% MagTek managed (files managed at MagTek’s host) so the user is not able to load the wrong files by accident.
* The app can auto execute or manually execute the update process which can include all of the above file options in a single action. This prevents the need to load individual files which is cumbersome and not practical for scale.
* The source code can be used to integrate this functionality into 3rd party apps which makes it easier for developers to use Magensa Remote Services.

## Benefits <a href="#id-1.2_benefits" id="id-1.2_benefits"></a>

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. It supports both iOS, Android and Windows, allowing flexibility in device management. (*See each OS specific installation manual for further details*)
* 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.

## iOS System Requirements <a href="#ios_system_requirements" id="ios_system_requirements"></a>

The RMS app is compatible with iPhone, iPad, and iPod touch, iPad OS.

{% hint style="info" %}
**Note**: Not all configuration options are available for all Secure Card Reader Authenticators (SCRAs). The available configuration options depend on:

* The specific SCRA model in use.
* The configuration options provided by MagTek.
  {% endhint %}

{% hint style="danger" %}
**Important**: Some commands may require a device reset.

* Refer to the Programmer's Manual for your particular device to see which commands are affected.&#x20;
  {% endhint %}

### RMS iOS Application <a href="#rms_ios_application" id="rms_ios_application"></a>

* iOS Application V1 (PN 1000009406)
* iOS Application V2 (PN 1000009755)
* Compatible with both USB and Bluetooth Low Energy (BLE) connected readers, as well as WLAN enabled readers.
* Supports MagTek MagneSafe and DynaFlex/DynaProx readers.

{% hint style="info" %}
**Note**: As of March 4, 2025, MagTek advises all current RMS V1 users to upgrade to V2 as soon as possible. While V1 is still supported, future firmware updates, EMV tags, and CAPKs will not be implemented on RMS V1.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.magtek.com/services/~/revisions/hh8XuzI4i4H7MDrPcZQI/reader-management-system/documentation/ios-installation-and-operation-manual/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
