Skip to content

Payment Config ​

Updated: 10/15/26, 10:20:22 AM

Platform-level configuration of payment products / providers / QR plates / domain verification / open apps. For the semantics of products and providers see the Web panel's Payment Config; this page covers the operations on the phone.

Payment Products ​

  • List: product cards with a brand icon, product name and code, channel, feature tags (ISV / sandbox supported), and description;
  • Product detail: basic info (code, channel, active environment, terminal or not, API invocation style, pay identifier type, ISV or not, pay capabilities, product intro);
  • The only editable field is "Active Environment" (production / sandbox; sandbox is selectable only for sandbox-supported products) plus the enable toggle — channel parameters (ISV apps, keys, authorizations) are directed to the Web admin panel for maintenance on the phone.

Product Config (Grid) ​

A config overview of all products: each cell shows the product and its state (disabled / sandbox / production); tap to open the corresponding config page — Alipay ISV and WeChat ISV go to the channel ISV config page, and the other products land on the product detail (active environment config).

Channel ISV config page (Alipay ISV as an example): an identity card + a config progress checklist (each item shown as configured / not configured, with a completion rate) + sandbox environment management. Tapping a checklist item opens guidance — check the progress on the phone, fill in the parameters on the Web. WeChat ISV additionally has a capability binding page: bind the "platform WeChat app" to each pay capability per product (bindings can be cleared); candidate apps are auto-filtered by the type the capability requires.

Pay Providers ​

A read-only list of providers (WeChat Pay / Alipay / Douyin / UnionPay and other C-end wallet brands): brand icon, name, code, description, number of pay methods.

QR Plate Management ​

The full lifecycle of static collection plates:

  • List: filter by code, name, status, program type (H5 / mini-program), amount type (random / fixed); cards show the bound merchant ("Unbound" when not bound);
  • Batch create: batch number auto-generated (or hand-filled, duplicate-checked before submitting), quantity 1-999, name, program type (uniform for the whole batch, immutable after creation), amount type, fixed amount (required for fixed-amount plates), status, remark;
  • Detail actions: enable / disable, edit (name, amount type, fixed amount, the allocation switch — when turned on, an allocation availability pre-check runs and lists the risks without blocking the save, remark), bind / unbind merchant, ownership settings (a bound plate can further specify an app and a store), delete (strong confirmation that requires typing the plate name).

The binding dialog: pick the merchant first, then optionally the app and the store — this decides which app / store ledger the plate's collections go to.

Platform Domain Verification ​

WeChat domain verification files hosted by the platform (distinct from merchant-level self-service upload):

  • List: filter by owner (platform / merchant), merchant number, file name, verification code;
  • Upload: manually fill in the file name (any format) and the file content;
  • Edit: only the remark can be changed; the file content is read-only and copyable.

Platform WeChat / Douyin Pay Apps ​

Registration of platform-level open apps (Official Accounts / mini-programs / mobile apps, etc.): app name, type, AppId, AppSecret (leave blank when editing = unchanged). The AppId is unique under the same merchant (auto duplicate-checked); delete is a strong confirmation that requires typing the AppId; changing the app type clears incompatible capability bindings (with a strong confirmation).

Where apps come from

Register the WeChat / Douyin mini-program and Official Account AppIds on the corresponding open platform, record them here first, then reference them in channel capability binding and on the merchant side.