Skip to content

Device Management ​

Updated: 11/10/26, 10:51:10 AM

Device management is a first-level section on the operations side that manages three kinds of collection carriers in one place: QR codes, virtual devices (voice broadcast) and merchant terminals. This page covers only the ledger operations in the operations panel; channel-side terminal registration records are maintained on the Channel Merchants detail page, and the business semantics of QR codes and terminals in payment are covered in QR Codes and Terminals.

The data of all three device types comes from the same source as the merchant panel's "Device Management"; for merchant self-service operations see Payment Device Management.

Section Overview ​

FunctionMenu pathPurpose
QR Code ManagementDevice Management → QR Code ManagementPlatform-side bulk creation, merchant binding, enable/disable and QR code viewing
Virtual DevicesDevice Management → Virtual DevicesVoice broadcast APP device ledger: generation, merchant binding, activation QR code, test broadcast and test print
Merchant TerminalsDevice Management → Merchant TerminalsPlatform-wide read-only overview of merchant terminals, with each terminal's linked channel terminals

Creation and ownership

QR codes and virtual devices are both generated on the platform side. After generation they enter platform inventory and are then bound to merchants; the merchant panel has no creation entry.

QR Code Management ​

Menu path: Device Management → QR Code Management. The list is a cross-merchant global view; QR codes are produced in bulk by the platform and then bound to merchants.

Query and List ​

  • Query conditions: merchant number, store number, batch number, QR code number, QR code name, QR code type (H5 / mini program), amount type (custom amount / fixed amount), status (enabled / disabled)
  • List columns: QR code number, QR code name, QR code type, batch number, amount, status, allocation flag, merchant, creation time
  • A QR code that is not bound to a merchant shows "Unbound" in the merchant column
  • Click a QR code number to open the "QR Code" dialog, which shows the QR code and its scan URL; "Copy Link" hands the link to the print vendor for producing materials

Batch Generation ​

"Batch Generate" in the toolbar opens the generation dialog:

FieldDescription
Batch numberAuto-generated by default (a time string starting with Q) and editable, or click "Generate" to regenerate it. The batch number is the prefix of QR code numbers; an existing one raises "Batch number already exists"
Quantity1 to 999
QR code nameOptional; shared by the whole batch
QR code typeH5 / mini program, deciding the landing page type after scanning; cannot be changed after creation
Amount typeCustom amount / fixed amount; a fixed amount must be filled in when that type is chosen
StatusEnabled / disabled, enabled by default

Generated items are blank QR codes owned by platform inventory. Numbers are built as "batch number + three-digit sequence" (starting at 001) and stay consecutive within a batch.

Binding and Unbinding ​

  • Select QR codes and use "Batch Operations" → "Bind Merchant": choose a merchant, and optionally an app and a store. With the app left empty, payment goes through the merchant's default app; with the store left empty, the QR code is a merchant-wide code
  • Binding an already bound QR code overwrites the original ownership and clears the original app, store and allocation settings; the dialog shows an overwrite warning at the top
  • After "Unbind Merchant" the QR code returns to blank inventory, keeping its number, batch and amount configuration while clearing merchant, app and store. In a mixed selection, unbound QR codes are skipped; when none of the selected codes is bound, a message says there is nothing to unbind

Edit, Enable/Disable and Delete ​

  • Edit: change the QR code name, amount type, fixed amount, allocation flag and remark; merchant and QR code type are read-only
  • Allocation flag: when on, scan payments pass the allocation flag down the order pipeline. Before saving, the payment products of the current route are pre-checked; scan scenarios that do not support allocation are listed as warnings — warnings only, saving is not blocked, and the affected payments fall back to ordinary collection
  • Enable / disable: row actions, both requiring a second confirmation; a disabled QR code cannot be paid
  • Delete: only disabled QR codes can be deleted — disable an enabled one first; deletion requires a second confirmation

Export ​

"Export" in the toolbar produces an xlsx list of QR codes. Selected rows take priority, exporting only the selection; with nothing selected, the current query filters apply to a full export. The scope and row count are confirmed before export.

Virtual Devices (Voice Broadcast) ​

A virtual device is an Android terminal with the "Voice Broadcast" APP installed: it announces each successful payment by voice, and prints a receipt at the same time when a receipt printer is connected. Menu path: Device Management → Virtual Devices.

