Sync Allocation Order
Description
When an allocation order is in processing status, the merchant can actively sync the allocation status from the payment channel. Useful when the channel advances asynchronously, callbacks are delayed, or manual confirmation is needed.
Request
POST /unipay/sync/order/alloc
- Auth: RSA signature (
@PaymentVerify) - Response:
DaxResult<AllocSyncResult>
Parameters
Common params same as Pay - Common Parameters. Business parameters:
| Parameter | Type | Required | Max | Description |
|---|---|---|---|---|
| allocNo | string | No* | 100 | Platform allocation number |
| bizAllocNo | string | No* | 100 | Merchant allocation number |
*At least one required. Priority: allocNo > bizAllocNo
Example
json
{
"mchNo": "M200000001",
"appId": "APP001",
"reqId": "REQ20241201031",
"reqTime": "2024-12-01 12:31:00",
"sign": "Base64Signature",
"allocNo": "A2024120112345700001"
}Response
DaxResult<AllocSyncResult>, data fields:
| Field | Type | Description |
|---|---|---|
| orderStatus | string | Allocation status after sync (AllocOrderStatusEnum) |
| adjust | boolean | Whether status was adjusted (changed) |
Example
json
{
"code": 0,
"msg": "success",
"data": {
"orderStatus": "success",
"adjust": true
},
"sign": "Base64Signature",
"resTime": "2024-12-01 12:31:00",
"reqId": "REQ20241201031"
}Usage Tips
- Sync is idempotent — safe to call repeatedly; no duplicate allocation or notifications.
- When sync triggers a status change, the platform re-sends the notification per Async Callback (events
alloc.success/alloc.fail). - Once a terminal state (
success/partial/fail) is reached, sync no longer adjusts the status — check theadjustflag. - For full allocation details (including per-receiver results), call Query Allocation Order.