## TL;DR

When a 3D Secure payment on Adyen fails or stalls, the cause is usually a dropped challenge redirect, missing browser data, or an issuer decline after authentication. Check the payment result and refusal reason in the Adyen dashboard, confirm your integration passes the required 3DS data, and verify the challenge return URL works. Retrying the same payment without fixing the data fails identically; fix the integration, then retry. Log the authentication result on every attempt so support can see what happened.

## The query

```text
3d secure adyen
```

## Use this when

- Adyen card payments failing at 3D Secure
- Challenge flow not completing on Adyen
- Reading Adyen 3DS refusal reasons

## Not for

- Non-card Adyen payment methods (iDEAL, SEPA)
- Payout or settlement issues

## Steps

1. Open the payment in the Adyen dashboard and read the 3DS result and refusal reason.
   Expected output: The failure is classified.
2. Confirm your integration sends the required browser and cardholder data.
   Expected output: Missing data is the most common fixable cause.
3. Verify the challenge redirect or native flow completes and returns to your site.
   Expected output: Stalled challenges are an integration bug, not a decline.
4. Fix the data or flow issue, then retry the payment.
   Expected output: The retry has a chance to succeed.
5. Log transStatus and refusal reasons on every 3DS attempt.
   Expected output: Support debugs from data, not guesses.

## Variant phrasings

### Adyen 3D Secure payment failed

### 3DS challenge Adyen not working

### Adyen authentication failed card payment

## Root cause

Adyen orchestrates the 3DS conversation between your checkout, the card networks, and the issuer; failures happen at whichever handoff is misconfigured. The dashboard's refusal reason names the handoff, which is why reading it beats retrying blindly.

## Edge cases

- Test cards simulate specific 3DS outcomes; use them to reproduce before debugging production
- Liability shift only applies when authentication actually completed

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tn5pfynx4C_-yqZpe2XkMQ