EukaPay vs Radom: comparing gateways for stablecoins or crypto

August 21, 2026

EukaPay vs Radom: comparing gateways for stablecoins or crypto

Radom publishes one of the more aggressive rate cards in the market. For a business comparing ways to accept stablecoins or crypto, that pricing page does a lot of work.

The product surface is genuinely broad, and its own terms of service place limits on who can use it that the pricing page does not mention. This guide compares the two across products, developer features, settlement and eligibility.

Quick verdict

EukaPay collects stablecoins or crypto from customers and settles to the merchant's own bank account in USD, EUR, GBP, CAD, with a locked exchange rate available on conversion. Invoices, payment links, checkout, subscriptions, a POS terminal and e-commerce plugins run from one account, and crypto payouts in USDC, USDT, ETH, BTC run from the same account.

Radom publishes a broad product list covering invoicing, subscriptions, virtual accounts, token presales and an Open Banking product. The Radom terms of service also carry a jurisdiction representation covering the US, the UK, Canada and the EU, plus a statement about Radom Pay's own regulatory standing. Both are set out in the next section.

For a business in the US, the UK, Canada or the EU that wants settlement into its own bank account, EukaPay is the option built for that.

Eligibility and corporate footing

The Radom site footer states that Radom Pay is incorporated in the Cook Islands and is registered with the Cook Islands Financial Intelligence Unit as a reporting institution.

The Radom terms of service, last updated 1 July 2026, add a sentence the footer does not: Radom Pay currently operates as an unregulated business entity under the Limited Liability Companies Act 2008 and is not licensed or regulated by the Cook Islands Financial Supervisory Commission.

The same Radom terms include a user representation covering jurisdiction: that you are not a US person, and that you are not accessing the services from the United Kingdom, Canada or the EU, or any jurisdiction where Radom Pay lacks required local authorisation, except strictly on the basis of reverse solicitation. Radom separately claims broad country coverage, and publishes localised sites for several markets. Those two positions sit in tension, and Radom is the party to resolve it with before you integrate.

Two further inconsistencies are on their own site. The Radom iGaming page states that Radom is licensed as a Virtual Asset Service Provider ensuring regulatory compliance across the EU, which the Radom terms of service do not support. A non-www version of the Radom about page still names different corporate entities as the provider of cryptoasset services, while the current Radom footer names a single provider.

EukaPay onboards through signup, verification and legal business information, then API key generation, and every merchant goes through a business review.

Payment products

The Radom product list is long. Radom does not publish a POS or in-person terminal product, and does not publish a Shopify integration.

Product

EukaPay

Radom

Invoicing

Yes

Yes

Subscriptions

Yes, invoices on a schedule from daily to annually

Yes, pulling funds from a customer wallet at the agreed interval

Hosted checkout

Yes

Yes

Payment links

Yes

Yes

POS terminal

Yes

Not published

E-commerce plugins

Yes

Yes, major platforms

Shopify

Yes

Not published

Crypto mass payouts

Yes, CSV upload in the dashboard

Yes, from the dashboard, CSV upload or API

Payout API

Yes

Yes

Currency conversion

Locked exchange rate available on conversion

Yes, a conversion API

White label

Yes, for payment service providers

Yes

Platform and developer features

Two developer details are worth weighing before you build.

Radom webhook verification uses a plaintext shared secret rather than a signed payload, and Radom documents a limited number of delivery retries. Both are worth allowing for in defensive code.

EukaPay's REST API is documented at docs.eukapay.com covering invoices, subscriptions, customers, the payout endpoints and balance transfer, and a sandbox is available for development.

Feature

EukaPay

Radom

REST API

Yes

Yes

Test environment

Yes

Yes

Idempotency on POST

Yes

No request-level idempotency header documented

Customer records

Yes

Referenced, with no documented customer object or endpoints

Onboarding route

Self-serve signup, then verification

Self-serve for core payments; newer infrastructure products are sales-gated

Settlement and assets

EukaPay settles to the merchant's own bank account in USD, EUR, GBP, CAD, and the merchant chooses fiat or crypto settlement. Payouts are sent in USDC, USDT, ETH, BTC across the Ethereum, Tron and Bitcoin networks, with asset and network set per payout. Because payouts settle on-chain, they are not tied to banking hours or the banking calendar.

