Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
Y | No Data Entry | Not tagged |
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.
| Message | Baseline inclusion |
|---|---|
| CReq | Conditional |
Conditional inclusion — source text
Required if: • ACS UI Type = 01, 02, or 03, AND • Challenge Data Entry is not present, AND • Challenge Data Entry 2 is not present when Challenge Entry Box 2 object was provided by the ACS, AND • Challenge Cancelation Indicator is not present, AND • Resend Challenge Information Code is not present, AND • Challenge Additional Code is not present
Related condition fields: acsUiType.
Format and scope
Type: String
- Source components
- 3DS SDK
- Device channels
- 01-APP
- Message categories
- 01-PA, 02-NPA
Version history
Field introduction tag: 2.2.0. 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 240, 241
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