Callbacks and Notifications
The callback chain has two segments: channel → platform (channel callback records) and platform → merchant (merchant callback push). When troubleshooting "the merchant did not receive the notification", first check whether the channel callback arrived, then whether the merchant push succeeded.
Chain Overview
- Channel callback records: raw records of the notifications the platform received from channels (Alipay, WeChat, etc.); read-only;
- Merchant callback push: the platform pushes order results via HTTP POST to the callback URL configured by the merchant; failed pushes can be resent.
Merchant Callback Push
Entry: Callback Notifications (top-level menu, on par with "Trade Orders") → Merchant Callback Push (same on both panels)
Query conditions: business order number, event, message format, merchant (admin panel).
List columns: business order number (click to open details), event, message format, source (order / app / protocol), success or not, send count, merchant, last send time.
Operations:
| Operation | Description |
|---|---|
| Send records | A drawer showing each send of the notification task: sequence number, send type (auto / manual), success or not, HTTP status code, error message, creation time |
| Resend | Manually push the notification again (e.g. the callback URL is temporarily unavailable, or re-push after a merchant-side processing incident) |
Task details: notify URL, next send time, retry count, full message content (JSON).
Failed pushes retry automatically
After a push fails, the system retries automatically per policy (send count and next send time are visible in the task details); tasks that keep failing can be manually resent once the callback URL is fixed.
Channel Callback Records
Entry: Callback Notifications → Channel Callback Records
Query conditions: channel merchant, trade number, channel trade number, payment product, callback type (payment / refund / transfer / allocation), processing status, merchant.
Operations: view only — the details show the raw message of the channel notification (notifyInfo JSON), for verifying what the channel returned. The raw message is visible on the admin panel only; the merchant panel shows the callback processing status alone (contact the platform if you need the message).
Callback URL Configuration
The merchant's receiving URL is specified by the business system via the notifyUrl parameter when initiating the payment; see Async Callback for the message format and signature verification.
App-level unified notification subscriptions (per-app callback URL, subscribing to payment / refund events) live in "Async Notify Config" on the app workbench; this feature is under construction in the current version.
FAQ
| Symptom | Handling |
|---|---|
| Merchant did not receive the callback | Troubleshoot in order: (1) in Channel Callback Records, confirm the channel notification arrived and was processed successfully; (2) in Merchant Callback Push, check whether the push task succeeded and what HTTP status code it got; (3) verify that the notifyUrl passed at payment time is reachable from the public internet |
| Callback received but signature verification fails | Verify the signature with the platform public key (copy it from "API Credentials" on the merchant panel); message format: Async Callback |
| Push keeps failing | Check the callback URL's service status; after fixing it, run Resend on the task |
Related Sections
- Async Callback: message format, signatures, and response requirements
- From Deployment to First Payment: obtaining the platform public key (see the merchant API credentials section)