# Standalone 3DS

Use the standalone 3DS API to run EMV 3D Secure (3DS) authentication and authorize the payment with any payment service provider (PSP).

Use the standalone 3DS API to run EMV 3D Secure authentication independently from payment authorization. By decoupling authentication and authorization, standalone 3DS allows you to authenticate on Stripe while processing payments with any payment service provider (PSP).

## Features

- **API-level control over 3DS requests**: Choose how each authentication behaves: request frictionless flows for low-risk transactions, request challenges when stronger verification is needed, or use data share only flows to exchange risk signals without cardholder friction. You can also specify a reason for 3DS, such as liability shift, processing costs, or regulatory compliance, and let Stripe select the optimal flow automatically.

- **Observability into issuer responses**: Access the full 3DS protocol output, including the authentication result, Electronic Commerce Indicator (ECI), Directory Server (DS) Transaction ID, and the cryptogram. Use these signals to build your own authorization logic and analyze authentication performance across issuers and networks.

- **Support for complex payment scenarios**: Authenticate recurring payments, installments, and card-on-file setups with dedicated parameters. Use 3DS Requestor Initiated (3RI) authentication for transactions where the cardholder isn’t present, such as authenticating at booking time for travel or fulfilling split shipments, by referencing a previous authentication to obtain new cryptograms for subsequent authorizations.

- **Non-payment authentication**: Run 3DS authentication for account verification, card enrollment, or identity confirmation without an associated payment amount.

- **Stripe Connect compatibility**: Run standalone 3DS as a platform on behalf of your connected accounts.

## How it works

A standalone 3DS authentication follows these steps:

1. **Create** a 3DS Authentication object with the transaction amount, currency, card details, and browser information from the cardholder’s device.
1. **Fingerprint** (optional). If the issuer supports it, collect device fingerprint data through a client-side iframe or Stripe.js to improve risk assessment.
1. **Submit** the authentication to the issuer. Stripe communicates with the card network’s DS and the issuer’s Access Control Server (ACS).
1. **Challenge** (if required). Present the issuer’s challenge to the cardholder through an iframe or Stripe.js. Stripe sends a webhook when the challenge completes.
1. **Retrieve** the authentication outcome. On success, extract the cryptogram, ECI, and DS Transaction ID.

Once authenticated, submit the cryptogram as part of a payment authorization request. You can import 3DS results with Stripe or pass them to any PSP of your choice.

## Supported networks and availability

Standalone 3DS supports Visa, Mastercard, American Express, Discover, and Cartes Bancaires. It’s available to businesses on Interchange Plus pricing in all countries where Stripe supports card payments, except Malaysia and Thailand.

## Get started

To integrate standalone 3DS, contact your Account Executive, or register your interest below and we’ll be in touch.