Skip to main content
Deposit accounts are permanent pay-in wallets under your organisation’s Virtual Accounts. Use them when each user holds a balance and can top up any amount over time (iGaming, prepaid wallets, account funding).

​
How it works

  1. You create or ensure a Ready primary virtual account
  2. For each user, call create pay-in address with reference = your user id and a chain_id
  3. Show the address (and memo/tag when the chain requires one)
  4. Deposits to that sub-account are automatically swept to the parent virtual account
  5. You credit the user’s balance only after verified webhooks / payment events

​
When not to use deposits

For a single fixed charge for a product, use Payments Overview instead.

​
Prerequisites

​
Asset and network safety

Only instruct users to send assets that are enabled on the chain you requested for that deposit wallet. Transfers of wrong tokens, wrong networks, or assets outside your virtual-account configuration may not be detected or credited. Review Networks and Currencies. When recovery is possible, pricing describes payment recovery fees.
Supported deposit-wallet namespaces (merchant pay-in API) are EVM, Solana, Tron, and Bitcoin. TON and Celo deposit wallets are rejected by the API.

​
Partner APIs

Platform partners can create virtual accounts and deposit wallets under /partners/accounts/.... Merchant guides focus on /accounts/virtual/.... See the API reference Partners tags if you integrate as a partner.

​
Next steps