How Do Binance Sub-Accounts and the Main Account Manage Funds? Sub-Account Setup Rules

Here's the direct answer to the title: Binance Sub-Accounts are a multi-account management feature only available to users at VIP 1 and above, as well as institutional and enterprise users — regular individual users don't have access to this feature. Once sub-accounts are enabled, the main account can create multiple independent sub-accounts (each with its own email, independent KYC, independent balance, and independent trading history). Funds can be transferred instantly and free of charge between the main account and its sub-accounts. The main account administrator can view every sub-account's transactions and balances, but by default, sub-accounts cannot see each other. This mechanism is a fund-management tool designed for teams, market makers, and institutional investors.

Most of our hands-on work at BabianLab is done from a personal-account perspective — we only got our hands on the sub-account feature in 2024, when we opened a VIP 1 test account. This note lays out the requirements for opening a sub-account, its relationship with the main account, the logic of fund management, and the pitfalls that are easy to fall into. If you've just registered on the Binance Official Site and haven't reached VIP 1 yet, treat this as background reading; if you're an institutional user evaluating whether to open sub-accounts, the second section has the full setup process.

The Core Relationship Between Sub-Accounts and the Main Account

The One-Line Definition

The Main Account (Master) is the owner of the funds and the management rights; the Sub-Account is a subordinate trading account under the main account — it trades independently and has its own KYC, but ownership belongs to the main account.

5 Key Relationships

Dimension	Main Account	Sub-Account
Who can create one	VIP 1+ / enterprise users	Created by the main account, no independent registration entry point
Login method	Its own email + password	Sub-account has its own independent email + password
KYC	Main account has its own independent KYC	Sub-account has its own independent KYC (depends on type)
Fund ownership	Managed by the main account	Nominally held under the sub-account, but ownership actually belongs to the main account
Trading permissions	Set up by the main account	Assigned by the main account (Spot/Futures/Margin toggles, etc.)
Transfers	Can transfer to any sub-account	By default can only transfer back to the main account, cannot transfer directly to another sub-account
Viewing rights	Can see all sub-accounts	Can only see itself
Closing an account	The main account can close any sub-account individually	A sub-account cannot close itself

Requirements for Opening a Sub-Account

Requirement 1: Reach VIP 1 Level

The threshold for VIP 1 is "spot trading volume of 1,000,000 USDT equivalent over the past 30 days, OR BNB balance ≥ 50 BNB" (either one qualifies, as of the 2026 standard). Neither of these thresholds is low for an individual user — an average daily trading volume of 33,000 USDT requires fairly substantial capital turnover.

Regular registered users default to the "Regular" tier and have no access to the sub-account feature. VIP 1 progress can be tracked under "Account Center → VIP Upgrade."

Requirement 2: Institutional User Verification

If you're an institution (a company, fund, or market maker), you can go through the "Institutional Account" process — submitting company registration documents, a UBO (Ultimate Beneficial Owner) declaration, and an AML (anti-money laundering) questionnaire. Once approved, the sub-account feature is enabled directly, without needing to reach the VIP 1 trading volume. The institutional setup process generally takes 5-15 business days.

Requirement 3: Enterprise Account

An Enterprise Account overlaps with an Institutional Account but isn't identical. An Enterprise Account is better suited to scenarios like "a company's finance team using USDT for receipts and payments," and has more relaxed limits on the number of sub-accounts (up to 200), but comes with compliance audit requirements.

Fund Management Between the Main Account and Sub-Accounts

Transfer Rules

Transfer Direction	Allowed?	Approval Needed?
Main account → sub-account	Allowed	Not needed
Sub-account → main account	Allowed	Not needed
Sub-account A → sub-account B	Allowed (only via the main account)	Needs to be triggered from the main account's backend
Sub-account A transferring directly to sub-account B on its own	Not allowed	—

Sub-accounts cannot transfer directly to each other; it must go through the main account as a relay: Sub-account A → main account → Sub-account B. This is Binance's compliance design, ensuring every cross-sub-account fund movement can be audited by the main account.

Transfer Fees

Transfers between the main account and sub-accounts are completely free and instant, same as transfers between regular sub-accounts. Binance doesn't distinguish fee rates between "8 internal sub-accounts" and "main-to-sub transfers" — they're all 0.

Transfer Limits

There's no upper limit on amounts for main-to-sub-account transfers. We tested a single transfer of 10,000 USDT with no issues, and 100,000 with no issues either (on our VIP 1 test main account).

Transfer Entry Point

After logging into the main account, go to Wallet → Sub-Accounts → select a sub-account → Transfer. In the popup, choose "from main account to sub-account" or the reverse, select the coin and amount, and confirm.

