App Payment Config
The app workbench holds three easily confused configurations: channel routing (the underlying routing strategy), gateway payment config (how deep the gateway link goes into routing), and cashier config (what the cashier page displays). This page walks through each one. Menu path: Merchant Center → Payment Config → App Management → app card → App Workbench.
All three are app-level — a different appId means a separate set of configurations; for merchant-level credentials see API Credentials.
Order of configuration
Recommended first-time setup: configure channel routing first, keep gateway payment config on "Follow channel routing", and adjust the cashier display as needed. Once configured, use Developer Debugging to fire a test payment.
Channel Routing
The base configuration that decides "which channel merchant a payment goes through". Menu path: App Workbench → Channel Routing.
The two strategy modes are mutually exclusive — only one takes effect; the toolbar offers "Enable this mode" to switch (with confirmation; the currently active mode carries an "Active" badge):
| Mode | Configuration granularity | Suited for |
|---|---|---|
| Basic mode (by provider default) | One default channel merchant per pay provider (aggregate pay / WeChat / Alipay / UnionPay / Douyin / Visa / Mastercard) | Single channel or simple primary/backup |
| Scene mode (by pay method) | A "channel merchant + capability" per pay method (wechat_jsapi, alipay_qr, ...) | Fine-grained splitting when different methods go through different channels |
- In basic mode, the dropdown candidates come from the configured channel merchants under that provider; no candidates means the corresponding channel has not been opened yet (see Channel Merchants);
- In scene mode's two-level cascade (channel merchant → capability), capability candidates refresh as the merchant changes; a half-filled entry counts as incomplete.
Gateway Payment Config
The routing-depth configuration for gateway links such as QR code plates and aggregate scanning. Menu path: App Workbench → Gateway Payment Config. The sidebar menus "Aggregate Pay Config" and "QR Code Plate Pay Config" also point to this page — QR code plates and aggregate pay share this single configuration.
The configuration dimensions form a "client environment × payment form" matrix: four environments (WeChat / Alipay / UnionPay App / Douyin) × two forms (H5 / mini program). First choose the configuration depth (a three-option radio) for the whole page:
| Depth | Semantics |
|---|---|
| Auto | Each cell uses the system default pay method (WeChat environment uses wechat_jsapi / wechat_mini, Alipay H5 defaults to the OAuth-free alipay_qr, etc.) — the recommended starting point |
| By pay method | Pick a pay method per cell from a dropdown |
| Specify directly | Pick "channel merchant → capability" directly per cell, skipping routing (for troubleshooting / special scenarios) |
The page has two helper blocks:
- Routing hit preview: each cell shows in real time the "hit channel merchant / capability" or "not configured" — you can predict where a payment lands without actually scanning;
- Coverage summary: the top shows the number of configured cells and the gaps (cells whose "other form under the same environment is already configured" are listed in orange), with a one-click jump to Channel Routing to fill them in.
In "by pay method" and "specify directly" modes, at least one row must be configured — an all-empty page cannot be saved. Saving requires confirmation.
Cashier Config
Configures which payment items the unified cashier page displays in each environment. Menu path: App Workbench → Cashier Config.
The bucket structure splits at the top level into three terminal types: H5 / WEB / mini program: H5 has five buckets by client environment (browser / WeChat / Alipay / UnionPay App / Douyin), mini program has four (no browser), WEB has no buckets. Each bucket maintains a payment item list:
| Field | Description |
|---|---|
| Name / icon | The button label and icon shown on the cashier; under "by pay method" resolution the icon automatically follows that method's provider icon |
| Recommended badge | A green label that guides users to prefer this item |
| Sort | Display order within the bucket |
| Resolution mode | By pay method (resolved via Channel Routing, for regular scenarios) or specify directly (a fixed "channel merchant + capability", skipping routing) |
Deleting a payment item is a dangerous operation and requires confirmation.
Related Links
- Channel Routing (admin panel) — the routing strategy from the operations perspective
- Gateway Payment — the business side of the unified cashier / aggregate scanning
- Developer Debugging — fire a test payment once configured