## TL;DR

Setting up Adyen 3DS means enabling 3D Secure 2 in your Adyen configuration, integrating the challenge flow into your checkout, and deciding your SCA exemption policy. Use Adyen's test cards to walk frictionless approvals, challenges, and failures before enabling in production. Start in a monitoring mode where you log authentication outcomes without blocking, then enforce once the data looks right. Document which transaction types are exempted and why, because auditors and the card networks both care.

## The query

```text
adyen 3ds
```

## Use this when

- First-time 3D Secure setup on Adyen
- Adyen 3DS configuration checklist
- Going live with Adyen authentication

## Not for

- Debugging live 3DS failures (different workflow)
- Migrating from another gateway's 3DS

## Steps

1. Enable 3D Secure 2 in the Adyen customer area.
   Expected output: The account is 3DS-capable.
2. Integrate the 3DS2 challenge handling into your checkout (redirect or native).
   Expected output: Challenges can complete.
3. Define your exemption strategy: low-value, recurring MIT, trusted beneficiaries.
   Expected output: The policy is explicit before go-live.
4. Test all outcomes with Adyen 3DS test cards.
   Expected output: Frictionless, challenge, and failure paths all work.
5. Monitor authentication rates for a week before enforcing.
   Expected output: The rollout is data-driven, not hopeful.

## Variant phrasings

### Adyen 3DS setup

### enable 3D Secure Adyen

### Adyen 3DS2 configuration

## Root cause

Adyen 3DS setup is configuration plus integration: the account setting enables the protocol, but your checkout must handle the challenge handoff or authentications stall. The monitoring-first rollout exists because enforcement without data blocks legitimate revenue.

## Edge cases

- Native 3DS2 in mobile SDKs needs the SDK integration, not just the API flag
- Exemptions are requests, not guarantees; issuers can still challenge

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_IP86nCc1aB5KVKFXxUt2yg