Skip to main content
RadiumOne has two ways to accept a card — hosted checkout and Elements + the Payments API — and three ways to run 3D Secure on top of either one. Pick a row for how you want to build the payment page, then a column for who runs 3D Secure.

The grid

The Elements + Payments API row is fully live today, with or without RadiumOne 3D Secure. Hosted checkout is live too, with or without RadiumOne 3D Secure, if you’d rather not build any payment UI at all.

How to choose

1

Is a RadiumOne-hosted payment page okay for your shoppers?

Yes → hosted checkout — see Redirect to hosted checkout. No, you want the card fields on your own page → Elements — see Accept a card payment.
2

Do you need 3D Secure today?

Both No-3DS paths above are already live. RadiumOne 3DS is live on both: it runs end to end with Elements — see 3DS with Elements — and inside the payment page with hosted checkout — see 3DS with hosted checkout. For how the options compare, see 3D Secure overview.
3

Do you already have your own 3DS provider?

Bringing your own 3DS provider is a direct Payments API integration: you collect the card details yourself (your PCI scope) instead of using Elements, and send them with your provider’s result. It’s available on request and enabled per outlet — see Use your own 3DS provider.

Hosted checkout

The shopper is redirected to (or embedded via an iframe with) a RadiumOne-hosted page where they enter their card. With hosted checkout, the shopper enters their card details on a RadiumOne-hosted page. Your server and website never see or handle raw card data, which keeps your PCI DSS scope minimal. Effort: low. You create a checkout session, redirect the shopper, and handle the return — no payment UI to build.

Elements + Payments API

RadiumOne Elements renders secure card fields on your own page and tokenizes the card in the browser; your server calls the Payments API to charge it. With Elements, card fields render inside RadiumOne-hosted iframes and tokenize the card before it reaches your server. Your website never touches raw card data, which keeps your PCI DSS scope reduced compared to handling card numbers directly. Effort: medium. You build the checkout page around the Elements fields and call the Payments API from your server.

Bringing your own 3DS provider

If you already run 3D Secure through another provider, you can collect the card details yourself, authenticate with them, and send the card details and the result to RadiumOne when you charge. When you use your own 3DS provider, you collect the card details yourself and send them to RadiumOne with your provider’s result, so your payment form, your server and your 3DS provider are in your PCI DSS scope. RadiumOne never passes the card number to your provider. Confirm your PCI DSS scope with your assessor before you go live.

Can I switch later?

Yes. Hosted checkout and Elements both call the same RadiumOne Payments API and emit the same webhook events, so your backend logic for capturing, refunding, and reconciling payments doesn’t change. Many merchants start with hosted checkout for the fastest launch, then move to Elements later for more control over the payment page.

Next steps

Sandbox and API keys

Get sandbox credentials before you write any code.

Quickstart

Accept your first payment in sandbox with hosted checkout.

3D Secure overview

Understand the 3DS column in more depth.

Elements overview

Learn what Elements provides before you integrate it.
Last modified on October 30, 2026