Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Static Passcode | Not tagged |
02 | SMS OTP | Not tagged |
03 | Key fob or EMV card reader OTP | Not tagged |
04 | App OTP | Not tagged |
05 | OTP Other | Not tagged |
06 | KBA | Not tagged |
07 | OOB Biometrics | Not tagged |
08 | OOB Login | Not tagged |
09 | OOB Other | Not tagged |
10 | Other | Not tagged |
11 | Push Confirmation | 2.2.0 |
12 | Decoupled | 2.3.1.1 |
13 | WebAuthn | 2.3.1.1 |
14 | SPC | 2.3.1.1 |
15 | Behavioural biometrics | 2.3.1.1 |
16 | Electronic ID | 2.3.1.1 |
17–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) | Reserved |
80–99 | Reserved for DS use If SDK Type = 02 and Split-SDK Type/Limited Indicator = Y, a value of 01 or 06 is not valid. | Reserved |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
Message inclusion
Baseline inclusion. Effective requirements depend on transaction context. Check the field’s conditions and FAQ qualifications; select channel and category in the explorer.
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
Version history
No field introduction version is tagged in the dataset. Introduction tags are curated metadata, not a full history of changes. Compare versions and understand coverage.
Source and review status
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 208, 209
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
6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6bOfficial EMVCo specifications · Methodology and coverage limits