Payment Master Data
Payment master data is the system's "catalog of supported pay capabilities": which channels, which products and which pay methods are available is defined here. Menu: Payment Management → Payment Master Data.
All five pages are read-only dictionaries: the data ships with the system version and channel integrations; the operations side has no editing entry (and doesn't need one) — day-to-day use is looking up codes and checking a product's capabilities.
The Five Dictionary Pages
| Page | Content | Typical use |
|---|---|---|
| Payment Channels | The list of payment channels the system supports (Alipay, WeChat, Lakala...), with a channel intro and its payment-product list | Check which products a channel offers and whether sandbox is supported |
| Payment Products | The channel × integration-mode granularity (e.g. "WeChat (ISV)" and "Alipay (direct)" are two different products), with owning channel, sandbox support, product traits (ISV / terminal registration / sandbox) and pay capabilities | Confirm the product form before provisioning a channel merchant |
| Pay Capabilities | The atomic checkout capabilities a product offers (e.g. WeChat JSAPI, Alipay QR), plus a reverse lookup of related products | Cross-reference when selecting capabilities in routing and cashier config |
| Pay Providers | The provider list grouped by provider (WeChat / Alipay / UnionPay...) | Understand the provider taxonomy |
| Pay Methods | The pay-method catalog grouped by provider (switch providers via tabs), e.g. JSAPI, Mini Program, QR and H5 under WeChat | Look up pay-method codes and meanings |
Click "View" on a row to open the detail drawer with the full attributes; a payment-product detail also lists the capabilities the product includes.
How They Relate
Payment channel ──1:N──> Payment product ──links──> Pay capability
(Alipay) (Alipay direct) (alipay_qr ...)
Pay provider ──1:N──> Pay method
(WeChat) (wechat_jsapi / wechat_mini ...)- Channel vs provider: a channel is the third-party payment institution (Lakala, Shengpay); a provider is the payment brand the payer pays with (WeChat, Alipay, UnionPay). Aggregate channels (such as Lakala) can offer pay methods of multiple providers.
- The product decides the provisioning form: what you pick when creating a channel merchant is a payment product; the product's ISV / direct traits decide which channel-side credentials must be filled in.
- Pay methods are the configuration language of routing and the cashier: channel routing dispatches by pay method, cashier config displays by pay method — codes follow this catalog.
Difference from "Payment Product Configuration"
Payment Product Configuration is the operations switchboard: it decides whether a product can be provisioned right now and whether it sits in sandbox or production; this page is the dictionary: it explains what the product itself is. Look up the product form here first, then manage enable/disable and environments in product configuration.
Where to look up codes
Codes like wechat_jsapi and alipay_qr that appear in configs or integration docs are searched on the "Pay Methods" page under the provider tabs; channel-side codes (e.g. the lakala_pay product) are searched on the "Payment Products" page.
Related Links
- Payment Product Configuration — product enable/disable and environments
- Channel Merchants — provisioning receiving identities per product
- Channel Routing — dispatching by pay method
- Code Tables — the online code reference