Order Management
The merchant panel's transaction queries and operations are concentrated in the "Transaction Orders", "Transfer Orders", and "Callback Notifications" sections; the detailed operations of each page (query, sync, close, refund, export, abnormal-order handling, etc.) are documented centrally in Business Feature Overview — this page is only an entry map.
All lists show only your own merchant's data (enforced by the login session; no merchant filter); time columns display in the timezone you selected; pages that support export export to Excel.
Entry Map
| I want to... | Menu entry | Details |
|---|---|---|
| Check whether a payment has arrived (fund transaction) | Transaction Orders → Payment Trades | Payment Order Management |
| Query by order origin (normal / gateway) | Transaction Orders → Payment Orders → Normal Orders / Gateway Orders | Payment Order Management |
| Initiate / query a refund | Transaction Orders → Refund Orders | Refund Management |
| Initiate a transfer | Transfer Orders → Initiate Transfer | Transfer |
| Query transfer records | Transfer Orders → Transfer Records / Channel Transfers | Transfer |
| Query allocation orders | Transaction Orders → Allocation Orders | Allocation |
| Check money in/out details (reconciliation) | Transaction Orders → Fund Flow | Abnormal Orders and Fund Flow |
| Handle orders that received money after being closed | Transaction Orders → Abnormal Orders | See below |
| Check my API request logs | Transaction Orders → Payment API Logs | See below |
| Check callback push records | Callback Notifications → Merchant Callback Push | Callbacks and Notifications |
| Check channel-side callback intake records | Callback Notifications → Channel Callback Records | See below |
Payment API Logs
Transaction Orders → Payment API Logs: the audit record of every call you make through the unipay open API (request ID, API, latency, access IP, error message) — the first stop when investigating "why did the API call fail".
- The request parameters and response payloads in the details are desensitized at write time, so they can be viewed and copied directly with no masking overlay;
- Filter by reqId, API path, traceId, and call status;
- Read-only page: logs cannot be deleted or modified.
Abnormal Orders and Channel Callback Records
- Abnormal orders: fund records where the local order was already closed / voided but the channel actually received the money. The merchant panel is view-only for them (including the raw channel callback payloads); handling actions (confirm, return funds, etc.) are performed by platform operations — contact operations when you find an abnormal record;
- Channel callback records: intake records of callbacks from the payment channel to the platform (filterable by processing status). Raw payloads are not exposed to the merchant panel; contact the platform when you need them.
Notes
- For the three-layer order model (payment order / payment trade / channel order), see the beginning of Payment Order Management — prefer "payment trades" for reconciliation; it is the single source of truth from the funds perspective;
- Each list supports combined time / status / order-number queries and export;
- The operations side's "Transaction Orders" section is the isomorphic, all-merchant view.