Admin Panel Overview
The operations admin panel ("admin panel" for short) is the unified operating platform used by the platform operator, covering merchant onboarding, channel integration, platform configuration, and system administration. Merchant self-service operations happen in the Merchant Panel; the two panels share many mirrored entries (such as channel merchants and API credentials) backed by the same data.
For the login URL and default accounts, see Run - Default Login.
Feature Sections
The admin panel sidebar is organized into the following sections by business domain:
| Section | Features | Description |
|---|---|---|
| Dashboard | Workbench, Analytics | Transaction overview and operational data |
| System Management | Users, roles, menus, dictionaries, platform configuration, notification center, system monitoring, logs | Platform-level system administration |
| Payment Management | Payment master data, payment product configuration, payment apps, QR plate management, integration configuration, payment security | Payment-domain master data and configuration |
| Merchant Management | Merchant list, channel merchants | Merchant onboarding and managed-administration entries |
| Transaction Orders | Payment trades, payment orders, refunds, allocation, fund flow, abnormal orders | Transaction queries and handling |
| Transfer Orders | Initiate transfer, transfer records, channel transfers | Transfer business |
| Callback Notifications | Merchant callback push, channel callback records | Callback chain troubleshooting |
| Development & Debugging | Payment debugging (normal/gateway), signature debugging, auth debugging | Verify the payment chain without writing code |
| Extensions | EasyPay | Compatibility-protocol access |
Start here for a new system
If the system has just been deployed, follow the main track From Deployment to First Payment first — this page is only a feature map for quick lookup.
Common Task Entry Points
| I want to... | Where to go |
|---|---|
| Change the system name, logo, or filing information | System Management → System Configuration → Platform Configuration → Site Configuration |
| Configure the access URL of each panel (payment callbacks depend on it) | System Management → System Configuration → Platform Configuration → Endpoint Configuration |
| Create a merchant | Merchant Management → Merchant List → New |
| Configure payment channels for a merchant | Merchant List → Manage → Merchant Workbench → Channel Merchants |
| Configure Alipay / WeChat channel keys | Merchant Workbench → Channel Merchants → Manage → the matching group |
| Configure platform-level ISV keys / the Alipay ISV app | Payment Management → Integration Configuration → Payment Product Configuration |
| Decide which channel merchant receives a payment | Merchant Workbench → App Workbench → Payment Routing |
| Look up a payment order | Transaction Orders → Payment Trades / Payment Orders |
| Handle a refund | Transaction Orders → Payment Trades → Refund |
| Check whether a callback has been sent out | Callback Notifications → Merchant Callback Push |
| Create an operator account | System Management → Permissions → User Management |
| Verify the payment chain works | Development & Debugging → Payment Debugging (normal) |
| Ban a suspicious source IP | Payment Management → Payment Security → Blacklist Management |
| Investigate "transaction restricted" reports | Payment Management → Payment Security → Risk Hit Records |
| See how today's / recent transactions look | Dashboard → Workbench / Analytics |
| Publish an announcement to all users | System Management → Notifications → Announcements |
| Find out why an open-API call fails | System Management → Logs → Open API Logs |
| Force an account offline / unlock it | System Management → System Monitoring → Online Users / Login Lockout |
| Change my own password or bind an email | Avatar at the top right → Profile |
| Adjust password strength and login lockout thresholds | System Management → System Configuration → System Security Configuration |
Core Concepts
- Merchant Workbench: the entry for the operations side to administer all configuration of a single merchant (open it from the "Manage" action in the merchant list), grouped as tile cards. The configuration pages the merchant sees in the merchant panel mirror it, backed by the same data.
- Channel Merchant: the merchant's onboarding record on a payment product (e.g. Alipay direct); the sandbox/production environment snapshot is frozen at creation, and it is the carrier of routing and key configuration.
- App (appId): the invocation isolation unit under a merchant; transactions that do not specify an appId fall back to the "default app". Gateway payment, the cashier, and payment routing are all configured per app.
Permission Model
- The admin panel uses role - menu authorization: a role binds the visible menus and action permission codes, and each user is assigned a role (single role). See User Management.
- Menus themselves are maintained under "System Management → Base Data → Menu Management" and usually need no changes; when onboarding a new operator, duplicate an existing role under "Permissions → Role Management" and fine-tune it.
Related Sections
- From Deployment to First Payment: the main track from deployment to the first payment
- Merchant Management / Channel Merchants / Application Configuration / Payment Routing: merchant onboarding and payment dispatch in detail
- Payment Master Data / Payment Product Configuration / Payment Apps / Common Channel Configuration: payment-domain master data, product and app configuration
- Payment Platform Configuration / System Security Configuration / Notifications and Email / Logs and Monitoring: platform-level configuration
- Permissions and Menu Management / Profile: authorization and account self-service
- Payment Security and Risk Control: anti-replay, blacklists, and hit-record investigation
- Developer Debugging / EasyPay Plugin: debugging tools and the compatibility protocol
- Business Feature Overview: daily operations such as orders, refunds, transfers, and allocation