Skip to main content

FAQ

What is KYC Status Notification URL?​

A POST webhook notify function that provides call backs when KYC information changes.
Retry Policy : Retry at 3rd, 5th, and 10th minute

Where can I get BizEntityKey?​

You can ask Binance to provide BizEntityKey for you.

What is entityCustomerId?​

A unique user id in the Exchange Link system.
Client/user needs to provide this to Binance to link accounts

How to populate the "language" field?​

Language code
For Example: en

Other possible options:
{ "en": "English", "ar": "العربية", "ar-BH": "العربية (البحرين)", "bg": "български", "bn": "বাংলা", "cs": "Čeština", "de": "Deutsch", "de-CH": "Deutsch (Schweiz)", "en-AU": "English (Australia)", "en-BH": "English (Bahrain)", "en-GB": "English (Britain)", "en-KZ": "English (Kazakhstan)", "en-NZ": "English (New Zealand)", "es": "Español (Internacional)", "es-AR": "Español (Argentina)", "es-LA": "Español (Latinoamérica)", "fr": "Français", "he": "עברית", "id": "Bahasa Indonesia", "en-IN": "English (India)", "it": "Italiano", "kk-KZ": "Қазақша (Қазақстан)", "ko": "한국어", "kz": "Қазақша", "lv": "latviešu valoda", "ng": "English (Nigeria)", "nl": "Nederlands", "ph": "Filipino", "pl": "Polski", "pt": "Português", "pt-BR": "Português (Brasil)", "pt-PT": "Português (Portugal)", "ro": "Română", "ru": "Русский", "ru-KZ": "Русский (Казахстан)", "sv": "svenska", "th": "ไทย", "tr": "Türkçe", "uk-UA": "Українська", "vi": "Tiếng Việt", "zh-CN": "简体中文", "zh-TC": "繁體中文" }

About Sharing Data?​

For KYC records originally initiated through KYC url, you cannot use KYC Sharing even if the KYC record is reset.

For KYC records originally initiated through KYC Sharing, you can reset and generate KYC url to redo it.

Misplaced / Uncredited Deposits?​

What if my user deposited into a retired wallet address, or into a sub-account that has not completed KYC yet?​

Since the implementation of KYC restrictions, newly created sub accounts will not be able to create an API key and retrieve a deposit address without first completing KYC, hence this scenario would not be applicable.

For older sub-accounts where users might have saved a copy of the wallet address and did not complete KYC, the deposit will be rejected. In order to retrieve the deposit, please use the SAPI asset recovery API to submit an appeal request. If you do not have the SAPI asset recovery API documentation, please approach our business team or contact our Binance Link team.

Please note that the appeal will be refunded to the source address, and could take up to 30 days to process. Please manage your user accordingly.

Overview of Restrictions​

1.Service Restrictions​

Sub-Account Restrictions

ServicesRestrictions
DepositsRestricted
WithdrawalsAllowed, unless otherwise specified
Spot TradingRestricted. Cannot place new orders and all existing spot orders will be canceled
Futures TradingRestricted. Cannot place new orders, but can reduce existing positions
Margin TradingRestricted. Cannot place new orders, but can reduce existing positions

2.API Restrictions​

Not allowed to create or permission API keys on a non-KYC-ed sub account Common APIs affected:

  • POST /sapi/v1/broker/subAccountApi
  • POST /sapi/v1/broker/subAccount/futures
  • POST /sapi/v1/broker/subAccountApi/permission

Not allowed to receive deposits into a non-KYC-ed sub account Common APIs affected:

  • POST /sapi/v1/broker/subAccountApi/permission/universalTransfer
  • POST /sapi/v1/broker/transfer
  • POST /sapi/v1/broker/transfer/futures
  • POST /sapi/v1/broker/universalTransfer

Note:

  • Non-KYC-ed Sub account can withdraw to Master account
  • Non-KYC-ed Sub account can withdraw to a sub account that is KYC-ed.
  • Non-KYC-ed Sub account CANNOT withdraw to another non-KYC-ed sub account
  • Master account CANNOT deposit into a non-KYC-ed sub account