Payment gateway
Radom
Payments infrastructure for crypto-native businesses, with subscriptions, payouts and multi-chain support.
Opens radom.com in a new tab.
Radom provides payment infrastructure aimed at businesses operating natively in crypto — one-off checkouts, recurring subscriptions, payouts and treasury tooling across multiple networks. Its subscription support is notable, since recurring billing is the hardest problem in stablecoin commerce and few providers address it directly.
Capabilities
- Custody model
- hybrid
- Settlement
- stablecoin, crypto, fiat
- Settlement notes
- Multi-network settlement with treasury and payout tooling.
- Fees
- Published on the provider's pricing page; confirm current rates directly.
- Shopify
- Not confirmed
- WooCommerce
- Not confirmed
- API
- Available
- Hosted checkout
- Available
- Invoicing
- Available
- Merchant verification
- Supported
- Geographic availability
- Confirm coverage with the provider for your market.
- Merchant requirements
- Business account and verification.
Integrations
- Custom API
- Hosted checkout
- Payment links
- Subscriptions
- Payouts
Strengths
- Genuine recurring subscription support, which is rare
- Payouts and collection in one platform
- Broad network coverage
Trade-offs
- API-first, so less suited to merchants wanting a plugin
- Smaller ecosystem than the incumbent gateways
- Aimed at crypto-native businesses rather than conventional retail
Radom is worth attention for one reason above the others: it takes recurring billing seriously.
The hardest problem in stablecoin commerce
Every SaaS business that considers accepting stablecoins hits the same wall. Cards renew themselves; stablecoins do not. The workarounds — prepaid balances, annual prepay, manual invoicing — all work and all shift effort onto the customer.
Providers that attack this directly are rare, and the approaches vary: on-chain authorisation where the network supports it, delegated transfers, or managed prepaid balances with automated dunning. None is as invisible as a card on file, and the good implementations get closer than you would expect.
API-first
This is infrastructure rather than a plugin. A team comfortable writing an integration will find it capable; a merchant wanting a WooCommerce checkbox should look elsewhere.
Payouts as well as collection
Businesses paying contractors, affiliates or suppliers in stablecoins need the other direction too, and having both on one platform removes a reconciliation problem.