Overview
A sub-wallet is a stable currency wallet that belongs to a sub-account created by a business, rather than to the business’s own account. The business is the authorizer of the sub-wallet and is the only party that can view or act on it — a sub-account can only be accessed by the parent that created it.Before creating a sub-wallet, the business must first create a sub-account via
POST /sub-account. See the Sub-Account documentation for details. The subAccountId returned from that call is required for every endpoint below.polygon, arbitrum, base, tron, solana
Supported tokens: USDT, USDC
Create Sub-Wallet
Each sub-account can only have one wallet. Calling this endpoint when a wallet already exists returns a
409 error.
Response
typeisSUB_ACCOUNTfor every sub-wallet.parentIdis the ID of the business account that created and authorizes the sub-account.addressis used for EVM-compatible networks (polygon,arbitrum,base).tronAddressis used for thetronnetwork.solanaAddressis used for thesolananetwork.
Get Balance
EndpointtotalBalance summary per token.
Withdraw
EndpointTransaction History
EndpointGet Single Transaction
EndpointFunding in Test Environments
There is no dev-fund endpoint for sub-account wallets. To simulate a deposit in a non-production environment, withdraw from your own main wallet to the sub-account’s address on the desired network (using the fund-dev flow on the main wallet first, if you need test tokens to withdraw).
Access Control
A sub-wallet can only be viewed or acted on by the business (parent account) that created its sub-account. Requests scoped to asubAccountId that does not belong to the authenticated business return an authorization error.
