Virtual accounts
Virtual accounts are named fiat collection accounts that help merchants receive bank-led deposits into Radom while keeping attribution and reconciliation clearer than with a shared account model.
Typical use cases
- Reconciling inbound collections by customer, merchant entity, or workflow.
- Supporting repeat or operationally structured bank-based collection flows.
- Mapping incoming fiat into downstream crypto treasury or payout processes.
Supported account types
Depending on your organization setup and regional coverage, Radom virtual accounts can support:
USDcollection accounts with US account and routing details.EURcollection accounts with IBAN and SEPA details.MXNcollection accounts with CLABE and SPEI-style collection details.BRLcollection accounts with Pix collection details.
Settlement model
Virtual account deposits generally settle into supported crypto balances. USD collection flows can settle into USDC or USDT depending on the enabled destination network. EUR, MXN, and BRL collection flows currently settle into USDC. Broader asset flexibility is expanding through Convert.
Settlement networks today
Fiat-connected settlement networks today include Arbitrum, Base, Ethereum, Polygon, Solana, and Tron. The exact destination network available to your organization depends on onboarding status and enabled products.
Availability and rollout
Virtual account support depends on your region, onboarding status, enabled capabilities, and the exact account types you need. Confirm the operating model, settlement asset, and collection behavior available to your organization before exposing the flow to customers or finance teams.
Implementation guidance
- Define how virtual account collections should be reconciled inside your business systems.
- Decide which virtual account types you need and how they map to customer, merchant, or treasury entities.
- Align operations, finance, and support teams on the lifecycle of incoming funds.
- Connect webhooks or related operational tooling before launch.