Channel Merchants
A "channel merchant" is your merchant's receiving identity on a specific payment channel (WeChat, Alipay, ...). For the concept and lifecycle, see the admin-side Channel Merchants page. This page covers only the merchant-panel self-service part: which channel parameters you can maintain yourself, and where to change them. Menu path: Merchant Center → Payment Config → Channel Merchants.
Channel merchant creation is available on both panels: on the admin panel you pick a merchant first, while on the merchant panel the record is created directly under the current merchant — the flow is otherwise identical.
List Page
The list shows all channel merchants under the current merchant (hence there is no filter section):
- The Payment Product column shows the channel logo and product name; products that support sandbox show an environment column (sandbox / production, color-coded) — the environment flag is a snapshot frozen at creation and does not change when the product switches;
- Enable switch: once disabled, the channel merchant immediately stops receiving payments and routing no longer hits it; switching requires confirmation;
- The merchant panel has no delete entry — disable it if you no longer use it; deletion is an admin-panel operation (channel merchants with transaction records cannot be deleted either).
Self-Service Scope
Click "Manage" in the list to open the channel merchant detail page. The detail page loads a different management UI per payment product; products that currently support self-service maintenance:
| Payment Product | Self-maintainable in merchant panel | Notes |
|---|---|---|
| Alipay (direct) | The most complete parameter set: add/edit/delete apps, keys / certificates, capability binding, transfer apps and transfer scenes, allocation receivers | App management is a secondary page inside the detail page |
| Alipay (ISV) | Self-service generation of the ISV delegated-operation authorization link, allocation receivers, rename, enable/disable | Channel parameters live on the ISV / platform side |
| WeChat (direct) | Full set of APIv3 key + merchant certificate + platform public key, WeChat apps, capability binding, allocation receivers | |
| WeChat (ISV) | WeChat apps, capability binding, allocation receivers, rename, enable/disable | ISV credentials stay on the platform side |
| Douyin (direct) | The merchant private key / serial number / encryption key trio, Douyin apps, capability binding, allocation receivers | |
| Leshua | Only basic info viewing, rename, WeChat app capability binding | All channel parameters are configured by operations |
The detail pages of other channels (UMS, Lakala, Huifu, Shande, Fuyou, etc.) show "not supported yet" — their parameters are configured on your behalf by the admin panel; contact platform operations staff. All channel merchants can be renamed and enabled/disabled in the merchant panel, regardless of channel.
Key Configuration (Direct Channels)
The key entries of the three direct products are all in the "Key Configuration" card on the detail page:
| Product | What to configure |
|---|---|
| WeChat (direct) | APIv3 key (apiKeyV3); upload three PEM files — merchant certificate apiclient_cert.pem, private key apiclient_key.pem, platform public key pub_key.pem; certificate serial number, public key ID |
| Douyin (direct) | Merchant private key, merchant serial number, message encryption key |
| Alipay (direct) | Configured at the app level (see next section); supports both "public key mode" and "certificate mode" signature verification |
Saving keys requires confirmation, and only sensitive fields that were modified are submitted — certificate files echo their file names and are overwritten only when re-uploaded.
Alipay App Management
The detail page of an Alipay direct channel merchant contains a dedicated "App Management" secondary page (card grid + dashed add card). Each Alipay app (corresponding to one app on the Alipay Open Platform) maintains:
- Basic info: app name, app type (mini program / mobile app / web app), Alipay appId (unique within the same channel merchant);
- Key configuration: environment follows the channel merchant (sandbox / production shown read-only); public key mode fills in the Alipay public key + app private key, certificate mode uploads three
crtcertificates; the interface encryption key is optional.
Deleting an app requires manually typing the appId to match as confirmation. Changing the app type automatically clears incompatible capability bindings, and the page prompts you to reconfigure.
ISV Delegated Operation Authorization (Alipay ISV)
Under the Alipay ISV product, the sub-merchant must complete a one-time "delegated operation authorization", which merchants can do themselves: detail page → ISV delegated-operation authorization card → "Generate delegated-operation authorization link", then show the QR code for the merchant's primary Alipay account to scan and confirm. The authorization status and authorization callback URL are visible in the card.
Allocation Receivers
For channel merchants that need allocation, maintain the receiver list in the "Allocation Receivers" card on the detail page. The full set of operations (add as binding, obtain account by QR, rebind, edit alias, unbind, delete) is identical to the admin panel — see the admin-side Channel Merchants - Allocation Receivers.
Two merchant-panel differences:
- Obtain account by QR: for openid / user ID types, an authorization QR code can be generated for the payee to scan and fill the account back automatically; WeChat and Douyin require an app to be selected first (accounts are bound at the app dimension);
- Failed bindings leave a trace: failed records are kept with the failure reason visible; fix the issue and use "Rebind".
Related Links
- Channel Merchants (admin panel) — concept overview, creation flow and deletion rules
- Allocation — the allocation business and receiver use cases
- Channel Routing — how channel merchants get hit by routing