Skip to main content

Crypto payments overview

Radom's crypto payment products are designed for merchants that want to accept on-chain payments and keep the rest of their money movement in the same operating stack. That usually means pairing payment collection with webhooks, deposits, conversion, and payout workflows rather than treating checkout as a standalone feature.

What falls under crypto payments​

  • Hosted checkout for the fastest launch path.
  • Integrated checkout when you want payment instructions inside your own UI.
  • Payment links for lighter-weight merchant collection flows.
  • Invoicing when you need payable requests with customer context and reconciliation.

Which launch path to choose​

  • Use Hosted checkout if you want Radom to host the payment experience.
  • Use Integrated checkout if you want the payment flow embedded inside your own product.
  • Use Payment links if you want reusable collection pages without a full custom checkout.
  • Use Invoicing if your process starts with a payable request rather than a cart-style checkout.

How settlement fits in​

Payment collection is usually only the first step. After a payment lands in Radom, merchants commonly:

  1. Reconcile the payment with webhooks.
  2. Route funds into treasury balances or customer-linked deposit flows.
  3. Convert assets with Convert if the business wants to hold or disburse a different asset.
  4. Move funds back out through Payouts or Mass payouts.

What to plan before launch​

  • Confirm which networks and tokens you want to make public.
  • Decide whether settlement should stay in the collected asset or move into a treasury asset after collection.
  • Connect webhooks before going live so fulfillment and reconciliation are not dependent on polling.
  • If you also need fiat funding or off-ramp flows, review Open banking onramp, Virtual accounts, and Payouts.