KuCoin Sub-Accounts Guide: Strategy Isolation, Permissions, Asset Transfers and Security Controls

KuCoin sub-accounts let one master account divide trading activity into separately managed environments. A user can assign capital to a strategy, restrict Spot, Margin or Futures access, create a dedicated API key, review transfers and freeze a problem account without treating every trade as part of one undifferentiated balance. That separation improves organization, but it is not a guarantee against loss: permissions, margin mode, API security and master-account control still determine how far an incident can spread.

Last reviewed: October 18, 2026. KuCoin eligibility, sub-account limits, permissions, account-switching behavior, Unified Trading Account access, API rules and interface labels can change. Confirm the live controls shown in your authenticated account. This independent guide is educational, is not affiliated with KuCoin and is not financial, legal, tax or investment advice.

What this guide covers

1. The difference between a master account, sub-account and internal account type.
2. How sub-accounts separate strategies, permissions, records and API access.
3. How master-to-sub, sub-to-master and sub-to-sub transfers work.
4. How account switching, verification methods and login history affect security.
5. How Classic and Unified Trading Account modes can coexist.
6. When to freeze, reactivate or permanently delete a sub-account.
7. How to troubleshoot missing balances, wrong profiles and unavailable permissions.

What is a KuCoin sub-account?

A sub-account is a child trading profile managed beneath a KuCoin master account. It can have its own name, login password, product permissions, account balances, orders, positions, history and API credentials. The master account retains administrative capabilities defined by KuCoin, including creating and managing sub-accounts and moving assets between them.

This structure is designed for operational separation. One sub-account might hold a Spot strategy, another a Futures strategy and a third an automated system. Their results become easier to attribute because orders and balances are not all recorded under one profile.

Master account, sub-account and account type are different

KuCoin uses the word “account” at more than one level. Confusing those levels causes incorrect transfers and misleading risk assumptions.

Moving USDT from Funding to Trading inside one profile does not create a sub-account. Creating a sub-account does not automatically make every position isolated. Each layer must be configured deliberately.

When a sub-account is useful

• Strategy separation: keep unrelated rules, orders and PnL apart.
• Capital budgeting: allocate only a defined amount to an experiment.
• API automation: give a bot a dedicated key and trading environment.
• Product separation: avoid mixing long-term Spot activity with leveraged Futures.
• Operational review: attribute logins, transfers and trades to one workflow.
• Team processes: divide approved responsibilities without sharing the master login.

A sub-account can reduce the operational blast radius of a mistake only when capital and permissions are actually limited. Funding every child profile from the same large shared risk pool or granting unnecessary API rights defeats much of the purpose.

When an internal account transfer is enough

A separate sub-account may be unnecessary when one person simply needs to move assets from Funding to Trading for an ordinary Spot order. KuCoin’s internal account types already divide balances by product purpose. Extra profiles add passwords, verification settings, records and administrative work.

Create a sub-account because a boundary is needed—not because the word “separate” sounds safer. Write down the intended boundary first: strategy, capital ceiling, product permission, API integration or team responsibility.

Design the structure before creating it

A useful plan defines the purpose, permitted products, maximum capital, operator, review schedule and exit conditions for every child profile. Avoid vague names such as Test2 or NewBot. Use a consistent internal convention that communicates purpose without exposing sensitive strategy details.

Standard and custodial sub-accounts

KuCoin documentation may display Standard and Custodial sub-account choices depending on account eligibility and platform context. An ordinary user should not select a type merely because it appears more professional. Review the current description, access model, responsibilities and applicable agreements shown during creation.

This guide focuses on the standard master–sub workflow. Institutional or custodial arrangements may involve additional roles, account managers and contractual controls.

How to create a KuCoin sub-account

1. Navigate directly to the official KuCoin website and sign in to the intended master account.
2. Open the profile menu and select the current Sub-Account area.
3. Select Create Sub-Account.
4. Choose the appropriate account type shown for your eligibility.
5. Enter a unique sub-account name, login password and useful internal remark.
6. Enable only the Spot, Margin or Futures permissions required by its written purpose.
7. Review every setting and confirm through the official verification flow.
8. Secure verification methods before transferring meaningful assets.

KuCoin’s current management guide specifies formatting requirements for the sub-account name and password. Treat the live creation form as authoritative because these rules can change.

Names and remarks should support an audit

A good name helps distinguish the active profile before an order or API change. A remark can document the owner, strategy or review date. Do not place API secrets, passwords, client personal data or a complete trading thesis in the label.

Maintain a separate non-secret inventory containing each profile’s purpose, creation date, allowed products, integration owner and retirement status. That prevents abandoned sub-accounts from becoming invisible access paths.

