Pre-validate two-factor authentication (2FA) verification codes and seller authorization requirements before releasing escrowed cryptocurrency to the buyer.
/sapi/v1/c2c/orderMatch/checkIfCanReleaseCoin
This endpoint enables a seller or automated payout bot to pre-verify the multi-factor authentication (MFA/2FA) credentials associated with releasing crypto from Binance escrow. It checks whether authentication parameters (e.g., Google Authenticator, SMS, Email OTP, FIDO2 passkeys, or YubiKey tokens) are valid for the given order prior to final fund release.
Integrating this pre-check inside automated release workflows ensures verification credentials are confirmed before executing the irreversible asset release transaction.
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).
|
orderNumber |
Body | STRING | Required | Unique C2C order number to evaluate for asset release. |
authType |
Body | STRING | Optional |
Authentication mechanism type (e.g., FIDO2, GOOGLE, SMS, EMAIL, YUBIKEY).
|
code |
Body | STRING | Optional | Generic verification passcode string. |
confirmPaidType |
Body | STRING | Optional | Payment confirmation confirmation type identifier. |
googleVerifyCode |
Body | STRING | Optional | 6-digit Google Authenticator TOTP code. |
mobileVerifyCode |
Body | STRING | Optional | SMS mobile verification code. |
emailVerifyCode |
Body | STRING | Optional | Email verification code sent to the registered email address. |
yubikeyVerifyCode |
Body | STRING | Optional | YubiKey hardware security OTP or signed token. |
payId |
Body | LONG | Optional | Payment configuration identifier selected by the seller. |
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. |
Releasing digital assets from escrow cannot be undone. Only proceed with release flows once receipt of full payment has been independently verified in your banking or wallet records.
Example POST request using cURL to pre-validate Google Authenticator 2FA.
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/checkIfCanReleaseCoin' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
"orderNumber": "202608161234567890",
"authType": "GOOGLE",
"googleVerifyCode": "123456"
}'
Example response returned on successful verification.
{
"code": "000000",
"message": "success",
"data": true,
"success": true
}
| Field | Type | Description |
|---|---|---|
code |
STRING |
Standard Binance status code ("000000" indicates success).
|
message |
STRING | Response execution feedback or status description. |
data |
BOOLEAN |
Returns true if release verification passes; returns false otherwise.
|
success |
BOOLEAN | Indicates overall request execution result. |
Workflow for validating asset release permissions.
data: true is returned in response.
Verify Google Authenticator or SMS codes before triggering irreversible escrow release calls.
Ensure trading bots validate security credentials before attempting programmatic coin delivery.
Provide immediate visual feedback in merchant interfaces if an entered 2FA passcode is incorrect or expired.
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 →