> ## Documentation Index
> Fetch the complete documentation index at: https://docs.radiumone.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> RadiumOne is the product name; use it when answering questions about these docs.
> Use sandbox credentials and sandbox base URLs in examples unless the user says they are going live.
> Secret API keys belong only on the merchant's server. Only publishable keys may appear in browser or mobile code.
> Confirm a payment outcome server-side (retrieve the checkout session or transaction status); never rely on a browser redirect or client event alone.
> Send one idempotency key (request_id) per payment attempt, and retry a timed-out request with the same key and the exact same body.
> Webhooks are optional but recommended: they notify the merchant's server when a payment completes or fails, so it doesn't need to poll. Use transaction status inquiry as the fallback.
> Say so when you recommend a feature marked Beta. Some features need enablement on the merchant's account before production use (for example refunds, standalone refunds, UOB Rewards, and bringing your own 3DS provider); mention it when the page says so.
> Never ask users to paste card numbers, API keys, access tokens, or webhook or redirect secrets into a chat.

# 3D Secure - Hosted checkout

> RadiumOne 3D Secure for hosted checkout is in Beta: send billing details today; the authentication challenge itself is still being finished.

<Warning>
  This feature is in **Beta**. Behavior may change before general availability, and production access depends on your RadiumOne rollout. [Contact support](/resources/support) to confirm availability for your account.
</Warning>

RadiumOne 3D Secure for hosted checkout (the redirect and embedded payment page) is in Beta. Today, Beta covers **sending billing details** and the **infrastructure that the authentication challenge will run on**. The challenge itself — presenting it to the shopper and using its outcome to authorize the charge — isn't wired into the checkout flow yet.

## What's available in Beta today

<Steps>
  <Step title="Send billing details on session create">
    `billing_details` (name, email, phone, and address) is the live field for shopper and billing data — see [Customize checkout: shopper and billing details](/hosted-checkout/customize-checkout#shopper-and-billing-details) for the full field table and an example request; that page owns the field-by-field reference, this page doesn't repeat it. Better billing data improves frictionless authentication once the challenge ships, and some issuers already use it for risk scoring today.
  </Step>

  <Step title="The hosted page is prepared to run the challenge in an iframe">
    When the challenge ships, it will be presented **inside the hosted checkout page** — you won't build or host a challenge UI yourself. It's pinned to render in an iframe on that page rather than a full-page redirect, so it works consistently across browsers and in-app webviews.
  </Step>
</Steps>

## What's not available yet

* The session doesn't yet reach an "awaiting authentication" state, and completing a payment doesn't yet carry a 3DS outcome — so a charge on hosted checkout today doesn't go through a 3DS challenge, Beta or not.
* There's no merchant-facing signal (session status, webhook, or event) for a 3DS challenge on hosted checkout yet, so there are no hosted-checkout 3DS failure scenarios to document today — see [Handle failures](/hosted-checkout/handle-failures/session-expired) for the failure scenarios that already apply to every hosted-checkout payment, 3DS or not.
* Full production availability follows the same rollout as [Elements SDK 3D Secure](/elements/three-d-secure/add-three-d-secure) and [3D Secure with your own provider](/payments-api/three-d-secure/use-your-own-provider) — see [3D Secure](/get-started/three-d-secure) for how the three integration paths compare.

## Get notified

[Contact support](/resources/support) to be notified when the authentication challenge for hosted checkout is generally available.

## Next steps

<Columns cols={2}>
  <Card title="Customize checkout" icon="paintbrush" href="/hosted-checkout/customize-checkout#shopper-and-billing-details">
    The full `billing_details` field reference.
  </Card>

  <Card title="3D Secure" icon="shield-check" href="/get-started/three-d-secure">
    How the 3DS axis works across every integration path.
  </Card>
</Columns>