Use a unique login password

Do not reuse the master password, email password or another sub-account password. Reuse turns one credential leak into access across several environments. Generate a unique password with a reputable password manager and protect the master account with its strongest available authentication.

The KuCoin trading password is a different credential with a different purpose. Do not store it in a label, API remark or bot configuration file unless the integration explicitly requires a secure mechanism and the current KuCoin workflow supports it.

Assign the minimum trading permissions

KuCoin can present Spot, Margin and Futures permissions during sub-account management. Grant only the products needed for the stated strategy. A Spot accumulation account does not need Futures permission merely because it might be useful later.

Permission isolation limits which products can be used; it does not choose safe trades. A permitted Futures strategy can still lose its complete allocated margin.

Secure verification methods before funding

KuCoin’s management interface can allow the master account to link or modify Google Authenticator, email, phone and trading-password verification for a child profile. Review what is inherited, what is unique and who controls each recovery channel.

Do not route every sub-account through a shared inbox that many people can access. Protect the master email first because master-account recovery and administration can override carefully separated child workflows.

Master-to-sub asset transfers

The master account can allocate funds to a sub-account through KuCoin’s internal transfer controls. This is normally a book-entry movement inside the exchange rather than an onchain transaction. It should not require a blockchain address or network selection.

Before confirming, verify the source profile, destination sub-account, internal account type, asset and amount. A correct sub-account with the wrong internal destination can make the balance appear unavailable for the intended product.

Sub-to-master and sub-to-sub transfers

KuCoin documentation describes master-level controls for transfers from a sub-account back to the master and between sub-accounts. A user logged directly into a child profile may be limited to transfers among its own internal account types rather than transfers across the master–sub hierarchy.

Use the master view for treasury allocation. Record the reason for material movements so strategy performance is not confused with external profit or loss. A transfer into a strategy is capital contribution, not trading return.

A sub-account does not normally withdraw independently

KuCoin’s current guide states that sub-accounts cannot perform direct withdrawals and that the master account manages movement back through the hierarchy. This is a useful control, but users should confirm current rules for their account and entity.

Do not attempt to bypass a missing withdrawal button by sending credentials to a third-party “assistant.” Move eligible funds internally through official controls and perform the permitted withdrawal from the correct master-account source.

Internal transfer versus blockchain withdrawal

Check transfer history, not only balances

The master account can review master–sub transfer history in the sub-account management area. Use it to reconcile opening capital, later additions, returned funds and unexplained movements. A balance alone cannot distinguish trading loss from an administrative transfer.

Export or preserve records according to accounting needs before deleting a profile. Tax treatment differs by jurisdiction, but internal transfers should not be mistaken for external disposals merely because they moved between account views.

Account Switching is convenience, not identity proof

KuCoin’s Account Switching function can let an authenticated user move between linked master and sub-account contexts without a completely separate login. This improves workflow but increases the importance of checking the active profile before every order, transfer or API action.

Display a clear naming convention and pause after switching. Verify the account banner, available balance and recent activity. A correct trade in the wrong profile can undermine both strategy isolation and accounting.

Control whether sub-accounts can switch contexts

KuCoin’s sub-account management guide describes a setting that can permit or prevent switching among profiles under a master account. Enable it only when the operator genuinely needs that reach. Convenience should not silently broaden access.

For a bot-only or narrowly delegated profile, reduced switching capability can support least privilege. Document why the setting is enabled and review it when responsibilities change.

Review login history after every access change

Use the master account’s transfer and login history areas to identify unfamiliar access, unexpected times or changes inconsistent with the workflow. Compare entries with authorized operators and automation schedules.

If activity is suspicious, do not continue trading to “test” control. Freeze the affected profile, secure the master account, revoke relevant API keys and contact KuCoin through the official support route.

Dedicated API keys preserve the boundary

An automated strategy should use an API key created for its own sub-account, not a master key shared across unrelated tools. KuCoin’s UTA documentation notes that master-account API keys are not substitutes for sub-account trading keys in the relevant workflow.

Create one key per integration where possible. This makes permission review, rotation and revocation more precise. A tax tool may need read access; a Spot bot may need order permissions; neither automatically needs Futures or transfer capabilities.

Apply least privilege to every API key

1. Identify the exact endpoints and products the integration requires.
2. Create the key inside the intended sub-account.
3. Enable only required general/read, Spot, Margin, Futures or Unified permissions.
4. Bind known static IP addresses when the workflow supports it.
5. Store the key, secret and API passphrase in a protected secret manager.
6. Test with minimal capital and a harmless order workflow.
7. Record the owner, creation date, purpose and rotation date.
8. Revoke the key when the integration is retired or suspected compromised.

