Execute final cryptocurrency release from Binance escrow to the buyer's account upon verified receipt of fiat payment, completing the peer-to-peer (C2C) order.
/sapi/v1/c2c/orderMatch/releaseCoin
This endpoint authorizes the irreversible transfer of cryptocurrency held in Binance escrow directly to the buyer's funding wallet.
It represents the final operational step in a P2P sell order workflow, transitioning the order status from BUYER_PAYED to COMPLETED.
Automated payout bots, merchant payment gateways, and high-frequency P2P settlement engines invoke this endpoint programmatically along with 2FA/MFA verification factors once inbound bank transfers or mobile money receipts are confirmed. For a complete implementation example, check out our guide on
How Binance P2P Release Crypto API
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).
|
orderNumber |
Body | STRING | Required | Unique C2C order number to release cryptocurrency for. |
authType |
Body | STRING | Optional |
Two-factor authentication mechanism (e.g., FIDO2, GOOGLE, SMS, EMAIL, YUBIKEY).
|
code |
Body | STRING | Optional | Generic verification code string. |
googleVerifyCode |
Body | STRING | Optional | 6-digit Google Authenticator TOTP token. |
mobileVerifyCode |
Body | STRING | Optional | SMS text verification code sent to the registered mobile number. |
emailVerifyCode |
Body | STRING | Optional | Email verification code sent to the account email. |
yubikeyVerifyCode |
Body | STRING | Optional | Hardware security key token string. |
payId |
Body | LONG | Optional | Payment configuration identifier selected by the seller. |
confirmPaidType |
Body | STRING | Optional | Confirmation type parameter. |
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. |
Releasing crypto assets transfers ownership instantly and permanently. Never release coins without directly verifying in your banking or payment mobile app that clear, non-reversible fiat funds have been credited.
Example POST request using cURL with Google Authenticator verification.
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/releaseCoin' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
"orderNumber": "202608161234567890",
"authType": "GOOGLE",
"googleVerifyCode": "654321"
}'
Example response returned on successful crypto asset release.
{
"code": "000000",
"message": "success",
"data": null,
"success": true
}
| Field | Type | Description |
|---|---|---|
code |
STRING |
Standard Binance status code ("000000" indicates success).
|
message |
STRING | Execution status feedback or message. |
data |
NULL / VOID | Void return payload on successful release completion. |
success |
BOOLEAN | Indicates overall request execution result. |
Workflow for releasing cryptocurrency to the buyer.
Trigger automated release of escrowed cryptocurrency once webhook notifications confirm fiat settlement.
Provide one-click "Payment Received & Release Crypto" action workflows for merchant desk operators.
Significantly lower average order completion times to rank higher on Binance P2P merchant leaderboards.
This article is part of our complete learning guide covering professional cross-exchange cryptocurrency arbitrage.
Explore the Spot Arbitrage Guide →This article is part of our complete learning guide covering Binance P2P automation, merchant tools, and automated trading.
Explore the Binance P2P Automation Guide →