English
Mock Channel: Console Tour
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
| Group | View | What it is for |
|---|---|---|
| Overview | Dashboard | Today's counts, amount, success rate, status distribution, merchant ranking, event stream |
| Transactions | Payment Orders | Search orders, inspect payment parameters and callback records, force a final state |
| Transactions | Refund Orders | Query refunds and confirm manually (WeChat refunds default to processing) |
| Transactions | Split Payments | Split allocations and receiver bindings, decided by last-digit rules |
| Transactions | Transfer Orders | Create and query transfer orders |
| Transactions | Pre-Authorization | Capture, unfreeze, push a final state, and resend callbacks for freeze orders |
| Merchant Profiles | Subject Profiles | ISV and merchant profiles in two tiers; freezing cascades to order rejection |
| Merchant Profiles | Merchant Onboarding | Accept and track ISV onboarding applications |
| Merchant Profiles | Receiver Management | Split payment receiver profiles |
| Merchant Profiles | Terminal Ledger | Terminal registration and status |
| Merchant Profiles | WeChat Emulation | Emulated WeChat apps, users, and openids |
| Mock Control | Integration Config | Runtime switches and split payment last-digit rules |
| Mock Control | Reconciliation Data | Generate bill files and create three difference types |
| Mock Control | Payment Parameter Simulation | Paste payment parameters → validate → short code QR → phone decision |
| System | Runtime Settings | Service-level parameters and "Clear All Data" |
| System | Integration Materials | Global key pair and gateway address for copying to the main app side |
| System | API Docs | List and fields of the 21 gateway endpoints |
| System | About | Version and runtime environment information |
Six Standalone Layout Pages
These pages have no sidebar and usually open directly from a QR code or payBody:
| Page | Address | Purpose |
|---|---|---|
| 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 | /#/wxauth | Simulates the official-account authorization redirect |
| WeChat payment emulation | /#/wxpay/{tradeNo} | Simulates the in-WeChat payment page |
| Payment code emulation | /#/authcode | Configure 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 to | Go to |
|---|---|
| Fail an order or keep it pending | Payment confirmation page: click "Payment Failed" or "Keep Pending" |
| Change the result of all orders for one merchant | Subject Profiles → per-subject overrides |
| Create a split payment failure | Integration Config → split payment rule table, change the last-digit rule |
| Create a reconciliation difference | Reconciliation Data page, three switches |
| Clear all transactions and start over | Runtime Settings → Clear All Data (profiles and rules untouched) |
| Give the keys to the main app | Copy both items from Integration Materials |
| Check how an endpoint is called | API Docs page |