API key, secret and passphrase are separate values

KuCoin API authentication can involve a public key identifier, secret and API passphrase. Do not paste them into chat, email, screenshots or public source code. KuCoin documentation indicates that secret material is shown during creation and may not be viewable later.

If a secret is lost, create a replacement rather than asking an unknown person to recover it. If it may have leaked, revoke the key immediately; editing the bot name or changing a website password does not necessarily invalidate an existing API credential.

Use an IP whitelist where practical

An IP whitelist limits where API requests can originate. It is valuable for a bot running from stable infrastructure, but only if the listed addresses are controlled and current. Do not add broad ranges simply to avoid maintaining the list.

IP restriction does not replace secret protection, least privilege or monitoring. A compromised host already on the whitelist can still use the key within its permissions.

Sub-accounts and Unified Trading Account

Eligible KuCoin users can operate Unified Trading Account mode, and official documentation describes sub-accounts as tools for strategy isolation within that environment. A master and its child profiles may not all use the same account mode.

UTA can combine supported Spot and derivatives activity into a shared collateral framework inside the selected profile. That improves capital efficiency while increasing the importance of understanding collateral haircuts, account-level equity, liabilities and liquidation rules.

Classic and UTA can coexist

KuCoin states that master and sub-accounts can be switched or activated independently in supported UTA workflows. One child may remain Classic while another uses Unified Account. Never infer a profile’s mode from the master account alone.

Before transferring capital or starting an API strategy, open that specific profile and verify its account mode. API keys intended for eligible Unified trading must use the required Unified option and permissions described in current documentation.

Sub-account isolation and margin isolation are not the same

A sub-account separates activity from other profiles. Within a UTA sub-account, cross-margin positions may still share eligible collateral. Isolated margin, where supported, defines a narrower position-level boundary.

Ask two questions separately: “Which profile owns this strategy?” and “Which collateral can this position consume?” Answering only the first does not reveal liquidation scope.

Capital efficiency can weaken a planned boundary

Multi-currency collateral and PnL offsets can allow several positions to support one another. That can reduce idle balances, but it also makes the risk budget harder to read. A loss in one cross-margin product may consume collateral that appeared unrelated.

If strict capital separation is the objective, evaluate whether Classic accounts or isolated margin better match the plan. Do not enable UTA solely because it is newer or more efficient.

Freeze a sub-account when control is uncertain

KuCoin provides a freeze action in sub-account management. Current documentation says freezing a sub-account cancels its orders. That makes freezing an appropriate containment step for suspicious access, a malfunctioning integration or a strategy that must be halted.

Before freezing for routine maintenance, understand how canceled orders and open positions will be handled. Freezing is not a substitute for closing leveraged exposure safely where the platform requires additional action.

Freeze versus delete

Choose freeze when investigation is incomplete. Permanent deletion can destroy convenient access to account context even if the platform retains records under legal obligations.

Checklist before deleting a sub-account

1. Close or settle every position according to product rules.
2. Cancel open orders and stop trading bots.
3. Revoke API keys and third-party integrations.
4. Move transferable assets to the intended master destination.
5. Check liabilities, interest, funding, fees and pending settlements.
6. Export trade, transfer, funding and tax records.
7. Confirm the profile is not referenced by accounting or automation.
8. Review KuCoin’s current deletion consequences and waiting periods.

Practical scenario: separate a Spot bot

Create a dedicated Spot-enabled sub-account, allocate only the intended strategy capital and create an API key with the minimum required read and Spot-order permissions. Bind the bot’s stable IP when possible. Do not grant Margin or Futures access. Set a drawdown threshold and a process for canceling orders, revoking the key and returning assets to the master.

Practical scenario: test a Futures strategy

Use a child profile with a deliberately small risk budget and Futures permission. Verify whether it is Classic or UTA, then choose the intended cross or isolated margin mode inside that profile. A separate profile limits allocated capital only when no additional funding is automatically or manually supplied after losses.

Practical scenario: an operator changes roles

Freeze or restrict the relevant profile before changing access. Rotate its login credentials and API keys, review authentication methods, switch permissions and examine recent login and transfer history. Removing a person from a chat or team document does not revoke credentials already issued.

Practical scenario: a bot behaves unexpectedly

Stop the bot at its provider, then freeze or otherwise contain the KuCoin sub-account if orders continue. Inspect active orders, positions, API permissions and key history. Do not delete evidence until transaction IDs, timestamps and configuration are preserved.

Troubleshooting: the sub-account option is unavailable

Confirm that you are using the verified KuCoin website, logged into a master account and eligible under the current regional, verification and account-tier rules. Some creation or API controls may require the web interface even when switching is available in the app.

