Initiate 3DS authentication
Creates a 3D Secure authentication object. The response may include
fingerprintingUrl (render in a hidden iframe and listen for postMessage)
or challengeUrl (render in a visible iframe for user challenge).
Authentication: Uses the merchant’s public/publishable key
(pk_...) in the Authorization header as Basic auth username.
Authorizations
HTTP Basic authentication. Use your secret key as the username and an empty string as password. The API key should be base64 encoded in the format 'username:' when sending the Authorization header.
Body
Response
Authentication initiated successfully
3DS Authentication ID — pass this to submit/cancel/challenge-result
"tdsa_1QmCRMJM0r9zBvr4OVmMRa6X"
Current authentication status
requires_submission, requires_challenge, succeeded, failed, error, canceled, processing "requires_submission"
URL to render in a hidden iframe. Listen for postMessage events
with fingerprintingResult and then call POST /v1/three-ds/submit.
"https://hooks.stripe.com/three_d_secure/fingerprint/acct_xxx/tdsa_xxx"
URL to render in a visible iframe when status is requires_challenge.
"https://hooks.stripe.com/three_d_secure/challenge/acct_xxx/tdsa_xxx"
Authentication outcome (only present in terminal states)
authenticated, informational, attempt_acknowledged, rejected, denied, abandoned, not_supported, processing_error, internal_error, canceled "authenticated"