Retrieve detailed information for a specific peer-to-peer (C2C) order, including counterparty parameters, trade amounts, execution status, and payment configuration details.
/sapi/v1/c2c/orderMatch/getUserOrderDetailThis endpoint returns the comprehensive lifecycle state and transaction properties for an individual C2C (P2P) order using its order identifier (adOrderNo). It supplies order matching details, price and volume metrics, buyer/seller credentials, and payment methods.
Automated trading systems, reconciliation scripts, and webhook listeners use this endpoint to confirm incoming payment requirements, monitor counterparty actions, and verify trade completion status.
Payment Data Privacy Rules
• Completed Orders (≤ 90 days old): Full payment method name, account numbers, and banking details are returned.
• Cancelled Orders OR Orders > 90 days old: Only the payment method name is returned; specific sensitive account details are masked.
01
Parameters accepted in Body and HTTP Headers.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
clientType | Header | STRING | Required | Client Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE). |
adOrderNo | Body | STRING | Required | Unique order number identifier to query details for. |
x-gray-env | Header | STRING | Optional | Environment flag identifier used for internal gray/stage testing. |
x-trace-id | Header | STRING | Optional | Custom client trace ID for request lifecycle tracking and debugging. |
x-user-id | Header | STRING | Optional | Target user identifier for context validation. |
02
Example POST request using cURL to fetch order details.
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/getUserOrderDetail' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
"adOrderNo": "202608161234567890"
}'03
Example response returned on successful execution.
{
"code": "000000",
"message": "success",
"data": {
"orderNumber": "202608161234567890",
"advNo": "1122334455667788",
"tradeType": "BUY",
"asset": "USDT",
"fiat": "USD",
"fiatSymbol": "$",
"amount": "100.00",
"totalPrice": "101.50",
"unitPrice": "1.015",
"orderStatus": "COMPLETED",
"createTime": 1786953600000,
"counterPartNickName": "CryptoTraderPro",
"payMethods": [
{
"payId": 123456,
"payType": "BANK",
"payMethodName": "Bank Transfer",
"fields": {
"account": "1234567890",
"bankName": "Chase Bank"
}
}
]
},
"success": true
}| Field | Type | Description |
|---|---|---|
code | STRING | Standard Binance status code ("000000" indicates success). |
data.orderNumber | STRING | Unique identifier of the C2C trade order. |
data.tradeType | STRING | Trade direction from user perspective (BUY or SELL). |
data.asset | STRING | Cryptocurrency asset being traded (e.g., USDT, BTC). |
data.fiat | STRING | Fiat currency code (e.g., USD, EUR, KES). |
data.amount | STRING | Total cryptocurrency volume in the order. |
data.totalPrice | STRING | Total fiat settlement amount to be paid or received. |
data.unitPrice | STRING | Effective price per unit of cryptocurrency. |
data.orderStatus | STRING | Current order state (e.g., TRADING, BUYER_PAYED, COMPLETED, CANCELLED). |
data.payMethods | ARRAY | List of active payment methods bound to this order. |
04
Workflow for fetching individual C2C order details.
Automated Payout Matching
Inspect recipient banking and account numbers to automatically initiate external B2C/fiat payouts.
Status Polling & Sync
Periodically synchronize order status transitions across external merchant databases and accounting systems.
Order Reconciliation
Verify transaction amounts, fees, and counterparty nicknames for accounting logs and trade dispute tracking.