Troubleshooting: the balance is missing after transfer

Check the active profile, asset and internal account type. Then open transfer history from the master view. A successful master-to-sub transfer may have credited Funding while the trading screen reads Trading or Unified balance.

Troubleshooting: the API can read but cannot trade

Verify that the key belongs to the correct sub-account, has the required product permission, uses the right API passphrase and satisfies its IP whitelist. For UTA, confirm that the Unified option and account mode match current KuCoin requirements. Do not broaden all permissions as the first troubleshooting step.

Troubleshooting: funds cannot return to master

Look for open orders, positions, liabilities, borrowed funds, accrued interest, bot allocations or settlement restrictions. Confirm the source internal account. Move eligible balances within the sub-account first if required, then use the official master-level transfer control.

Troubleshooting: the wrong profile placed an order

Do not create an offsetting trade automatically. Identify the order state, fees and current exposure. Cancel an unfilled order if appropriate; manage a filled position according to its actual risk. Record the mistake, then improve naming and active-account verification.

Common KuCoin sub-account mistakes

• Confusing a sub-account with Funding or Trading Account.
• Giving every profile Spot, Margin and Futures permissions.
• Reusing the master password.
• Funding a profile before configuring security.
• Using one master API key for several tools.
• Assuming Account Switching means every operator should reach every profile.
• Ignoring login and transfer history.
• Calling an internal capital transfer “profit.”
• Assuming a sub-account automatically creates isolated margin.
• Deleting a profile before exporting records and revoking integrations.

A repeatable monthly audit

1. List every active, frozen and planned-for-deletion sub-account.
2. Confirm its owner, purpose, permissions and capital ceiling.
3. Review login and master–sub transfer history.
4. Compare balances with strategy records.
5. Review open orders, positions, liabilities and margin mode.
6. Inventory every API key, permission and IP whitelist.
7. Revoke unused keys and remove obsolete access.
8. Freeze profiles whose ownership or purpose is unclear.
9. Export records before permanent retirement.

Frequently asked questions

What is the difference between a KuCoin master account and sub-account?

The master account administers the hierarchy and asset allocation. A sub-account is a separately managed trading profile with its own permissions, balances, history and possible API credentials.

Is a KuCoin sub-account the same as Trading Account?

No. Trading Account is an internal product balance. A master or sub-account can contain several internal account types.

Can a KuCoin sub-account withdraw crypto directly?

KuCoin’s current guide says sub-accounts cannot perform withdrawals directly. Assets are managed through master–sub internal transfers. Confirm the live rules for your account.

Does a sub-account protect the master from every trading loss?

No. It helps separate allocated capital and permissions, but losses can consume funds assigned to that profile. UTA and cross-margin rules also determine collateral scope inside it.

Should a bot use the master API key?

Prefer a dedicated key created for the intended sub-account with only required permissions and an IP whitelist where practical.

Can Classic and Unified sub-accounts exist together?

KuCoin documentation describes independent activation in supported workflows, allowing Classic and UTA modes within one master–sub structure. Verify each profile’s actual mode.

What happens when a KuCoin sub-account is frozen?

Current KuCoin documentation states that its orders are canceled. Review open positions and current platform behavior before freezing.

Can a deleted KuCoin sub-account be restored?

KuCoin states that deletion is permanent, while a frozen sub-account can be reactivated. Export records and reconcile the profile before deletion.

Final sub-account checklist

Final takeaway

KuCoin sub-accounts are most useful as an operational architecture, not as a label. A strong design gives each strategy a clear purpose, minimum permissions, limited capital, dedicated credentials, auditable transfers and a planned shutdown process. The master account remains the security root, while account type, UTA mode and margin settings define risk inside each child profile. When those layers are documented separately, sub-accounts can make automation, trading and accounting substantially easier to control.

Official KuCoin sources and further reading

• KuCoin Sub-Account Functions and Management Guide — creation, permissions, transfers, verification methods, freezing and deletion.
• How to Switch Between KuCoin Accounts — master and sub-account switching on web and app.
• How to Upgrade to KuCoin Unified Trading Account — UTA activation, sub-account strategy isolation and API requirements.
• KuCoin Unified Trading Account Overview — Classic versus UTA structure, collateral sharing and product scope.
• KuCoin UTA Expanded Eligibility and Sub-Account Controls — current eligibility, supported quantities and isolation features.
• KuCoin API Security and Permission Management — API segregation, permissions, validity and IP whitelisting.
• KuCoin Sub-Account API Documentation — dedicated sub-account API fields, permissions and IP whitelist parameters.
• Official KuCoin Blog — current product announcements and platform updates.