Skip to main content

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:

  • USD collection accounts for ACH and wire-style inbound flows.
  • EUR collection accounts for IBAN and SEPA-style inbound flows.
  • MXN collection accounts for SPEI flows with CLABE details.
  • BRL collection accounts for PIX collection flows.

Settlement model​

Virtual account deposits generally settle into supported crypto balances. Today, that usually means USDC and, where enabled, USDT on supported networks. Broader asset flexibility is expanding through Convert.

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​

  1. Define how virtual account collections should be reconciled inside your business systems.
  2. Decide which virtual account types you need and how they map to customer, merchant, or treasury entities.
  3. Align operations, finance, and support teams on the lifecycle of incoming funds.
  4. Connect webhooks or related operational tooling before launch.