Radom publishes off-ramp settlement in USD, GBP and EUR, and the Radom documentation also references MXN and BRL. Radom's stated coverage spans major assets across supported networks, and Lightning is not mentioned on the Radom site or documentation. The Radom pricing page also omits the per-network deposit address setup fees and deposit minimums that appear in the Radom documentation. On small payments, that detail changes the arithmetic. EukaPay prices each merchant on volume, use case and product mix, agreed with the EukaPay team during onboarding.

The Radom terms of service describe safekeeping of cryptoassets by Radom Pay on the user's behalf, using either segregated blockchain addresses or omnibus wallets with internal ledger segregation, while stating that title remains with the user. The Radom about page separately describes a world without any middleman. Those two statements sit awkwardly together.

Item

EukaPay

Radom

Fiat settlement currencies

USD, EUR, GBP, CAD

USD, GBP, EUR, with MXN and BRL in the docs

Settlement destination

The merchant's own bank account

Off-ramp to a bank account, or virtual accounts

Fiat rails

Settlement to the merchant's own bank account

Yes, standard bank rails

Pay-in assets

BTC, ETH, USDT, USDC, BCH, LTC, SOL and Lightning

Major assets across supported networks

Lightning

Yes

Not mentioned on its site or documentation

Payout assets

USDC, USDT, ETH, BTC

Crypto payouts across its supported networks

Where the differences actually matter

For a business in the US, the UK, Canada or the EU

The user representation in the Radom terms of service covers exactly those markets, except on the basis of reverse solicitation. A business in New York, London, Toronto or Berlin should read that clause in full and get clarity from Radom before building against the API. EukaPay settles to the merchant's own bank account in USD, EUR, GBP, CAD, and onboards through signup, verification and legal business information.

For a retail or in-person business

Radom does not publish a POS or terminal product. EukaPay's

POS terminal

handles in-person payments from the dashboard, which matters for a shop, a venue, or any business taking payment across a counter.

For a Shopify store

Radom publishes integrations for a small number of e-commerce platforms. Shopify is not among them. EukaPay publishes

e-commerce plugins

covering Shopify, so a store owner installs rather than builds.

Switching from Radom to EukaPay

Three questions come up before a migration: onboarding, customer impact, and what the integration work actually is.

  • Onboarding:

    sign up on the EukaPay dashboard, complete verification, provide legal business information, then generate an API key. A sandbox is available for development.

  • Customer experience:

    customers pay through a hosted EukaPay checkout and can pay in BTC, ETH, USDT, USDC, BCH, LTC, SOL and Lightning. A locked exchange rate is available on conversion.

  • Integration work:

    move the authorisation header to EukaPay authentication, point checkout or invoice creation at the EukaPay endpoints, and rebuild the webhook handler to verify the EukaPay payload rather than compare a shared secret. The endpoints are documented at docs.eukapay.com, and the sandbox is available to run the new integration before production traffic moves.

Move any remaining Radom balance out before the switch. There is no direct provider-to-provider transfer of crypto balances.

Frequently asked questions

Which currencies can EukaPay settle to my bank account?

USD, EUR, GBP, CAD, to your own business bank account. You choose fiat or crypto settlement.

What does EukaPay charge?

EukaPay does not publish a public rate card. Pricing is agreed with the EukaPay team based on your business, so

contact the team

for a quote.

Which assets can my customers pay with?

BTC, ETH, USDT, USDC, BCH, LTC, SOL and Lightning.

Which assets can EukaPay send in a payout?

USDC, USDT, ETH and BTC, across the Ethereum, Tron and Bitcoin networks. Asset and network are set per payout.

Can I take payments in person?

Yes. The

POS terminal

handles in-person payments from the dashboard.

Does EukaPay work with Shopify?

Yes. EukaPay publishes

e-commerce plugins

for online stores, including Shopify.

Does EukaPay support recurring billing?

Yes. Subscriptions send invoices on a recurring schedule at intervals from daily to annually, through the dashboard and the API.

How does onboarding work?

Sign up, complete verification, provide your legal business information, then generate an API key. Every merchant goes through a business review.

Related articles

Get started with EukaPay

Create your EukaPay account

and explore the dashboard, or

talk to sales

to scope a specific use case.

Last updated: August 2026. Verify current pricing, terms and feature availability with each provider.