After logging into a sub-account, go to Wallet → Transfer, and the destination account dropdown will only show the main account as an option — you can't select any other sub-account.

The Sub-Account Setup Process (From the Main Account's Perspective)

Step 1: Go to Sub-Account Management

Log in to the main account on the Binance Official Site, then avatar in the top right → Sub-Accounts (this menu item only shows up once you're VIP 1 or above).

Step 2: Create a Sub-Account

Click "Create Sub-Account," and fill in the sub-account's email (must be a new one that hasn't already been registered with Binance), a nickname, and a password.

Choose a sub-account type:

• Standard Sub-Account: the default type, with independent KYC
• Managed Sub-Account: used for market makers and institutional partners to custody funds — the main account can act on behalf of the sub-account for API and trading

Step 3: Set Sub-Account Permissions

By default, all trading permissions are turned off after a sub-account is created. The main account administrator has to enable them one by one:

• Spot trading: yes/no
• USDⓈ-M Futures: yes/no
• COIN-M Futures: yes/no
• Margin trading: yes/no
• C2C: yes/no
• Withdrawals: yes/no (off by default)
• API creation: yes/no

Step 4: Sub-Account KYC

Once the sub-account's email receives an activation link, the sub-account user logs in on their own device and submits their KYC materials independently. The sub-account can only trade normally once its KYC is approved. Sub-account KYC has no effect on the main account.

Step 5: Transfer in Initial Funds

Using the main account's backend "Sub-Accounts → Transfer" entry point, transfer in USDT or another coin, and the sub-account can start trading.

What the Main Account Can See About Sub-Accounts

What It Can See

The main account administrator can view, for each sub-account:

• Real-time balances (across Futures/Spot/Earn for every sub-account)
• Complete trading history (Spot orders, Futures positions, withdrawal records)
• Login devices and IPs
• API creation and usage
• Deposit and withdrawal records (including destination addresses)
• KYC status

What It Cannot See

• The sub-account's login password (can only reset it, not view it)
• The sub-account's 2FA secret key (it's independent)
• The sub-account's anti-phishing code (it's independent)

What a Sub-Account Can See

After a sub-account user logs into their own account, they cannot see any information about the main account or other sub-accounts at all. The sub-account UI looks almost identical to a regular account, except a "Sub-Account" label appears under the avatar, and the transfer destination list only shows "Main Account."

Sub-Account Limitations and Unavailable Features

Limitation 1: Different Deposit Addresses

