> 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/qwantifi-tm/qwantifi-cloud-overview.md).
# QwantiFi Cloud Overview
QwantiFi is MagTek's MQTT-driven cloud platform for Dyna family hardware, hosted on Magensa to provide complete remote device control across diverse operating systems, browsers, and networks. Connect a DynaFlex II PED WLAN to a merchant's Wi-Fi network, bring it online through QwantiFi, and your point-of-sale integrated application can accept transactions through the cloud — cloud-managed and platform-neutral, with no device-side drivers or OS-specific integration. This is the place to start: it explains what QwantiFi is, how the pieces fit together, and the concrete steps to get your first device online and taking transactions.
{% hint style="info" %}
**A Note on "QwantiFi" vs "MQTT":** QwantiFi is built on MQTT, a lightweight, standard messaging protocol for secure device-to-cloud communication. Throughout this documentation we call it "QwantiFi" rather than "MQTT," so you have one consistent name for the service and don't need any prior MQTT knowledge to get started. The underlying protocol is named only where you actually need it, such as in the API reference.
{% endhint %}
## How QwantiFi Works
#### At a high level, QwantiFi has three parts:
* **Your reader** connects to QwantiFi Cloud over a local Wi-Fi network, where it receives commands and sends back responses without a physical, wired connection to the integrated application. (see [**QwantiFi Device Configuration Commands**](https://developer.magtek.com/api-and-command-reference/~/revisions/AxjZXnxcrmQygHeCLIf3/dynafamily-programmers-manual/mqtt-qwantifi-configuration-device-settings)).
* **Provisioning** equips a reader with its QwantiFi connection settings and credentials. You do this from the [**QwantiFi Cloud Device Management browser tool**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-cloud-device-management-tool-guide) or through the [**RMS Provisioning API**](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/rms-mqtt-configuration-api-reference) to automate a whole fleet.**.**
* **Your Application** connects to QwantiFi Cloud with credentials generated by your Merchant or Reseller account and uses them to run transactions. See [**Integration Guide**](https://developer.magtek.com/guides/guides/qwantifi/pos-integration-guide) and [**QwantiFi Credential Model**](https://developer.magtek.com/guides/guides/qwantifi/qwantifi-credential-model)**.**
Everything flows from your Magensa Reseller Account — start with **Before You Begin**, below.
### Before You Begin
Everything in QwantiFi — devices, merchant accounts, and provisioning — flows from a **Magensa Reseller Account** at the top of your hierarchy.
* **New to Magensa:** Your first step is account setup. Before you can onboard a device or access QwantiFi, you need an active Magensa Reseller or Merchant Account.
{% hint style="info" %}
Contact a Magensa Sales Associate to set up your reseller or merchant account — visit [**magensa.net**](https://www.magensa.net) or ask your MagTek Sales Associate. Once your account is active, return here and continue with the prerequisites below.
{% endhint %}
* **Existing Magensa Customer:** Your reseller hierarchy and any previously registered devices already appear in the onboarding tool. Confirm you have reseller-level access and that the target merchant account exists, then continue with the prerequisites below.
{% hint style="info" %}
**Credentials are issued for you.** There is no self-service onboarding endpoint — initial device provisioning and integrated application credentials are set up server-to-server by MagTek or your reseller's portal. Once you hold your credentials, everything after that (token refresh, device lookups) is self-service. If you haven't been onboarded, or need credentials re-issued, contact your MagTek Sales Associate.
{% endhint %}
## Prerequisites
Confirm you have all of the following before you start.
| | |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Magensa Reseller Accoun**t | Active account with reseller-level access. New customers must contact Magensa Sales to set this up. |
| [**DynaFlex II PED**](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaflex-ii-ped)[ ](https://developer.magtek.com/guides/guides/qwantifi/pos-integration-guide) - **WLAN** | The physical reader to be deployed and powered on. |
| **Merchant Wi-Fi credentials** | The SSID and password for the network at the location where the reader will operate. |
| **Merchant account in QwantiFi** | The target merchant under your reseller hierarchy. Create it in advance if it does not already exist. |
## Get Started
#### Register the Reader from the Dashboard
There are two ways to start registering a reader — from the QwantiFi Cloud Dashboard, or directly in the QwantiFi Cloud Device Management tool. Both open the same tool, where you'll set the reader's Wi-Fi and location. To start from the dashboard:
1. Sign in to the Magensa Reseller Portal and select **Devices** in the left menu to open the QwantiFi Cloud Dashboard.
2. Scroll to the bottom of the device list and click **Register Device**.
3. In the *Select a merchant* dialog, choose the merchant to assign the reader to, then click **Proceed** — the QwantiFi Cloud Device Management tool opens in a new tab, ready for the next step.
{% hint style="info" %}
Prefer to skip the dashboard? Open the QwantiFi Cloud Device Management tool directly and register the reader there instead — the remaining steps are identical.
* [**QwantiFi Cloud Dashboard (Guide)**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-tools-manuals/qwantifi-cloud-dashboard-guide)
* [**QwantiFi Cloud Device Management (Tool Guide)**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-tools-manuals/qwantifi-cloud-device-management-tool-guide)
{% endhint %}
### Connect the Reader to Wi-Fi
Wi-Fi is configured entirely through the onboarding tool — there's no need to set up the network from the device screen. Launch the tool and follow its onboarding screens to enter the SSID and password; it pushes the settings to the reader and confirms the connection before you continue.
{% hint style="info" %}
Have the merchant's Wi-Fi SSID and passphrase ready before you start, and configure the reader on the exact production network it will use — moving it to a different network after onboarding requires reconfiguring the SSID and password.
{% endhint %}
* [**QwantiFi Cloud Device Management (Tool Guide)**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-cloud-device-management-tool-guide)
### Onboard the Reader to QwantiFi
Use the same onboarding tool to register the reader and assign it to the correct merchant account under your reseller hierarchy. This is the browser-based path for single-device or manual deployments.
{% hint style="info" %}
Existing Magensa customers: your hierarchy and previously registered devices already appear in the tool. Select the correct merchant before registering to avoid mis-assignment.
{% endhint %}
* [**QwantiFi Cloud Device Management (Tool Guide)**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-cloud-device-management-tool-guide)
### Provision Through the RMS API — Optional
For resellers managing multiple readers or building automated deployment workflows, the RMS API registers and configures devices programmatically — no browser required. Skip this for a single manual deployment and come back when you're ready to automate at scale.
* [**RMS Provisioning API**](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/rms-mqtt-configuration-api-reference)
### Integrate Your Application
With the reader onboarded, your application connects to QwantiFi Cloud to perform transactions. The same cloud API works on Windows, Linux, Android, or any other environment — no device-side drivers or OS-specific integration required.
* **Authentication:** [**QwantiFi Credential Model**](https://developer.magtek.com/guides/guides/qwantifi/qwantifi-credential-model)
* **Transactions:** [**Integration Guide**](https://developer.magtek.com/guides/guides/qwantifi/pos-integration-guide)
### Resources at a Glance
Everything used in this integration, in one place.
| | |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| [**QwantiFi Credential Model**](https://developer.magtek.com/guides/guides/qwantifi/qwantifi-credential-model) | Understand how your application authenticates and keeps its access alive. |
| [**Integration Guide** ](https://developer.magtek.com/guides/guides/qwantifi/pos-integration-guide) | Connect your application and perform card-present transactions through the cloud. |
| [**API Reference** ](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/pos-mqtt-api-reference) | Look up the exact endpoints your application calls at runtime. |
| [**QwantiFi Cloud Device Management (Tool Guide)**](https://developer.magtek.com/sdks-and-tools/tools-and-utilities/qwantifi-cloud-device-management-tool-guide) | Register readers and assign them to merchant accounts from the browser. |
| [**QwantiFi Device Settings**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/qwantifi-configuration-device-settings) | Reference the on-device connection settings applied during provisioning. |
| [**RMS Provisioning API**](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/rms-mqtt-configuration-api-reference) | Automate reader registration and configuration at scale. |
## Next Steps
Once your first reader is connected and your applicattion integration works end-to-end:
* **Deploy additional readers** — repeat the connect and onboard steps for each unit. For large fleets, use the [**RMS Provisioning API**](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/rms-mqtt-configuration-api-reference) to automate bulk registration.
* **Monitor device health** — track connectivity and transaction activity across all your registered readers from the QwantiFi Cloud Dashboard.
## Need More Help
{% hint style="info" %}
**Need Help?**
For additional support, please contact MagTek Support:
**Technical Support:**
* 📧 **Email:** [support@magtek.com](mailto:support@magtek.com?subject=Support%20Request)
* 📞 **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](mailto:feedback@magtek.com?subject=Feedback)
{% 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/qwantifi-tm/qwantifi-cloud-overview.md?ask=&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.
