Customer deposits
Provision persistent addresses and account for customer-owned stablecoin balances.
Customer deposits let a merchant assign persistent, merchant-scoped deposit addresses to a Customer. They are different from one-time Checkout payment addresses: deposits credit the customer's exact chain-and-asset balance and can later fund customer-balance payments or withdrawals.
Resource model
Customer
└── Deposit account (EVM address family)
└── Address slot
├── Ethereum asset watches
├── Base asset watches
├── BNB Chain asset watches
└── Polygon PoS asset watchesOne EVM address slot may watch multiple enabled EVM chains, but balances remain separated by exact
chain and asset. Never present balances as interchangeable just because symbols match.
Before provisioning, call GET /api/v1/deposit-assets for the authoritative enabled chains,
contracts, precision and deposit limits. Address provisioning can be asynchronous; wait for an
active/watching state and consume signed customer_deposit.* events.
Continue with Accounts and addresses and Deposits and balances.
Did this page answer your question?
Your feedback helps us improve the integration path.