Payment Configuration
Self-service integration configuration for merchants: apps, keys, channel merchants, and open apps. All core, high-frequency configuration can be done fully on the phone, with the same interactions as the Admin App.
App Management
- List: app name, default app flag, AppId, status; a warning appears when no default app is set;
- Edit: name, status, default app (disabling the default app requires an extra confirmation);
- Configuration grid (after entering an app): four self-service configuration items — channel routing, gateway payment configuration, cashier configuration, EasyPay protocol — plus async notification configuration (under construction, see below) and edit / set default / delete (the default app cannot be deleted).
The four configuration items work exactly as in the Admin App (three-mode gateway configuration, environment-bucketed cashier configuration, channel / scene routing, EasyPay protocol); see Apps & Integration Configuration (Admin App) — it is the same configuration page, whoever signs in can edit it.
Async notification configuration is under construction
The app-level event subscription UI is under construction; for now, do it on the Web portal. For the semantics see App Configuration (Web).
Key Configuration
The trio for integrating with the open API: the platform public key (read-only, copyable), your merchant public key (an RSA key pair can be generated), and the communication key (an AES key can be generated). The private key is shown only once, at generation time — save it immediately. Same as the Admin App; see Key Configuration.
Channel Merchants
Self-service maintenance of the channel receiving accounts under your name:
- List: product icon + name, enabled / disabled, channel merchant number;
- Detail (two grids; the merchant side has no delete — contact platform operations to remove one):
- Transaction configuration: allocation receivers, transfer configuration, authorization tokens (Alipay ISV) — same operations as the Admin App, including scan-code authorization;
- Basic management: basic info (read-only), rename, key configuration (PC only), enable / disable;
- Five products are supported on mobile: WeChat direct / ISV, Alipay direct / ISV, and Douyin; other products show "not supported on mobile" — use the Web portal instead.
Self-service boundary
Merchants can rename and enable/disable all their channel merchants themselves; creating a new channel merchant is done by platform operations (it involves channel onboarding) — once operations has opened it for you, you maintain it on your phone.
WeChat / Douyin Open Apps
Register the official account / mini-program / mobile app you use to collect payments (JSAPI payment and mini-program login both depend on it):
- Register: app name, type (WeChat: official account / mini-program / mobile app; Douyin: mini-program / mobile app / website app), AppId, AppSecret (leave blank when editing = keep unchanged);
- The AppId is unique within a merchant (automatic duplicate check); deletion requires strong confirmation by typing the AppId, and an app referenced by a pay capability cannot be deleted;
- Changing the app type clears incompatible capability bindings (strong confirmation).
Pay capability binding for the WeChat ISV mode (platform app ↔ pay capability) is maintained on the Admin App.
Related Links
- Channel Merchants (Web merchant panel) — full walkthrough of self-service channel maintenance
- Apps & Integration Configuration (Admin App) — complete reference for the same configuration pages
- Merchant App Feature Map