Open banking onramp
Use Radom open banking flows when you want fiat to enter Radom from bank rails and settle into supported crypto balances. This is typically used as a merchant treasury funding tool, a customer funding flow, or part of a broader bank-to-crypto product experience.
What it is for
Open banking onramp is typically a fit when you want:
- Customers or operations teams to fund Radom from a bank account.
- Fiat inflows to settle into USDC or another supported stablecoin balance today.
- A bank-led funding step that can later connect to payout, convert, or treasury workflows.
What the public flow supports today
The standalone public onramp API currently creates SEPA funding instructions. In some enabled EUR checkout experiences, customer-facing bank methods can appear as Sepa Credit or Sepa Instant, but that depends on the product flow and organization setup.
How settlement fits in
Fiat-connected settlement networks today include Arbitrum, Base, Ethereum, Polygon, Solana, and Tron. Public flows commonly settle into USDC today, with USDT also available on selected destination networks. Broader asset flexibility is expanding through Convert, including automatic asset movement in more workflows.
Availability and onboarding
Open banking availability depends on geography, onboarding status, enabled products, and the exact payment flow you want to launch. Treat this page as public guidance rather than a guarantee that every rail or country is enabled by default.
Recommended implementation path
- Confirm availability with your Radom contact before building your production experience.
- Decide whether the flow is merchant treasury funding, a customer-facing payment journey, or a hybrid product flow.
- Define which network and balance the onramp should settle into and how Convert should fit after funding.
- Use webhooks wherever you need real-time status updates about funding state changes.