Order Status Query

If a downstream merchant encounters network jitter, timeout, or other abnormalities when calling the transfer interface (deposit/withdrawal), they can pass in the unique transaction serial number (transfer_id) to actively query the final success/failure status of the transaction.

API Information

Property	Value
Path	POST /papi/v1/order/status
Authentication	Agent Token (Bearer)
Content-Type	application/x-www-form-urlencoded

Request Headers

Header	Value	Required
Authorization	Bearer {agent_token}	✅ Yes

Request Parameters

Parameter	Type	Required	Description
transfer_id	string	Yes	The merchant's unique custom transaction serial number

Request Example

curl -X POST https://api.example.com/papi/v1/order/status \
  -H "Authorization: Bearer {agent_token}" \
  -d "transfer_id=TXN202606152311001"

Response Fields

Data Fields

Field	Type	Description
transfer_id	string	Unique serial number passed in the merchant request
hub_member_id	string	Unique player ID on the gateway platform (Format: MerchantPrefix_PlayerID)
currency	string	Transaction currency
amount	decimal	Transaction amount
transfer_type	string	Transaction type: • deposit • withdraw
balance_before	decimal	Player's account balance before the transaction
balance_after	decimal	Player's account balance after the transaction
status	string	Transaction status: • success • failed • pending
remark	string	Remark
created_at	string	Order creation time (ISO 8601 format)

Successful Response (HTTP 200)

{
  "code": 0,
  "data": {
    "transfer_id": "TXN202606152311001",
    "hub_member_id": "TESTAGENT_PLAYER_USER_001",
    "currency": "CNY",
    "amount": 500.00,
    "transfer_type": "deposit",
    "balance_before": 1000.00,
    "balance_after": 1500.00,
    "status": "success",
    "remark": "",
    "created_at": "2026-06-15T23:11:00+08:00"
  },
  "msg": "ok"
}

Error Response

Order Not Found (HTTP 200)

{
  "code": 7,
  "data": {},
  "msg": "order not found"
}