Skip to main content

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.
Supported networks: 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.
Endpoint
Path Parameters Response
  • type is SUB_ACCOUNT for every sub-wallet.
  • parentId is the ID of the business account that created and authorizes the sub-account.
  • address is used for EVM-compatible networks (polygon, arbitrum, base).
  • tronAddress is used for the tron network.
  • solanaAddress is used for the solana network.

Get Balance

Endpoint
Returns the same response shape as the main wallet Get Balance endpoint — token balances for all network/token pairs, plus a totalBalance summary per token.

Withdraw

Endpoint
Initiates an on-chain token transfer from the sub-account’s wallet to an external address. Same request body and response shape as the main wallet Withdraw endpoint.
A fee is deducted from every withdrawal. The fee amount is returned in the response and is charged in addition to the withdrawal amount.

Transaction History

Endpoint
Same query parameters and response shape as the main wallet Transaction History endpoint, scoped to the sub-account.

Get Single Transaction

Endpoint
Same response shape as the main wallet Get Single Transaction endpoint.

Funding 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 a subAccountId that does not belong to the authenticated business return an authorization error.