Every sub-account has its own independent on-chain deposit address (different from the main account's USDT deposit address). This is a compliance requirement — the deposit address for each KYC entity must be kept separate.

Limitation 2: Withdrawals Off by Default

The sub-account's withdrawal entry point is disabled by default, and the main account administrator has to enable it on the permissions page. This is anti-abuse design — even if a sub-account password leaks, funds can't be withdrawn unless the withdrawal permission has been turned on.

Limitation 3: API Key Limits

Each sub-account can create up to 30 API Keys.

Limitation 4: Cannot Participate in Certain Activities

Sub-accounts generally cannot participate in activities like Binance Launchpad, Launchpool, or new coin subscriptions (to prevent using multiple accounts to farm allocations) — only the main account can.

Limitation 5: Fee Rates Are Not Independent

A sub-account's Spot/Futures fee rates follow the main account's — you cannot set a separate fee rate for a sub-account.

Sub-Accounts vs Multiple Independent Main Accounts

A lot of people mistakenly think "I can just register multiple Binance accounts to manage different pools of funds." Binance's rules are:

Dimension	Sub-Account	Multiple Independent Main Accounts
Same person opening multiple	Allowed (VIP 1+)	Not allowed (violates the ToS)
Shared use	Used by teams/institutions	One person, one account
Risk	Compliant	May get frozen
Fund movement	Free, instant transfers between main and sub	Must use Pay or an on-chain transfer

Binance's Terms of Service explicitly prohibit individual users from opening multiple main accounts ("One Account Per Person"). If the system detects the same identity information (KYC, device fingerprint, IP) tied to multiple accounts, one of them will be frozen — see How Do You Unfreeze a Frozen Binance Account?.

Common Use Cases for Sub-Accounts

Case 1: Team Risk Isolation

Sub-account A runs high-frequency spot trading, sub-account B runs leveraged futures. Even if B gets liquidated, it won't affect A's funds. The main account keeps all "cold funds" out of trading entirely.

Case 2: Strategy P&L Accounting

Different strategies are placed in different sub-accounts, so at the end of the month the main account administrator can clearly see "strategy A's sub-account is up 5%, strategy B's sub-account is down 2%," making performance attribution easy.

Case 3: API Isolation

Each sub-account has its own independent API Key — a leak on one doesn't affect the others. The main account's API can optionally be set to read-only mode, "can query all sub-accounts but cannot trade."

Case 4: Splitting Across Multiple Markets

Sub-account A trades only Spot BTC/ETH, sub-account B trades only SOL futures, sub-account C trades only altcoins. Each strategy team logs into its own sub-account, without interfering with each other.

Can Regular Users Simulate a Sub-Account?

If you're a regular user who hasn't reached VIP 1 yet but still want to manage "fund separation," there are a few alternatives:

Alternative 1: Use Spot + Futures + Funding as Psychological Separation

Put money for different purposes into different wallets (not the sub-account feature — the 8 built-in accounts inside the Binance wallet). For example, "idle cash goes into Earn flexible," "short-term money stays in Spot," "futures margin goes into USDⓈ-M Futures." This is only psychological separation — ownership is still all under your one UID.

Alternative 2: Use API Keys for Strategy Separation

The main account creates multiple API Keys, each restricted to different trading pairs and permissions, and assigns them to different strategy programs. This was the common practice institutional investors used before sub-accounts existed.

Alternative 3: Wait for VIP 1

If your trading volume is growing quickly, VIP 1 isn't out of reach. An average daily trading volume of 33,000 USDT is something a mid-sized retail trader could realistically hit within 1-2 years.

5 Best Practices for a Main Account Managing Sub-Accounts

Practice 1: Audit Sub-Account Balances Regularly

The main account administrator should log into the backend weekly to check all sub-account balances against expected allocations. If any sub-account's balance changes significantly, check the trading history to confirm whether it was a strategy action or something abnormal.

Practice 2: Keep Sub-Account Withdrawal Permissions Off by Default

Only temporarily enable a sub-account's withdrawal permission when you need to do a batch withdrawal, and turn it back off immediately after.

Practice 3: Force 2FA On for Sub-Accounts

The main account should require the sub-account user to bind 2FA immediately after creating the sub-account (the mandatory toggle is on the sub-account management page). See Setting Up Google Authenticator for 2FA.

Practice 4: Restrict Sub-Account API IP Whitelists

Set an IP whitelist on every sub-account's API Key, only allowing calls from specific server IPs. This prevents abuse if an API Key leaks.

Practice 5: Sweep Large Balances at End of Day

The main account automatically sweeps all sub-accounts' excess USDT into the main account's "cold funds account" at 23:50 UTC every day, then redistributes it at 00:10 UTC the next day. This cycle reduces the funds exposure sitting in sub-accounts.

Closing a Sub-Account

A sub-account can be closed individually:

1. Log into the main account → Sub-Account Management
2. Select the sub-account → "Freeze Sub-Account" (temporary suspension) or "Delete Sub-Account" (permanent closure)
3. Before deleting, the sub-account's balance must be transferred back to the main account (you cannot delete it while it still has a balance)

A frozen sub-account's user cannot log in, but the data is retained. Once a sub-account is deleted, that email can never be used to register with Binance again.

FAQ

Q: When can a regular registered user open a sub-account? A: Once they reach VIP 1 (spot trading volume of 1,000,000 USDT equivalent over the past 30 days, or a BNB balance ≥ 50 BNB).

Q: Can a sub-account withdraw independently? A: Yes, but only if the main account has enabled the "Withdrawal" toggle on the sub-account's permissions page, and the sub-account completes its own independent 2FA verification.

Q: Does a sub-account need to redo KYC? A: A standard sub-account needs its own independent KYC (using the sub-account user's own ID documents). A managed sub-account can have its KYC handled by the main account on its behalf.

Q: Can the main account view a sub-account's private keys? A: No Binance account exposes private keys at all (Binance itself custodies the private keys for all hot wallets), so this question doesn't really apply. What the main account can see is metadata like the sub-account's "deposit address," "2FA status," and "trading history."

Q: Can a sub-account open another sub-account under itself? A: No — Binance's sub-account system is a single-layer structure; a sub-account cannot open further sub-accounts beneath it.

Q: If the main account gets frozen, are sub-accounts affected? A: Yes — freezing the main account causes all its sub-accounts to be frozen too (funds cannot be moved out). So the main account's security settings should be set to maximum — 2FA, whitelist, and anti-phishing code should all be turned on.

Q: Can sub-accounts be managed from the Official Binance App? A: Yes — the App's settings page has a "Sub-Accounts" entry point where you can create, transfer, and view sub-accounts, but some advanced features (like API permission management) can only be done on PC.