Go-Live Checklist
After the system is deployed, walk through this checklist to complete the go-live. ✳️ = required — skipping it breaks a core flow; 🌟 = recommended — pick per your scenario.
For the concrete actions behind each item, see the corresponding step in From Deployment to First Payment.
Phase 1: Admin Panel Initialization
Get the system into a basically usable state: sign-in-able and configurable.
Accounts and Security
- ✳️ Production: create a proper operations administrator account and assign permissions, and confirm the config item
enable-admin=falseturns off the development super administrator (the development super administrator can only sign in to the admin panel in the dev environment and cannot log in at all in production) - 🌟 (development environments only) change the default password of the development super administrator (System Management → User Management)
- 🌟 Assign separate roles to operations staff with different duties (see User Management)
Platform Configuration (System Management → System Configuration → Platform Configuration)
- ✳️ Endpoint configuration — the payment gateway frontend URL (cashier redirects depend on it) and the backend API URL (callback notifications depend on it); both can be connectivity-checked with the "Check" button
- ✳️ Production: the backend API URL must be a publicly reachable address (Alipay / WeChat and other channel callbacks depend on it), HTTPS recommended; for local / intranet debugging see Local Debugging
- 🌟 Endpoint configuration — the admin panel / merchant panel URLs (used for third-party login callbacks)
- 🌟 Site configuration — system name, logo, ICP filing, and copyright info
- 🌟 OSS configuration — file storage; see Storage Configuration
- 🌟 Email configuration — notification scenarios such as password recovery
- 🌟 Sensitive word policy — enable/disable sensitive word detection
Payment Environment (Access Configuration → Payment Product Configuration)
- ✳️ For sandbox integration: switch "Alipay (direct)" and other products to sandbox first, then create channel merchants (the environment is frozen when the channel merchant is created; the order cannot be reversed)
- ✳️ Production deployment: confirm
sandbox-enabled=false(mandatory in production; at startup the system resets leftover sandbox products to production automatically) - 🌟 Review the enabled state of built-in payment products / pay methods under "Payment Management → Payment Master Data" (master data is read-only; enable/disable as needed)
Payment Security (Payment Management → Payment Security)
- 🌟 Configure "risk control strategies" as needed: blacklist blocking (on by default), overseas IP blocking, region blocking, etc., plus the handling on hit (block ordering / record only); defaults are fine at launch, tighten later per observed risk
- 🌟 Maintain blacklists in "Blacklist Management" when suspicious sources appear; "Risk Hit Records" support after-the-fact review; adjust interface access security policies in "API Security Configuration" as needed
Phase 2: Merchant and Payment Readiness
Get a merchant actually receiving money.
Merchant Onboarding (Merchant Management → Merchant List)
- ✳️ Create the merchant: fill in the merchant info and administrator info, and record the one-time administrator initial password
- 🌟 Pass the initial password to the merchant administrator, and remind them to change it after first signing in to the merchant panel
- ✳️ Confirm the merchant's default app and default store were created automatically (Merchant Workbench → App Management)
Channel Configuration (Merchant Workbench → Channel Merchants)
- ✳️ Create channel merchants: pick the payment product and fill in the channel parameters (Alipay: merchant user ID; WeChat: merchant number)
- ✳️ Configure channel keys: Alipay (app ID + authentication mode + Alipay public key + app private key; certificate mode additionally uploads three certificates); WeChat (API V3 key + API certificate + certificate serial number + payment public key)
- ✳️ Check that the channel merchant's "Environment" badge matches expectations (it should read "Sandbox" during sandbox integration)
- 🌟 Create separate channel merchants and keys for sandbox and production (environment snapshots are not interchangeable; production go-live requires rebuilding them)
- 🌟 Additionally configure the WeChat "transfer scene" (channel merchant detail → Transaction Configuration; only needed when using WeChat transfers)
Integration Signature (merchant panel → Merchant Center → Business Configuration → API Credentials)
- ✳️ Generate the merchant RSA key pair and save the merchant public key (the private key is shown only once; keep it safe)
- ✳️ Copy the platform public key into your business system (used to verify response and callback signatures)
- 🌟 Communication key (AES; reserved field for data encryption, can be added later)
Optional Feature Configuration
- 🌟 Gateway payment configuration (app workbench): needed for the unified cashier / aggregate scan / QR terminal scenarios; not needed for plain API integration — see Gateway Payment
- 🌟 Domain verification files (Merchant Workbench → Business Configuration; the merchant panel entry is the same): to open H5 / JSAPI payment pages or the cashier inside WeChat, upload the WeChat-issued
MP_verify_*.txtfirst to complete ownership verification; the random verification file for the cashier mini program's "plain-link QR code" rules is uploaded on the admin panel under "Payment Config → Domain Verification Files" - 🌟 Cashier configuration (app workbench): customize which pay methods the cashier page shows in each environment
- 🌟 Channel routing (app workbench): decide which channel merchant each pay method of the app goes through (multi-channel splitting scenarios)
- 🌟 Allocation: first enable the allocation product permission for the merchant on the WeChat / Alipay merchant platform, then bind allocation receivers in channel merchant management; declare
allocation=trueat order time to freeze funds before allocation can be initiated — see Allocation - 🌟 EasyPay-compatible API (
/epay): for merchants integrating via the EasyPay protocol; it must be enabled in the operations panel gateway under "External Endpoints" before use — see EasyPay Integration
Acceptance
- ✳️ After setting the merchant private key in "Development & Debug → Payment Debug (Standard)", successfully initiate one (sandbox) payment and get the QR code displayed
- ✳️ Pay with the (sandbox) wallet and see the order's business status turn to "Success" (if callbacks cannot reach you, a manual "Sync" works too)
- ✳️ The payment shows up on the "Payment Trades" page, with the correct amount and refundable balance
- 🌟 Re-check the string-to-sign once with the "Signature Debug" page to confirm your business system's signing matches the platform
- 🌟 Run one small real end-to-end payment before going live in production