Introducing Radom v2.0: one balance, any asset, anywhere

Radom v2.0 is live, and organisations are being moved onto it over the coming weeks. It changes the basic unit of a Radom account. Instead of holding a separate balance for each network an asset happens to arrive on, an organisation now holds one balance per asset, converts between assets with a live quote, and pays out in whatever asset and network the recipient wants, funded from whatever it already holds.

This post covers what is live today, what it means day to day, and what is planned for the rest of the year and into 2027.

One balance per asset, on every supported network

Until now, a stablecoin balance in Radom was really several balances, one for each network the stablecoin had arrived on. A payout had to be funded from the balance on the network the recipient used, so teams kept an eye on several numbers for what was, economically, one asset.

In v2.0 that distinction is gone. USDC received on Ethereum, Base, Polygon, Arbitrum, BNB Chain, Tron or Solana is simply USDC in the account, and it can be spent on whichever network the recipient uses without the organisation moving anything first. The same applies to every other supported asset: one balance, usable across every network that asset is supported on. The live list of supported assets and networks is on the cryptocurrencies page.

For finance teams this is a simpler ledger. For product and operations teams it means one number to reconcile, one balance to top up, and no more per-network balances to juggle.

Conversions with a live quote

Organisations can now convert between supported assets directly from the dashboard or the API. Each conversion is priced with a live quote, shown before it is confirmed, and it settles straight into the balance of the asset being bought. There is no separate exchange step to run or reconcile afterwards. Conversion is available where supported; the crypto convert page describes the product in more detail.

Payouts from any asset to any asset

Payouts work the same way. A recipient can be paid in the asset and network they want, funded from whatever balance the organisation holds. Where the two differ, the conversion happens as part of the payout, with the quote shown before the payout is confirmed. An organisation that collects in one stablecoin and pays contractors in another no longer needs a manual conversion in between. The payouts page covers batch and API-driven payouts in more depth.

Auto conversion for incoming payments

Some organisations want to accept whatever their customers pay in but hold only one or two assets. Auto conversion handles that. When it is switched on, incoming payments are converted automatically into a preferred settlement asset as they arrive, so the organisation holds what it wants to hold without anyone watching the balances. It is optional.

Built on a unified treasury

Everything above runs on Radom's unified treasury. It keeps every organisation's balances backed one to one, and it monitors solvency continuously rather than at the end of a reporting period. Customers do not have to think about it, but it is what allows a single balance to be spent on any supported network and converted with a live quote.

What comes next

Radom v2.0 is also the foundation for the fiat side of the platform. The items below are expectations rather than commitments. Each depends on partner and regulatory approvals, and timings may move.

• Later this year: a direct US banking partnership that is expected to give Radom much more flexibility in offering US dollar accounts, with ACH, Fedwire and FedNow for domestic transfers, plus US dollar SWIFT rails for global transfers.
• Before the end of the year: a similar arrangement in Europe, expected to allow Radom to offer both virtual IBANs and full featured IBANs for EUR and GBP, with local SEPA and SEPA Instant rails and Faster Payments.
• Expected in the first quarter of 2027: a further bank partnership through which Radom expects to offer more than fifty local bank transfer rails. Customers would be able to move USD, EUR, GBP and any supported crypto asset to send payouts like a local and receive payments like a local across many jurisdictions, with strong anticipated coverage across the Middle East, East and South Asia, Latin America, Oceania and parts of Africa.

The direction is simple: one account, every supported asset and currency, and whichever rail suits the recipient. Today's virtual accounts and on and off ramp products are the starting point for that.

How existing customers get v2.0

There is nothing to do. Radom moves each organisation over to v2.0, and a banner appears in the dashboard when it is live for that organisation. Accounts are being moved over the coming weeks.

Where to go next

If you want to talk through what v2.0 means for your payment and payout flows, contact our sales team. Developers can start with the documentation.