Getting Started with Mobile Apps
Beyond the Web admin panel and the Web merchant panel, the system offers four mobile-shaped applications. Start by telling them apart by who uses them:
| Admin App | Merchant App | Payment Gateway (H5) | Cashier Mini-Program | |
|---|---|---|---|---|
| Who uses it | Platform administrators | Merchants (owners / staff) | Customers (payers) | Customers (payers) |
| How it opens | Sign in deliberately | Sign in deliberately | Open the payment link in a browser (phone or computer) | Launched automatically by scanning the merchant's QR code inside WeChat / Alipay |
| Sign-in | Administrator account | Merchant account | No sign-in | No sign-in |
| Core capability | Mobile edition of the Web admin panel: inspection + high-frequency operations | Mobile edition of the Web merchant panel: daily transaction queries and refunds | Complete a payment inside a web page; channel authentication and third-party login also relay through it | Complete a payment inside a mini-program |
| Details | Admin App | Merchant App | Payment Gateway (H5) | Cashier Mini-Program |
Pick by Role
- Platform operators: day-to-day work happens in the Web admin panel; deploy the Admin App to handle transactions and configuration from a phone while away or on duty;
- Merchants: use the Merchant App for daily checks without turning on a computer (query transactions, refund, read notifications); go back to the Web merchant panel for complex configuration;
- Customers: install nothing — scanning the code shown by the merchant inside WeChat / Alipay opens the Cashier Mini-Program; opening the payment link in a browser (including desktop browsers) gives the checkout page of the Payment Gateway (H5). Both sit on the same collection pipeline and automatically land in the right form depending on where they are opened.
Account System
The Admin App, the Merchant App, and their Web counterparts share the same account and login-security system (account & password, two-factor authentication, password recovery, etc.) — change it once and it takes effect on every endpoint. The Payment Gateway and the Cashier Mini-Program serve payers and need no registration or sign-in (users coming from third-party login on the Web only pass through the gateway's relay page and do not sign in there).
What Each Needs to Go Live
| App | Go-live essentials |
|---|---|
| Admin App | Mini-program form: platform registration + compile & upload; App form: packaging and distribution, see Cross-Platform Apps |
| Merchant App | Same as above; in WeChat scenarios, the mini-program AppId used for login must be registered under "Payment Apps (WeChat)" |
| Payment Gateway (H5) | Deployed as a standalone front end under the payment gateway domain (payment and callback URLs are generated by the backend from that domain), see Payment Gateway (H5) |
| Cashier Mini-Program | Platform registration + domain verification + plain-link QR code rules, see Cashier Mini-Program |
Both management apps (Admin / Merchant) are built with uni-app: the same codebase compiles to WeChat / Alipay / Douyin mini-programs as well as H5 and native apps. For the build process see Cross-Platform Apps.
Related Links
- Admin App: Workbench / Login and Account Security / Merchant Management / Channel Merchants / Apps & Integration Configuration / Payment Configuration / Risk Control & Terminals / Trade Management / Notifications & System
- Merchant App: Workbench / Transactions & Refunds / Merchant Center / Payment Configuration
- Payment Gateway (H5): Checkout Pages / Authentication & Relay / Deployment & Go-Live
- Cashier Mini-Program: Publishing & Go-Live
- Cross-Platform Apps: compilation and release
- Gateway Payment: the business pipeline behind the checkout page