How to manage multiple portfolios using an exchange's sub-account feature?

Sub-Account Structure and Access Control

1. Each sub-account operates as an independent entity under a single master account, with its own unique API keys, deposit addresses, and withdrawal permissions.

2. The master account holder can assign granular permission levels—such as read-only, trade-only, or fund-transfer—without granting full asset control.

3. Sub-accounts inherit the KYC status of the parent account but maintain separate trading histories, order books, and margin positions.

4. Withdrawals from sub-accounts require explicit approval via the master account’s two-factor authentication, adding a structural barrier against unauthorized fund movement.

5. Internal transfers between sub-accounts occur instantly and without network fees, enabling real-time capital reallocation across strategies.

Risk Isolation Across Trading Strategies

1. A sub-account dedicated to high-leverage futures trading holds no exposure to spot holdings in another sub-account used for long-term BTC accumulation.

2. Margin calls triggered in one sub-account do not liquidate assets held elsewhere, preserving capital integrity across divergent risk profiles.

3. Automated trading bots deployed on individual sub-accounts cannot access balances or open orders outside their designated scope.

4. If a sub-account incurs losses exceeding its equity, the deficit remains contained and does not propagate to other sub-accounts or the master wallet.

5. Isolated margin settings apply per sub-account, meaning leverage parameters, maintenance margins, and liquidation prices are configured independently.

Compliance and Audit Trail Segmentation

1. Every sub-account generates distinct ledger entries, including timestamps, transaction hashes, and counterparty identifiers, which remain non-mergeable in export reports.

2. Tax reporting tools allow filtering by sub-account ID, producing segregated PnL summaries compliant with jurisdiction-specific capital gains rules.

3. Institutional clients use sub-accounts to allocate funds across departments—e.g., market-making, OTC desk, and treasury—each with auditable custody boundaries.

4. Regulatory inquiries can be addressed with sub-account-specific data packages, reducing disclosure scope and minimizing operational exposure.

5. No shared order book visibility exists between sub-accounts; even identical trading pairs execute in siloed matching engines.

API Integration and Automation Constraints

1. API keys generated for a sub-account only authenticate endpoints relevant to that sub-account’s balance, orders, and positions.

2. Webhook payloads include a sub-account identifier field, allowing backend systems to route events to strategy-specific processing queues.

3. Rate limits are enforced per sub-account, preventing one bot’s burst activity from throttling another’s execution pipeline.

4. Sub-account APIs prohibit cross-sub-account operations—no endpoint accepts requests to transfer funds or cancel orders outside its assigned namespace.

5. Historical trade data retrieval is scoped exclusively to the requesting sub-account’s activity, with no aggregation or cross-reference capability.

Frequently Asked Questions

Q: Can a sub-account initiate withdrawals to external wallets?A: No. External withdrawals must originate from the master account. Sub-accounts may only transfer internally or request approval through the master’s authorization workflow.

Q: Are sub-accounts visible to exchange support staff during ticket resolution?A: Support agents see sub-account identifiers and activity logs only when explicitly referenced in the support request; they cannot browse or switch between sub-accounts without user-provided context.

Q: Does staking rewards earned in one sub-account affect the APY calculation of another?A: No. Staking yield accrual, lock-up periods, and reward distribution are calculated and credited separately for each sub-account based on its individual staked balance and selected product.

Q: Can I apply different whitelisted withdrawal addresses per sub-account?A: Yes. Whitelist management is sub-account specific. Each can maintain its own set of pre-approved external addresses, with independent confirmation requirements.