BINANCE SAPI · C2C

Check If Can Release Digital Asset API

Pre-validate two-factor authentication (2FA) verification codes and seller authorization requirements before releasing escrowed cryptocurrency to the buyer.

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

Overview

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.

01

Request Parameters

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.
!
Irreversible Escrow Release

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.

02

Request Example

Example POST request using cURL to pre-validate Google Authenticator 2FA.

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

Response

Example response returned on successful verification.

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

Response Fields

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.
04

How It Works

Workflow for validating asset release permissions.

01 Collect 2FA Obtain TOTP, SMS, Email, or FIDO2 token from user.
02 Submit Verification POST credentials to /checkIfCanReleaseCoin.
03 Evaluate Data Ensure data: true is returned in response.
04 Execute Release Proceed to call final release endpoint to deliver crypto.

Common Use Cases

2FA Code Pre-Validation

Verify Google Authenticator or SMS codes before triggering irreversible escrow release calls.

Automated Payout Safeguards

Ensure trading bots validate security credentials before attempting programmatic coin delivery.

UI Error Handling

Provide immediate visual feedback in merchant interfaces if an entered 2FA passcode is incorrect or expired.



💬
Telegram WhatsApp