Risk Control and Terminals
The risk-control quartet (blacklist / hits / strategy / API security) plus the terminal device ledgers. For the semantics and layers of the risk control system see the Web panel guide; this page covers what you can do on the phone.
Blacklist
The first line of pre-check interception, blacklisting by IP / province / city:
- List: filter by list value, type, status; cards show the region name (province / city auto-encoded to text), status, type, reason, and expiry (blank = permanent);
- Add / Edit: type (IP entered by hand; province / city via a cascading region selector), list value, status, expiry (clearable = permanent), blacklist reason, remark. The type and value are immutable after creation;
- Detail actions: enable / disable, edit, delete.
Risk Hits
The hit ledger of risk control rules, read-only for investigation:
- List: filter by phase (pre-check / post-check), hit type (IP / overseas IP / province / city), hit value, source scenario (API / gateway / QR plate / manual);
- Detail: hit info + the trade context (merchant, trade number, trade type, pay method, product, channel) + client info (IP, openid, buyer identifier) — start here when investigating "why was this order intercepted".
Risk Control Strategy
Global toggles and interception strategy:
- Master switch: turning it off requires typing a confirmation keyword — once off, all interception rules stop working;
- Common settings: the IPv6 matching toggle (a precision-impact notice shows when enabled);
- List interception: the blacklist feature toggle;
- Region restriction: overseas IP interception and the province / city region blacklist toggles;
- Interception strategy: the pre-check (before payment) interception toggle.
API Security
Transport-layer protection of the open API (signature verification is always on and cannot be disabled):
- Replay protection: the nonce validation toggle and the request timeout validation toggle;
- Parameters: request timeout seconds, nonce validity (seconds).
Terminal Devices
The terminal ledger, two tabs:
- System Terminals: terminals registered by the platform (cloud speakers, cashier plugins, etc.), filterable by terminal number, name, and enable state; details include the owning store and remark, plus the bound channel terminals (one system terminal can carry several channel-side terminal numbers);
- Channel Terminals: terminals registered on the channel side (WeChat / Alipay, etc.), filterable by name, channel, and registration state (initialized / to submit / submitted / registered / error); details include the channel merchant number, product, and error message.
Entering from "System Terminals" in a merchant detail grid limits the list to that merchant automatically. The terminal ledger is view-only; registration and binding are done on the Web.
Device domain boundary
Terminal management today is a "session-level ledger": it records only device identifiers and ownership, with no online status or remote commands — IoT device services are a separate future capability.
Related Links
- System and Security (Web): the risk control system in detail
- Trade Management: cross-check intercepted trades in risk hits
- Admin App Feature Map