Skip to content

Mock Channel: Console Tour ​

Updated: 11/10/26, 10:51:10 AM

The console shares the same origin as the mock service; open http://127.0.0.1:10400/ in a browser (hash routing).

Login ​

The default account is mock / mock; browser login exchanges for a long-lived cookie (login itself never times out; changing the account or password invalidates old sessions); scripts and curl use the Authorization: Basic header directly. Set mock.console-auth-enabled to false to disable authentication.

Login protects the console only. Payer-facing standalone pages (payment confirmation, mock payment, payment code) rely on anonymously allowed endpoints; /v3/mock/** uses signatures and is not part of this.

Group Map ​

GroupViewWhat it is for
OverviewDashboardToday's counts, amount, success rate, status distribution, merchant ranking, event stream
TransactionsPayment OrdersSearch orders, inspect payment parameters and callback records, force a final state
TransactionsRefund OrdersQuery refunds and confirm manually (WeChat refunds default to processing)
TransactionsSplit PaymentsSplit allocations and receiver bindings, decided by last-digit rules
TransactionsTransfer OrdersCreate and query transfer orders
TransactionsPre-AuthorizationCapture, unfreeze, push a final state, and resend callbacks for freeze orders
Merchant ProfilesSubject ProfilesISV and merchant profiles in two tiers; freezing cascades to order rejection
Merchant ProfilesMerchant OnboardingAccept and track ISV onboarding applications
Merchant ProfilesReceiver ManagementSplit payment receiver profiles
Merchant ProfilesTerminal LedgerTerminal registration and status
Merchant ProfilesWeChat EmulationEmulated WeChat apps, users, and openids
Mock ControlIntegration ConfigRuntime switches and split payment last-digit rules
Mock ControlReconciliation DataGenerate bill files and create three difference types
Mock ControlPayment Parameter SimulationPaste payment parameters → validate → short code QR → phone decision
SystemRuntime SettingsService-level parameters and "Clear All Data"
SystemIntegration MaterialsGlobal key pair and gateway address for copying to the main app side
SystemAPI DocsList and fields of the 21 gateway endpoints
SystemAboutVersion and runtime environment information

Six Standalone Layout Pages ​

These pages have no sidebar and usually open directly from a QR code or payBody:

PageAddressPurpose
Payment confirmation page/#/pay/{tradeNo}Returned as payBody for QR, H5, PC, and APP orders; three buttons decide the final state manually and trigger callbacks, and the page echoes callback delivery status
Mock payment page/#/sim/{code}Opened by a short code; click "Simulate Payment Success / Failure" to decide parameter simulation
Pre-authorization confirmation page/#/preauth/{authNo}Capture and unfreeze after a pre-authorization freeze
WeChat authorization emulation/#/wxauthSimulates the official-account authorization redirect
WeChat payment emulation/#/wxpay/{tradeNo}Simulates the in-WeChat payment page
Payment code emulation/#/authcodeConfigure and generate a payment code QR on one page; supports ?provider=WECHAT&mode=CONFIRM presets

The payment confirmation page only performs manual decisions and shows no "suggested action" badges: automatic decisions belong to transaction defaults and the override chain, manual decisions belong to this page.

Common Operations Quick Reference ​

I want toGo to
Fail an order or keep it pendingPayment confirmation page: click "Payment Failed" or "Keep Pending"
Change the result of all orders for one merchantSubject Profiles → per-subject overrides
Create a split payment failureIntegration Config → split payment rule table, change the last-digit rule
Create a reconciliation differenceReconciliation Data page, three switches
Clear all transactions and start overRuntime Settings → Clear All Data (profiles and rules untouched)
Give the keys to the main appCopy both items from Integration Materials
Check how an endpoint is calledAPI Docs page