Products
Payment infrastructure organised by the job it needs to do
Choose collection, conversion, settlement, or payout capabilities by operating requirement—not by a long list of overlapping product names.
Product map
Choose by payment intent
Accept payments
Choose the customer-facing surface by payment intent rather than creating duplicate products.
Collect and reconcile
Attach repeat bank or blockchain deposits to the right customer, merchant, or ledger entity.
Convert and settle
Connect collection to supported balances, quoted conversion, treasury, and settlement operations.
Pay out and embed
Disburse approved balances or embed selected infrastructure into a platform.
Currencies, assets, and networks
Published examples, with availability kept honest
The examples below are grounded in Radom's public documentation. They are not a universal coverage commitment: onboarding, organisation configuration, market, route, account type, asset, network, corridor, limits, and partner availability still apply.
Browse digital asset payment research pages →Open Banking
Radom publicly documents enabled EUR and GBP bank-led payment flows. Banks, rails, markets, timing, and organisation access remain configuration-specific.
Review the public sourceVirtual accounts
Public material describes enabled USD, EUR, MXN, and BRL account formats. Account type, region, permitted purpose, settlement asset, and network depend on onboarding and configuration.
Review the public sourceCrypto payments
Assets and blockchain networks must be read from currently documented or enabled payment methods; a token name alone is not a complete payment route.
Review the public sourceConversion and payouts
Supported pairs, minimums, quotes, payout currencies, assets, networks, and corridors are route-specific and should be confirmed from current APIs and organisation capabilities.
Review the public source
