3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

Authentication MethodauthenticationMethod

Source edition: Core 2.3.1.1 · Type: Array

Read in message AResRReq

Baseline in ARes Conditional

Same classification across the remaining channels and categories. • Required in the ARes message if Transaction Status = C or D. • Required in the RReq message if Transaction Status = Y or N. Usage and conditions ↓

Jump to values ↓Open in explorer →

Field value definitions

Field-wide definitions. Check message-specific restrictions in usage and conditions.

CodeMeaning
01Static Passcode
02SMS OTP
03Key fob or EMV card reader OTP
04App OTP
05OTP Other
06KBA
07OOB Biometrics
08OOB Login
09OOB Other
10Other
11Push ConfirmationIntroduction tag: 2.2.0
12DecoupledIntroduction tag: 2.3.1.1
13WebAuthnIntroduction tag: 2.3.1.1
14SPCIntroduction tag: 2.3.1.1
15Behavioural biometricsIntroduction tag: 2.3.1.1
16Electronic IDIntroduction tag: 2.3.1.1

Reserved values

CodeMeaning
17–79Reserved for EMVCo future use (values invalid until defined by EMVCo)
80–99Reserved for DS use If SDK Type = 02 and Split-SDK Type/Limited Indicator = Y, a value of 01 or 06 is not valid.

Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 208, 209. Read usage and conditions.

Usage in ARes

Indicates the list of authentication types the Issuer will use to challenge the Cardholder, when in the ARes message or what was used by the ACS when in the RReq message. Note: For 03-3RI, only present for Decoupled Authentication.

Conditional inclusion — source text

• Required in the ARes message if Transaction Status = C or D. • Required in the RReq message if Transaction Status = Y or N.

Related condition fields: transStatus.

Format and scope

Type: Array

Source components
ACS
Device channels
01-APP, 02-BRW, 03-3RI
Message categories
01-PA, 02-NPA

Introduction tags

No field introduction version is tagged in the dataset. Introduction tags are curated metadata, not a full history of changes. An absent value tag does not establish when that value was introduced.

Compare source editions and understand coverage.

Sources and review status

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 208, 209

This page describes the published source edition. Scheme programme requirements are not inferred from it.

Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.

Source document fingerprint

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf

6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b

Official EMVCo specifications · Methodology and coverage limits