Subaccount

Overview

Meaning and scope

Subaccount is a separately identified account maintained under a parent account for a customer, merchant, strategy, legal entity, asset, or operational purpose. Account balances and labels are ledger concepts whose meaning depends on inclusion rules, legal ownership, external asset backing, restrictions, and timing.

How it works

Internal records must be reconciled to blockchain and custodian evidence. It can provide ledger segregation and permissions without representing a separately titled external custody account or unique blockchain address. Operationally, systems define parent-child ownership, balances, transfer rules, permissions, limits, statements, and reconciliation to external assets.

Operational checks and limits

A subaccount is a logical segment within a larger customer or treasury relationship. Depending on architecture it can share custody keys or receive distinct addresses and permissions.

Practical example

A marketplace tracks seller balances in subaccounts while settlement funds remain in a common controlled treasury.

Distinctions

A subaccount is an accounting or permission boundary; a separate on-chain wallet requires independently defined keys and addresses.

How to evaluate it

Asset availability and authority to move an asset are different questions; for Subaccount, map who can initiate, approve, sign, recover, and audit a movement, and which keys or institutions control each step. When evaluating Subaccount, the recovery plan should consider compromised credentials, unavailable signers, incorrect destination information, and frozen or delayed transfers; test access changes without assuming that a displayed balance guarantees immediate spendability.

Operational edge cases

Subaccounts let a treasury separate projects, teams or customer activity without necessarily creating independently owned wallets. Determine whether balances are legally and cryptographically segregated or only split in a software ledger. Internal transfers between subaccounts must not be counted as fresh deposits or payouts. Access and reporting policies should specify which parent account is responsible for liabilities and reconciliation. Related concepts: Multi-Account Management; Omnibus Account; Vault Account.