---
title: "Get the 3DS2 authentication result"
method: POST
path: "/retrieve3ds2Result"
tags: ["Payments"]
---

# Get the 3DS2 authentication result

`POST /retrieve3ds2Result`

Retrieves the `threeDS2Result` after doing a 3D Secure 2 authentication only.

## Request body

- ThreeDS2ResultRequest
  - `merchantAccount` string, required — The merchant account identifier, with which you want to process the transaction.
  - `pspReference` string, required — The pspReference returned in the /authorise call.

## Response `200`

OK - the request has succeeded.

- ThreeDS2ResultResponse
  - `threeDS2Result` ThreeDS2Result
    - `authenticationValue` string — The `authenticationValue` value as defined in the 3D Secure 2 specification.
    - `cavvAlgorithm` string — The algorithm used by the ACS to calculate the authentication value, only for Cartes Bancaires integrations.
    - `challengeCancel` '01' | '02' | '03' | '04' | '05' | '06' | '07' — Indicator informing the Access Control Server (ACS) and the Directory Server (DS) that the authentication has been cancelled. For possible values, refer to [3D Secure API reference](https://docs.adyen.com/online-payments/3d-secure/api-reference#mpidata).
    - `dsTransID` string — The `dsTransID` value as defined in the 3D Secure 2 specification.
    - `eci` string — The `eci` value as defined in the 3D Secure 2 specification.
    - `exemptionIndicator` 'lowValue' | 'secureCorporate' | 'trustedBeneficiary' | 'transactionRiskAnalysis' — Indicates the exemption type that was applied by the issuer to the authentication, if exemption applied. Allowed values: * `lowValue` * `secureCorporate` * `trustedBeneficiary` * `transactionRiskAnalysis`
    - `messageVersion` string — The `messageVersion` value as defined in the 3D Secure 2 specification.
    - `riskScore` string — Risk score calculated by Cartes Bancaires Directory Server (DS).
    - `threeDSRequestorChallengeInd` '01' | '02' | '03' | '04' | '05' | '06' — Indicates whether a challenge is requested for this transaction. Possible values: * **01** — No preference * **02** — No challenge requested * **03** — Challenge requested (3DS Requestor preference) * **04** — Challenge requested (Mandate) * **05** — No challenge (transactional risk analysis is already performed) * **06** — Data Only
    - `threeDSServerTransID` string — The `threeDSServerTransID` value as defined in the 3D Secure 2 specification.
    - `timestamp` string — The `timestamp` value of the 3D Secure 2 authentication.
    - `transStatus` string — The `transStatus` value as defined in the 3D Secure 2 specification.
    - `transStatusReason` string — Provides information on why the `transStatus` field has the specified value. For possible values, refer to [our docs](https://docs.adyen.com/online-payments/3d-secure/api-reference#possible-transstatusreason-values).
    - `whiteListStatus` string — The `whiteListStatus` value as defined in the 3D Secure 2 specification.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

---

[API](https://skmtc.net/adyen/apis/adyen-payment-api.md) · [All operations](https://skmtc.net/adyen/apis/adyen-payment-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/adyen-payment-api/versions/82f2803ec1b9/schema)