Binance API / SAPI / C2C
BINANCE SAPI · C2C

Release Crypto API

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.

ENDPOINT
POST /sapi/v1/c2c/orderMatch/releaseCoin
Authentication USER_DATA / SIGNED
API Group C2C / Order Match
Method POST
Response JSON

Overview

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

01

Request Parameters

Parameters accepted in Body and HTTP Headers.

ParameterInTypeRequiredDescription
clientTypeHeaderSTRINGRequiredClient Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
orderNumberBodySTRINGRequiredUnique C2C order number to release cryptocurrency for.
authTypeBodySTRINGOptionalTwo-factor authentication mechanism (e.g., FIDO2, GOOGLE, SMS, EMAIL, YUBIKEY).
codeBodySTRINGOptionalGeneric verification code string.
googleVerifyCodeBodySTRINGOptional6-digit Google Authenticator TOTP token.
mobileVerifyCodeBodySTRINGOptionalSMS text verification code sent to the registered mobile number.
emailVerifyCodeBodySTRINGOptionalEmail verification code sent to the account email.
yubikeyVerifyCodeBodySTRINGOptionalHardware security key token string.
payIdBodyLONGOptionalPayment configuration identifier selected by the seller.
confirmPaidTypeBodySTRINGOptionalConfirmation type parameter.
x-gray-envHeaderSTRINGOptionalEnvironment flag identifier used for internal gray/stage testing.
x-trace-idHeaderSTRINGOptionalCustom client trace ID for request lifecycle tracking and debugging.
x-user-idHeaderSTRINGOptionalTarget user identifier for context validation.
!

Irreversible Action Warning

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.

02

Request Example

Example POST request using cURL with Google Authenticator verification.

cURL BASH
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"
}'

03

Response

Example response returned on successful crypto asset release.

RESPONSE 200 OK
{
    "code": "000000",
    "message": "success",
    "data": null,
    "success": true
}

Response Fields

FieldTypeDescription
codeSTRINGStandard Binance status code ("000000" indicates success).
messageSTRINGExecution status feedback or message.
dataNULL / VOIDVoid return payload on successful release completion.
successBOOLEANIndicates overall request execution result.

04

How It Works

Workflow for releasing cryptocurrency to the buyer.

01 Verify Payment Confirm receipt of full fiat amount in bank or wallet.
 
02 Generate 2FA Code Obtain TOTP or hardware security verification token.
 
03 Send POST Request POST payload to /sapi/v1/c2c/orderMatch/releaseCoin.
 
04 Escrow Released Crypto transfers to buyer; order transitions to COMPLETED.

Common Use Cases

Automated Payout Release Bots

Trigger automated release of escrowed cryptocurrency once webhook notifications confirm fiat settlement.

Merchant Terminal Integration

Provide one-click "Payment Received & Release Crypto" action workflows for merchant desk operators.

High-Speed Escrow Turnaround

Significantly lower average order completion times to rank higher on Binance P2P merchant leaderboards.

💬
Telegram WhatsApp