Skip to content

Merchant Panel Overview ​

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

The merchant panel is the management platform for merchant self-service: daily transaction queries and refunds happen here, and configuration such as API credentials, channel merchants, and the cashier can also be self-served here (the operations-side merchant workbench provides managed entries over the same data).

The login account is generated when the operator creates the merchant (the initial password is shown only once); after first login, change it promptly and consider enabling two-factor authentication (Profile → Security Settings).

Feature Sections ​

The merchant panel sidebar is organized into the following sections by business domain:

SectionFeaturesDescription
DashboardWorkbench, AnalyticsTransaction overview, quick entries, announcements; multi-dimensional transaction analytics
Merchant CenterThree groups: Basic Management / Payment Configuration / Business ConfigurationThe core of merchant self-service configuration
Transaction OrdersPayment trades, payment orders (normal / gateway), refunds, allocation, abnormal orders, fund flow, payment API logsDaily transaction operations
Transfer OrdersInitiate transfer, transfer records, channel transfersTransfer business
Callback NotificationsMerchant callback push, channel callback recordsCallback chain self-checks
Development & DebuggingPayment debugging (normal / gateway), signature debugging, auth debuggingVerify the payment chain without writing code
ExtensionsEasyPayCompatibility-protocol access

The three groups of Merchant Center:

  • Basic Management: merchant info, merchant users (sub-accounts), store management, QR plate management, system terminals;
  • Payment Configuration: channel merchants, app management (the app workbench holds payment routing / gateway payment config / cashier config / EasyPay config), WeChat apps, Douyin apps;
  • Business Configuration: API Credentials (API signing and encryption keys), domain verification files.

Profile (via the avatar at the top right): basic info, change password, email binding, third-party account binding, passkeys, two-factor authentication — the same feature set as the operations side; see Profile (Admin Panel).

Common Task Entry Points ​

I want to...Where to go
Get my API credentials (private key / platform public key / communication key)Merchant Center → Business Configuration → API Credentials
See today's takingsDashboard → Workbench, or Transaction Orders → Payment Trades
Refund a paymentTransaction Orders → Payment Trades → Refund
Onboard / configure a receiving channelMerchant Center → Payment Configuration → Channel Merchants
See which channel parameters I can change myselfChannel Merchants - self-service maintenance scope
Decide which channel a payment goes throughApp Workbench → payment routing
Configure which pay methods the cashier showsApp Workbench → cashier config
Create accounts for the store manager / cashiersMerchant Center → Basic Management → Merchant Users
Find out why an API call failsTransaction Orders → Payment API Logs
Check whether a callback went outCallback Notifications → Merchant Callback Push
See which receiving QR codes I haveMerchant Center → Basic Management → QR Plate Management
View transaction trends and per-provider success ratesDashboard → Analytics
Try whether payments go throughDevelopment & Debugging → Payment Debugging
Change my password / enable two-factor authenticationAvatar at the top right → Profile

Relationship with the Operations Side ​

Many pages of the merchant panel and the operations-side merchant workbench mirror each other (channel merchants, app management, API credentials, etc.); the data is shared and changes made on either side take effect immediately. The differences:

  • The merchant panel can only operate its own merchant's data — isolation is inherent;
  • Platform actions such as merchant creation and merchant-level account management do not appear in the merchant panel;
  • The channel merchant creation entry exists on both sides (in the merchant panel under Payment Configuration → Channel Merchants);
  • A few handling actions are open to the operations side only (such as abnormal-order handling, raw channel callback payloads, and merchant enable/disable); see the corresponding pages.