Query and List ​

  • Query conditions: device number, batch number, merchant number, store number, status (enabled / disabled)
  • List columns: device number, device name, batch number, owner, activation, running status, enabled, last online
  • Owner: a bound device shows the merchant name and merchant number; an unbound one shows "Platform inventory"
  • Activation: "Activated" or "Not activated"; a device that is not activated cannot run test broadcast or test print
  • Running status: activated devices show "Online" or "Offline", inactive ones show "-". Online status is kept alive by APP heartbeats; "Last online" is throttled on heartbeat before being written to the database, so it is not a real-time value
  • Enabled: toggled directly by the switch in the list; a disabled device cannot be activated or receive commands

Generating Virtual Devices ​

"Generate Virtual Device" in the toolbar opens the generation drawer:

  • Quantity: 1 to 5000
  • Batch number: auto-generated by default (a time string starting with B); it can be replaced with a custom batch number, or regenerated via "Regenerate"
  • Generate and stock: a second confirmation precedes submission; generation and stocking complete in one step, and the devices go straight into platform inventory, unbound
  • Device number rule: VD + date (yyMMdd) + a six-character random segment (digits 2-9 and uppercase letters, excluding I and O), e.g. VD261022K7M2Q4
  • On success the drawer closes and the list is filtered by this batch's number automatically, for immediate checking and export

Activation QR Code ​

Row "More" → "Activation QR Code":

  • The QR code content is the activation protocol string daxpay:activate:{device number}; scanning it with the virtual device APP completes the device binding. The server address is built into the APP package, so the QR code carries only the device number
  • When scanning is not possible, use "Copy Number" or "Copy Content" to enter it manually; "Download PNG" saves the QR code for printing and posting
  • A device without a bound merchant fails activation on scan — bind a merchant first
  • A disabled device fails activation — enable it first
  • Scanning again on an activated device rotates the device key and kicks the currently online device offline; this suits machine replacement and credential reset scenarios, and a warning is shown beforehand

Binding and Unbinding Merchants ​

  • Single binding: row "More" → "Bind Merchant", choose the merchant number, and optionally an app and a store. An empty app means the merchant's default app; an empty store means a merchant-wide device
  • Batch binding: select unbound devices and use "Batch Operations" → "Batch Bind Merchant" to bind them all to one merchant at once
  • Adjusting a bound device: the row entry becomes "Adjust App/Store" — the merchant is locked and only app and store can change; changing merchants requires unbinding first
  • Batch binding restriction: if the selection contains any device already bound to a merchant, the whole batch is blocked with a prompt to unbind first; adjust bound devices one at a time
  • Unbinding: single "Unbind Merchant" or batch "Batch Unbind Merchant" both clear the device credentials, so the device must be activated again; both entries require a second confirmation

Test Broadcast and Test Print ​

Row "More" → "Test Broadcast" or "Test Print", available only on activated devices:

  • Test broadcast: enter an amount (in yuan) and a payment method; "Expected Broadcast" in the dialog previews the text in real time using the same token rules as the device side; "Send Test Broadcast" delivers a real broadcast command to the device
  • Test print: enter an amount and a payment method, choose the output mode (broadcast + print / print only), the merchant order number (optional, a receipt variable) and the print layout (built-in standard receipt, 58 / 80mm paper widths); "Send Print" delivers a print command to the device

Edit, Enable/Disable and Delete ​

  • Edit: change the device name and enabled status; the device number is read-only and ownership changes go through bind / unbind
  • Delete: only devices that are neither activated nor bound can be deleted; a bound or activated device must be unbound first (unbinding clears credentials and returns the device to a deletable state); a deleted device number cannot be restored

Export ​

"Export" in the toolbar produces an xlsx list of virtual devices containing ledger information only, with no device credential fields. Selected rows take priority; with nothing selected the current query filters apply; the scope and row count are confirmed before export.

Access Parameters and Credential Version ​

  • At activation the platform delivers MQTT access parameters (MQTT access URL, access account, access password) and a credential version to the device
  • After the platform's "MQTT Access" configuration changes, activated devices do not switch automatically — they must be re-activated by scanning to pick up the new values
  • When the access account or password changes, the credential version changes with it; heartbeats from online devices receive a re-activation flag, and following the APP prompt to re-activate is enough
  • Installing an APP package built for a different server environment also makes the APP ask for re-activation, which is expected behavior

