Binance sub-account creation is located in the main account’s [Dashboard] - [Sub-Accounts]. The main account must have completed identity verification and enabled two-factor authentication (2FA). Regular users can create up to 5 sub-accounts; higher VIP levels get more quotas.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Step 1: Access the Creation Entry
Log in to the main account in a desktop browser, click the profile icon in the top-right corner to go to [Dashboard], find the [Sub-Accounts] tab, then click [Account Management].
Step 2: Choose the Creation Type
Click + Create Sub-Account. The system offers two options:
Create with Email: Enter a valid email address that has never been used to register a Binance account, set a password, then verify via that email. Once created, this sub-account can log in normally with the email and password.
Create with Virtual Email: No real email needed. Just give the sub-account a name, and Binance will generate a virtual email address automatically. This virtual email cannot be used to log in; it only works with API Keys for programmatic operations.
After verification or creation, the sub-account will appear in the management list, each with a unique UID.
High Risk: The sub-account and main account share the same identity verification. If the sub-account engages in rule violations (such as money laundering, market manipulation), the main account will bear joint liability and may be frozen or closed. When granting sub-account access to others, always confirm their intended use.
Step 3: Configure Sub-Account Permissions & API
After creating a sub-account, permissions are controlled at two levels:
Functional Permissions: The main account can enable features like futures trading and options trading for sub-accounts in the management interface. The corresponding API can be finely authorized — when creating an API Key, you can check permissions for spot/margin trading, futures, universal transfer, European options, etc. All are disabled by default; enable as needed.
IP Whitelist: When creating or modifying an API Key, you can set IP restriction status: 1=unrestricted, 2=restrict to a list of IPs, 3=third-party IP restriction. If you choose status 2, you need to enter the allowed IP address list.
Step 4: Fund Transfers
Sub-accounts do not have independent external deposit addresses; the main account must transfer funds to them.
Main to Sub-Account Transfer: Use the main account’s API Key, call /sapi/v1/sub-account/universalTransfer, which supports transferring from main account funds to sub-account spot, futures, margin wallets.
Sub to Main Transfer: Use the sub-account’s own API Key, call /sapi/v1/sub-account/transfer/subToMaster.
Sub to Sub Transfer: Use the sub-account’s API Key, call /sapi/v1/sub-account/transfer/subToSub, specifying the recipient sub-account email and amount.
Important: Sub-accounts cannot directly withdraw to external addresses; all withdrawals must be done via the main account.
Common Failure Reasons
Email already in use: The email entered must not already be registered as a Binance main account; otherwise it will fail.
IP restriction blocks: If the main account has IP whitelist enabled and the API call’s IP is not on the allowed list, it will be rejected.
Permission not enabled: If the API Key does not have universal transfer permission, transfer requests will fail.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
After the Operation
Verification: In the sub-account management page, confirm the new account appears in the list. Then try transferring a small amount (e.g., 1 USDT) to the sub-account to verify it arrives.
Next Steps: After creating the sub-account, immediately record the sub-account’s API Secret on the API management page (it is shown only once). Also check that each API Key’s enabled permissions do not exceed actual needs — for example, a sub-account only doing spot trading should not have futures and options permissions enabled.
