Instructions for Qwantum Token Redemption Demo
This demo illustrates how to connect to a MagTek device and process the data from a scanned Qwantum Token. **Specifically, this application is designed for tokens formatted as QR Codes or NFC Tags that utilize either TOTP (Time-based One-Time Password) or OTC (One-Time Code) technology.** This workflow immediately retrieves and displays the token's associated claims, owner information, and usage count in real-time.
Note: You must have a compatible MagTek device connected to your computer to run this demonstration.
1. Device Connection and Management
Before scanning any tokens, you must establish a connection to the device:
- Click the Open button (Open) to initiate the connection to the MagTek device.
- Verify the status indicator: The text next to the buttons will change from **Disconnected** to **Connected** when successful.
- To stop processing or disconnect the device, click the Close button (Close).
- The **Clear** button allows you to clear all current log data from the Transaction Log for a fresh view.
Connecting via MQTT (Dyna Readers)
Unlike a standard USB-connected Dyna reader, the MQTT version of this demo requires identifying the specific Dev path of your MQTT-configured reader. This Dev path must be appended to the end of the base URL to establish a successful connection.
- Base URL:
https://rms.magensa.net/Token/DisplayClaims/mqtt.html - Connection Method: Append
?followed by your reader's unique Dev path to the end of the base URL. - Example URL:
https://rms.magensa.net/Token/DisplayClaims/mqtt.html?MagTek/US/PA/Paoli/AndyD/DynaFlexIIGo/Andy-B59D5C5
As long as the appended Dev path is a valid path to that MQTT-configured reader, the demo app will successfully connect and read the Qwantum Tokens.
2. Scanning or Tapping the Qwantum Token
Once the device is connected, the application is ready to receive token data:
- Scan the **Qwantum Token formatted as a QR Code** or tap an **NFC Tag** on your connected MagTek device.
- The application processes the token data and uses it to query the associated claims.
- The status display will update from "WELCOME: Scan a Qwantum Token" to confirm the action.
3. Handling OTC/TOTP Verification
If the scanned Token requires additional verification:
- The application will prompt for an OTC (One-Time Code) or TOTP (Time-based One-Time Password).
- You can manually type the code generated at the time of redemption.
- Alternatively, if the Token is configured to dispatch an OTC (via SMS or Email) that is presented as a QR Code, you can scan the one-time QR Code containing the verification data.
4. Interpreting the Claims Data
After a successful scan, the main panel will populate with the token's associated data:
- Owner and Branding: The center column will display the **Owner Name**, a **Profile Image**, and any configured branding elements like a **Banner** or **Signature**.
- Token Usage: Check the **Token Uses Count** to see the current remaining uses or value associated with the token. This number updates immediately upon a successful transaction.
- Claims Data: The list on the right shows the **specific claims** linked to this token (e.g., "1 Free Coffee," "20% Off Next Purchase," "Gold Tier Access"). This is the core transactional information.
5. Monitoring the Transaction Log
The Transaction Log provides an essential audit trail and debugging tool:
- The log is initially expanded (or can be toggled using the header button).
- Every step of the transaction—from device open, scanning, data processing, and claims retrieval—is recorded with a timestamp.
- Use this log to confirm that the device is transmitting data correctly and that the claims retrieval process is functioning as expected.
6. Security Note
This demonstration executes API calls directly from the client-side (browser) to illustrate functionality within a standalone environment. This architecture is not intended for production use. In a live production environment, all API interactions should be routed through a secure backend server (server-side proxy) to protect API keys and sensitive credentials from being exposed in the browser.
7. Architectural Disclaimer
To provide a transparent view of the data flow, this demo implements direct client-to-API communication. Please be advised that this pattern exposes authentication tokens to the front end. Production implementations should utilize a Backend-for-Frontend (BFF) pattern or server-side SDKs to ensure security compliance and credential protection.
For further assistance or to discuss customizing your token configuration, please contact MagTek support.