Channel Configuration (Common Operations)
The config pages of every payment channel the system integrates (Alipay, WeChat, Lakala, Shengpay...) share a highly consistent structure: the three stages ISV keys → merchant onboarding → channel-merchant management. This page covers the common model and the per-channel differences; per-channel intros live on the corresponding channel pages of the "Versions and Channels" section (e.g. Alipay, WeChat Pay, Lakala).
For the channel-merchant concept (frozen environment flag, enable/disable, deletion rules) see Channel Merchants; for a complete first-time walkthrough of connecting Alipay / WeChat on a fresh system, see Channel Integration.
Where to Enter
Each payment product's config entry is always at: Payment Management → Payment Product Configuration → the product → Config Detail. Inside, config pages are split per product (e.g. one page each for "WeChat (ISV)" and "Lakala"), offering key config and related app entries; a single merchant's channel-side info is maintained on its channel-merchant detail page.
Two Integration Modes
| Mode | Meaning | What to configure |
|---|---|---|
| ISV (service provider) | The platform onboards merchants as a service provider; merchants are "special / sub merchants" on the channel side | ISV keys + the channel-side sub-merchant number recorded at onboarding |
| Direct | The merchant opens the account on the channel side itself; the platform only initiates transactions | The channel merchant's merchant number and transaction keys |
Some channels support both modes (Alipay, WeChat, Huifu, etc.) — pick the product to provision according to the merchant's situation.
The Three-Stage Configuration Model
Stage 1: ISV Keys (ISV Mode)
For ISV-mode channels, configure the platform-level ISV keys first (certificates, private keys, API keys, etc., varying by channel), in the "ISV Keys" drawer of the product config page, per environment (one set each for sandbox / production).
- WeChat (ISV) is special: the platform itself is the service provider — no ISV number needed; configure the APIv3 key and payment certificate directly;
- Aggregate channels (Lakala etc.) usually also have institution codes, terminal numbers and other dedicated fields;
- Secret-type fields submit only the changed parts on save; certificate files (
.pem/.crt) are uploaded by picking the file directly.
Stage 2: Merchant Onboarding (Creating the Channel Merchant)
Create a channel merchant for a specific merchant: pick the payment product → fill in the channel-merchant name + channel-side merchant number (special merchant number / merchant ID, per the channel) → done. For the detailed flow and rules see Channel Merchants.
- Alipay (ISV) onboarding also requires picking the owning ISV app, and the app authorization token (the merchant-granted
app_auth_token) can be filled in now or later; - Onboarding only records the "number", not the keys — keys are configured in the next stage, per merchant.
Stage 3: Channel-Merchant Management
Enter via "Manage" on the channel-merchant list; maintain a single merchant's channel-side config as grouped cards:
| Group | Common content |
|---|---|
| Basic management | Basic info, renaming; direct mode configures transaction keys here (APIv3 key / certificates etc.); Alipay (ISV) has app authorization token maintenance |
| Trade config | Allocation receivers; WeChat direct and Alipay additionally have transfer config (transfer scenes and the initiating app) |
| App management | Channel-side apps and capability binding: WeChat goes through the WeChat app hub; Alipay maintains channel-merchant apps here (app ID + key / certificate + authorization type) and can bind payment apps by capability |
| Terminal ledger | Under development |
Alipay delegated-operation authorization
The Alipay (ISV) app authorization token can be maintained in two ways: paste the merchant-granted token manually, or use the delegated-operation authorization link — generate an authorization link / QR code for the merchant to scan; the token updates automatically after the authorization callback (the authorizing account must match the sub-merchant number bound at onboarding).
Per-Channel Differences Quick Reference
| Channel | Modes | Key specifics |
|---|---|---|
| Alipay | ISV + direct | App system (ISV apps / channel-merchant apps); authorization tokens; at most 3 transfer scenes enabled |
| ISV + direct | The platform is the service provider; certificate + public-key dual sets; transfers can only be initiated by an Official Account | |
| Douyin | direct | Transfer app and transfer-scene config |
| Lakala / Sheng Pay / Leshua / Dougong / Fuyou / Suixingfu (vbill) / Haikerongtong (hkrt) / Hema Pay | ISV (aggregate) | ISV keys + merchant-number onboarding; WeChat-type payments need WeChat apps bound (sub-app level) |
| Huifu (Adapay) / Yinsheng (YSEP) | ISV (+ direct) | Yinsheng has an ISV-layer config |
| UnionPay / UMS (LianDong YiSheng) / YeePay / Easy Pay | direct | Merchant number + keys suffice |
| Stripe | direct | Cross-border oriented; key config |
WeChat app binding for aggregate channels
When aggregate channels (Lakala, Leshua, etc.) process WeChat JSAPI / mini-program payments, the openId depends on the sub app (sub_appid): bind the merchant's WeChat app to the corresponding capability under "App Management / Capability Binding" in the channel-merchant detail, otherwise order placement reports a missing app.
Related Links
- Channel Merchants — concept, creation and allocation receivers
- Channel Integration — complete walkthroughs for Alipay / WeChat direct
- Payment Apps — WeChat / Douyin app registration and capability binding
- Channel Intros — each channel's intro page ("Versions and Channels" section: Alipay / WeChat Pay / Lakala, etc.)