QR Code Plates and Terminals
A QR code plate is the physical carrier (table stand, floor stand, sticker) of an aggregate QR collection link. The model is "the platform manufactures plates centrally, merchants claim and bind them": the admin panel batch-generates blank plates and assigns them; the merchant panel claims them and binds them to its own app and store.
Plate Lifecycle
Admin Panel: QR Plate Management
Menu path: Payment Management → QR Plate Management (platform-wide view)
Batch create: toolbar Batch Create — choose the program type (H5 / mini program), amount type, batch number, and quantity (optionally name, initial status, and fixed amount) to generate a batch of blank plates at once.
Query conditions: merchant number, store number, batch number, code, name, program type (H5 / mini program), amount type (random amount / fixed amount), status.
List columns: code (click to view the enlarged QR code with its scan URL), name, program type, batch number, amount, status, allocation flag, merchant, creation time.
Operations:
| Operation | Description |
|---|---|
| Batch create | Generate a batch of blank plates |
| Batch operations | Batch bind / unbind merchant — the bind dialog also sets the app and store (deciding which app's gateway payment configuration the collection goes through); unbinding reclaims the plates for reassignment |
| Edit | Change the name, amount type, fixed amount, allocation flag, and remark (app / store ownership is read-only) |
| Enable / disable | Control whether the plate can collect payments |
| Delete | Delete a plate (enabled plates cannot be deleted — disable first) |
Merchant Panel: Claim and Bind
Menu path: Merchant Center → Basic Management → QR Plate Management
The merchant panel cannot create plates (manufacturing is a platform action); its core action is claiming:
- Bind plate: enter the blank plate code issued by the platform to claim the plate for the merchant;
- After claiming, use Edit to bind the app and store (deciding which app's gateway payment configuration the collection goes through) and set the amount type (random amount lets the user enter the amount; fixed amount locks the collection amount);
- Enable / disable controls the deployment state; View QR code shows the enlarged QR code and lets you copy the scan link to hand to the print vendor.
What happens after scanning a plate
User scans the plate → opens the aggregate QR landing page (open environment auto-detected) → routes to a channel merchant per the gateway payment configuration of the plate's bound app. So collecting via a plate requires: the plate is bound to an app + that app's gateway payment configuration is ready; see Gateway Payment.
System Terminals
Menu path: merchant panel → Basic Management → System Terminals (admin panel: Merchant Workbench → Basic Management → System Terminals)
A system terminal is the merchant's logical terminal number, used in channel scenarios that require a terminal number in the request (e.g. consumer-scan devices, cashier plugins). Core concepts:
- System terminal: managed logically within this system, with a custom code;
- Channel terminal: the terminal number registered on the channel side (WeChat, Alipay, etc.);
- The binding between them is maintained in the Bind Management drawer of a system terminal (one system terminal can bind multiple channel terminals).
Operations: add, edit, bind management (bind / unbind system terminal ↔ channel terminal), delete; query conditions are terminal code, terminal name, store number, and enabled status.
Related Sections
- Gateway Payment: the routing configuration behind the plates
- Merchant Panel Getting Started