BINANCE SAPI · C2C

Verified Additional KYC API

Verify supplemental counterparty KYC credentials, identity verification levels, and risk compliance status associated with a specific peer-to-peer (C2C) trade order.

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

Overview

This endpoint enables verified Binance C2C (P2P) merchants and high-volume institutional desks to validate whether a counterparty has satisfied specific supplemental KYC (Know Your Customer) requirements on an active order. It checks custom identity verification proofs, enhanced tier certifications, and anti-fraud identity checks attached to the transaction.

Automated compliance pipelines and risk monitoring engines invoke this endpoint to confirm that counterparties meet strict local financial regulations before accepting or releasing fiat funds.

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, WEB_MOBILE).
orderNumber Body STRING Required Unique order number identifier to verify additional KYC status 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.
i
Compliance Automation

Use this verification check to automatically screen counterparties against your compliance whitelist before triggering bank transfers or accepting large fiat deposits.

02

Request Example

Example POST request using cURL to check additional KYC verification.

cURL BASH
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/verifiedAdditionalKyc' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
  "orderNumber": "202608161234567890"
}'
03

Response

Example response returned on successful verification check.

RESPONSE 200 OK
{
    "code": "000000",
    "message": "success",
    "data": {
        "orderNumber": "202608161234567890",
        "verified": true,
        "kycLevel": "VERIFIED_PLUS",
        "realName": "John Doe",
        "country": "US"
    },
    "success": true
}

Response Fields

Field Type Description
code STRING Standard Binance status code ("000000" indicates success).
message STRING Status description or response feedback message.
data.orderNumber STRING Unique identifier of the checked C2C trade order.
data.verified BOOLEAN Indicates whether the counterparty has satisfied required additional KYC checks (true or false).
data.kycLevel STRING Verified identity tier level of the counterparty (e.g., VERIFIED, VERIFIED_PLUS, ENTERPRISE).
data.realName STRING Legal identity name verified under the account's KYC documents.
data.country STRING Registered country / jurisdiction code of the verified counterparty.
success BOOLEAN Indicates overall request execution result.
04

How It Works

Workflow for verifying counterparty additional KYC.

01 Order Matched Obtain orderNumber from active trade match event.
02 Send Verification Request POST orderNumber to /verifiedAdditionalKyc endpoint.
03 Evaluate Compliance Verify real name matching, verified tier, and country code.
04 Proceed or Hold Release payment instructions or prompt operator intervention.

Common Use Cases

Third-Party Payment Prevention

Ensure the verified KYC real name matches the sending bank account holder's name to prevent third-party payment fraud.

Jurisdictional Compliance

Verify counterparty registered country codes to enforce strict local AML regulatory standards automatically.

High-Tier Order Authorization

Require VERIFIED_PLUS tier verification before processing large-volume merchant trades.



💬
Telegram WhatsApp