---
title: "3D Secure 2 authentication"
description: "Integrate 3D Secure 2 authentication."
url: "https://docs.adyen.com/online-payments/3d-secure"
source_url: "https://docs.adyen.com/online-payments/3d-secure.md"
canonical: "https://docs.adyen.com/online-payments/3d-secure"
last_modified: "2024-01-18T13:44:00+01:00"
language: "en"
---

# 3D Secure 2 authentication

Integrate 3D Secure 2 authentication.

[View source](/online-payments/3d-secure.md)

##### Adyen Authentication Engine

Implementing 3D Secure 2 with Adyen lets you benefit from our [Authentication Engine](https://www.adyen.com/knowledge-hub/psd2-simplified-with-our-new-authentication-engine) that reduces regulatory complexity and optimizes authentication success.

3D Secure 2 is an authentication protocol that provides an additional layer of verification for card-not-present (CNP) transactions. We recommend that you use it to comply with regulations that require strong customer authentication for online payments such as [PSD2 SCA](/online-payments/psd2-sca-compliance-and-implementation-guide) in the [European Economic Area](https://en.wikipedia.org/wiki/European_Economic_Area) and the Payment Services Regulations 2017 in the UK, and to use [liability shift rules](/online-payments/3d-secure-for-regulation-compliance#3dsecurechargebackliabilityshiftrules).

## Implement 3D Secure 2

We support two 3D Secure 2 authentication implementations:

* **Native**: The card issuer performs the authentication within your website or mobile app using passive, biometric, and two-factor authentication approaches. For more information about the shopper experience, refer to [3D Secure 2 authentication flows](#authentication-flows).

* **Redirect**: Shoppers are redirected to the card issuer's site to provide additional authentication data, for example a password or an SMS verification code. The redirection might lead to lower conversion rates due to technical errors during the redirection, or shoppers dropping out of the authentication process.

How you implement depends on the server-side flow of your online payments integration:

* [**Sessions flow** ](/online-payments/build-your-integration#sessions-flow-a-single-api-request): You do not need additional configuration to support 3D Secure 2. The [Sessions flow integration](/online-payments/build-your-integration/sessions-flow) has built-in support for 3D Secure 2.
* [**Advanced flow** ](/online-payments/build-your-integration#advanced-flow-three-api-requests): Use the following guides to integrate with 3D Secure 2, selecting the platform (Web, iOS, or Android) and integration type (Drop-in or Components) that corresponds to your online payments integration. For an API-only integration, use the following guides to integrate with our pre-built 3D Secure 2 Component or Action Component.

###### [Native 3D Secure 2](/online-payments/3d-secure/native-3ds2)

[Provide a better shopper-experience by performing 3D Secure 2 authentication in your website or mobile app.](/online-payments/3d-secure/native-3ds2)

###### [Redirect 3D Secure 2](/online-payments/3d-secure/redirect-3ds2)

[The fastest way to support 3D Secure 2, redirecting the shopper to another site to verify the payment.](/online-payments/3d-secure/redirect-3ds2)

To build a Native 3D Secure 2 integration with **Checkout API v46 or earlier**, follow the [integration guide for earlier versions](/online-payments/3d-secure/native-3ds2/api-integration).

## 3D Secure 2 authentication flows

When you have implemented native 3D Secure, a transaction that qualifies for 3D Secure 2 can go through either a [frictionless flow](#frictionless-flow) or a [challenge flow](#challenge-flow), depending on the issuer's requirements.

### Frictionless flow

In a frictionless flow, the acquirer, issuer, and card scheme exchange all necessary information in the background through passive authentication using the shopper's device fingerprint. The transaction is completed without further shopper interaction.

[![](/user/pages/docs/02.online-payments/19.3d-secure/3ds2-component-frictionless.png)](/user/pages/docs/02.online-payments/19.3d-secure/3ds2-component-frictionless.png)

### Challenge flow

In a challenge flow, the issuer requires additional shopper interaction, either through biometrics, two-factor authentication, or similar methods based on [SCA authentication factors](/get-started-with-adyen/adyen-glossary/#strong-customer-authentication-sca).

[![](/user/pages/docs/02.online-payments/19.3d-secure/3ds2-component-challenge.png)](/user/pages/docs/02.online-payments/19.3d-secure/3ds2-component-challenge.png)

### Other 3D Secure flows

Besides the standard 3D Secure 2 implementation options, there are additional 3D Secure flows that you can use with or without an existing 3D Secure 2 integration.

###### [Authorization-only](/online-payments/3d-secure/authorize-mpidata)

[Use a third-party 3D Secure 2 provider, and perform the authorization request with Adyen.](/online-payments/3d-secure/authorize-mpidata)

###### [Data-only](/online-payments/3d-secure/data-only)

[Submit a 3D Secure 2 request without requesting for an authentication. Only available for Visa and Mastercard.](/online-payments/3d-secure/data-only)

###### [Standalone authentication](/online-payments/3d-secure/standalone-authentication)

[Submit a 3D Secure 2 request to perform authentication and receive authentication data you can use to authorize the payment later.](/online-payments/3d-secure/standalone-authentication)

## See also

* [PSD2 SCA compliance guide](/online-payments/psd2-sca-compliance-and-implementation-guide)
* [3D Secure for regulation compliance](/online-payments/3d-secure-for-regulation-compliance)
* [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)
