Can an existing channel serve a new site or business type? Scope, configuration versions and old orders

The same operator launching a website, adding an app or expanding beyond memberships does not automatically make an existing payment channel suitable for every new scenario. Explain the change to the integration team, confirm the supported scope, then update configuration. This merchant checklist supports WenFuPay WeChat, Alipay and UnionPay collection discussions; no business label receives unconditional approval.

Continue by topic

Explain the change, not just the domain

Describe old and new entry points, operating entity or responsible team, products, the payment-to-delivery flow, expected amount range, currencies, refunds and support. Labels such as C2C, B2C and P2P do not replace an explanation of the product and funds flow.

Record domain changes separately from business changes. Even a new presentation entry can affect payment environment, callback addresses or order ownership; a new product type also needs channel-scope confirmation. Copying an account or checkout to another site and successfully creating an order is not proof of approval.

Retain a traceable configuration after confirming scope

Confirm merchant or project ownership, available methods, amount and fee conditions, settlement network, callback contract and effective time with the technical team. Formal materials follow account setup and integration arrangements; do not assemble fields or keys from another merchant’s online examples.

A merchant may version its own configuration, recording applicable sites and products, approver, effective time and acceptance evidence. This is a local management method, not a public WenFuPay API field. Whether sites share a merchant, order namespace or key depends on the actual confirmed integration.

A new configuration does not erase old orders

Old orders retain their original site, purchaser, product, amount and configuration snapshot. Match late notifications and queries to those orders; never assign them to whoever most recently logged into the new site or stop recording them because the old entry is offline.

Example: S1 creates OLD-A before the switch, but success arrives after S2 launches. Check S1’s original purchase and delivery history. A missing row in the new database does not prove an invalid payment. Confirm secure retention or revocation of old credentials and the handling window for historical notices with the technical team; do not keep old keys active indefinitely on your own initiative.

Launch with entry-specific acceptance and a rollback plan

Test old-entry orders, new-entry orders, repeated notices, amount mismatches, unreachable callbacks and identical order prefixes. If launch fails, stop new attempts and preserve evidence rather than deleting paid records. A rollback also needs a decision about which old orders remain active.

Send WenFuPay the change list and intended timing together. Confirm scope and configuration before testing against formal documentation. Merchant USDT settlement from CNY collections currently uses TRC20 only; merchant-owned-wallet TRC20/ERC20 monitoring is a separate service. Confirm fees and minimum amounts per actual channel rather than treating the old site’s terms as a universal promise.

Frequently asked questions

Should an unchanged operator confirm a new domain too?

Yes, confirm first: payment environment, ownership, callbacks and products may differ. One operator does not automatically imply one configuration or channel scope.

Can all old callbacks stop when the new site launches?

Not based only on launch time. Reconcile old orders and unresolved items, then confirm notice handling and credential changes with the technical team.

References