What’s available in Beta today
1
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 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.2
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.
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 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 and 3D Secure with your own provider — see 3D Secure for how the three integration paths compare.
Get notified
Contact support to be notified when the authentication challenge for hosted checkout is generally available.Next steps
Customize checkout
The full
billing_details field reference.3D Secure
How the 3DS axis works across every integration path.