Wallet operations
Embedded wallets
Embedded wallets let your backend create blockchain addresses for product entities without exposing wallet infrastructure directly to end users.
Use this model when you need a wallet or deposit address per customer, merchant, seller, contractor, player, recipient, or internal account.
Common wallet models
| Model | Example |
|---|---|
| Per-customer wallet | An exchange or fintech creates a deposit address for each customer |
| Per-merchant wallet | A payment platform gives each merchant an isolated stablecoin receiving address |
| Per-seller wallet | A marketplace tracks funds and payouts per seller |
| Per-player wallet | An iGaming operator attributes deposits and withdrawals to player accounts |
| Internal account wallet | A treasury team separates operating, settlement, or fee accounts |
Why embedded wallets matter
Embedded wallets help you:
- Attribute deposits to the right product account.
- Avoid relying only on omnibus-wallet memo logic.
- Track wallet activity with stable internal identifiers.
- Route wallet events into product, operations, finance, and support workflows.
- Connect wallet activity to ledger entries for reconciliation.
Wallet creation flow
- Choose the product entity
Decide which customer, merchant, seller, recipient, player, or internal account needs a wallet.
- Request the wallet
Your backend sends a signed API request with the organization, chain, asset, and label.
- Store BroSettlement IDs
Store walletId, organizationId, chain, asset, address, and your internal account ID.
- Subscribe to lifecycle events
Use WebSocket events to detect deposits, confirmations, withdrawal state changes, and failures.
- Reconcile the ledger
Use ledger entries to update accounting state and customer-facing balances.