For configuration and re-activation after changing environments, see Payment Platform Configuration and Voice Broadcast (Virtual Device): Deploy & Use.

Merchant Terminals ​

A merchant terminal is a logical terminal record on the platform side (cash register, scan box, etc.); the terminal code is generated by the platform and is the anchor that channel-side terminal registration links to. Menu path: Device Management → Merchant Terminals.

Read-Only Overview ​

This page is a cross-merchant read-only overview and offers no create, edit or delete:

  • Query conditions: merchant, terminal code, terminal name, store number, enabled (enabled / disabled)
  • List columns: merchant, terminal name, terminal code, store, enabled, linked channels, creation time
  • Linked channels: shows the summary "N records · reported X · errors Y", marked red when the error count is above 0; "Unbound" when there is no link
  • Enabled: shows only the enabled or disabled tag; it is not toggled on this page

Maintenance Within a Merchant ​

Merchant terminal records are created and maintained in the merchant workbench: Merchant Management → Merchant List → Manage → Merchant Workbench → Cashier & Devices → Merchant Terminals. That page is locked to the current merchant and supports:

  • Create: fill in the terminal name, enabled status, store (optional) and remark; the terminal code is generated by the platform
  • Edit: change the terminal name, enabled status, store and remark; the terminal code is read-only
  • Delete: second confirmation; a store's default terminal cannot be deleted directly — clear the default or hand it over to another terminal first
  • List columns: terminal code, terminal name, store (the default terminal carries a "Default" tag), enabled, remark, creation time

Linked Channel Terminals ​

Row "Linked Terminals" opens a read-only drawer showing how this merchant terminal is registered on each channel side:

  • The drawer title is "Linked Channel Terminals · terminal name or terminal code"
  • List columns: channel, channel merchant number, report type, channel-side terminal number, registration status, error message, creation time
  • Report type: WeChat channel report, Alipay channel report, UnionPay channel report, standard report
  • Registration status: not reported, reported, error, deregistered, initializing
  • The drawer notes that links are established when the channel terminal is registered (registering is binding) and this view is for reference only; to adjust, go to the "Terminal Ledger" on the channel merchant detail page
  • When there is no linked channel terminal, "No bindings" is shown

Store Default Terminal ​

The store default terminal is not set on this page; the entry is in the merchant workbench: Merchant Management → Merchant List → Manage → Merchant Workbench → Basic Management → Store Management → store card → Store Workbench → Default Settings. Candidates are the store's bound and enabled merchant terminals; a store keeps only one default terminal, and cashiering without a terminal number falls back to the store's default terminal. See Merchant Management.

Relationship with Channel Terminals ​

  • A merchant terminal is a platform-side ledger record, carrying this system's terminal semantics (logical terminals such as cash registers and scan boxes)
  • A channel terminal is a terminal record registered or reported on the channel side, attached to a specific channel merchant
  • The two are linked in "Channel Merchant Detail → Terminal Ledger": one channel terminal belongs to exactly one merchant terminal; registering is binding, so the link is created by the registration action
  • The "Device Management → Merchant Terminals" overview is read-only; creating channel terminals, adjusting links and deregistering them all happen on the channel merchant detail page, see Channel Merchants

FAQ ​

A virtual device fails activation on scan: what to check first ​

Check in order: whether the device is bound to a merchant, whether it is enabled, and whether the platform's "MQTT Access" has the MQTT access URL, access account and access password all filled in. An unbound device and a disabled device both fail activation, and missing access parameters are rejected by the platform as well. Configuration: see Payment Platform Configuration.

Why does changing MQTT Access require re-activation ​

An activated device uses the access parameters delivered at activation; after the platform's "MQTT Access" configuration changes, activated devices do not switch automatically and need one more scan activation. A change to the access account or password changes the credential version, online devices receive a re-activation flag on heartbeat, and following the APP prompt is enough.

Why does the broadcast APP stop working after unbinding or rebinding ​

Unbinding clears the device credentials and kicks the device offline; it returns to the not-activated state and the old APP stops working at its next heartbeat. To move a device to another merchant, unbind first, then bind, then have the device scan to activate again.

Does deleting a merchant terminal also deregister the channel terminal ​

No. Deleting a merchant terminal only removes the platform-side terminal record and its links; no deregistration is sent to the channel. The channel-side terminal record remains and must be deregistered in the "Terminal Ledger" of the channel merchant detail page — only then does that terminal number become unusable for payments.