Apps and Integration Config
An app (AppId) is the identity unit a merchant uses to integrate with the open API. On the phone you can complete app management, key config, gateway payment config, cashier config, channel routing, and EasyPay — the config entries of the "Business Config" and "Payment Config" groups in the merchant detail grid all belong here.
App Management
- List: app name, default app marker, AppId, status; a warning banner shows when no default app is set;
- Edit: name, status, whether default (disabling a default app asks for a second confirmation);
- App management grid (after entering an app): channel routing, gateway payment config, cashier config, async notify config, EasyPay protocol config, plus edit, set / unset default, delete (the default app cannot be deleted; delete is a strong confirmation that requires typing the app name).
Async notify config is under construction
The mobile UI for app-level event subscriptions (unified notification config) is under construction and currently shows a placeholder page. Before it ships, operate on the Web admin panel; see App Configuration (Web).
Key Config
The trio needed to integrate with the open API:
| Key | Purpose | Action |
|---|---|---|
| Platform public key | Verifies messages sent by the platform | Read-only, copyable |
| Merchant public key | For the platform to verify merchant requests | One-click RSA key pair generation |
| Communication key | Encrypts / decrypts API messages | One-click AES key generation |
The generated private key is shown only once in a dialog — copy and store it immediately; saving asks for a second confirmation.
Gateway Payment Config
Distribution of pay methods across the three collection scenarios — cashier / aggregate QR / QR code plate. Three modes, configured cell by cell over 4 providers (WeChat / Alipay / UnionPay / Douyin) × 2 forms (H5 / mini-program):
- AUTO: read-only display of the system default pay methods, zero config;
- METHOD (by pay method): each cell picks one pay method (e.g. "WeChat JSAPI");
- DIRECT (specify directly): each cell picks a "channel merchant + pay capability" pair (they must go together; at least one row) — for splitting one merchant's traffic across multiple channels.
Cashier Config
The list of pay methods customers see on the unified cashier: configured per cashier type — H5 / Web / mini-program — with H5 and mini-program further split by open environment (browser / WeChat / Alipay / UnionPay / Douyin). Each row: name, sort, resolution mode (by pay method, or by channel merchant + capability), recommended or not. The customer-side "Recommended" badge and pinning logic come from here.
Channel Routing
Assigns the default channel merchant per provider, in two modes:
- Basic: pick one channel merchant each for WeChat / Alipay / UnionPay / Douyin;
- Scene: a "channel merchant + pay capability" per "provider + pay method" row — finer-grained splitting control.
EasyPay Protocol
Integration config compatible with the EasyPay (Epay) protocol: a master enable switch; access info (merchant number, V1 / V2 endpoint URLs) read-only and copyable; V1 uses an MD5 key; V2 optionally a platform-hosted key (the platform public key shown read-only) or a self-managed RSA public key.
WeChat Domain Verification File (Merchant Level)
Hosting of WeChat domain-ownership verification files: on upload, the file name must match the MP_verify_XXX.txt format (the official WeChat format), and the content is the full file text pasted in. The list supports view / edit remark / delete.
Related Links
- App Configuration (Web): the Web panel in detail
- Gateway Payment: the business flow of the three collection scenarios
- Admin App Feature Map