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 has been entered in the Native UI text field; AND • Challenge Cancelation Indicator is not present; AND • Resend Challenge Information Code is not present; AND • Challenge Additional Code is not present See Table A.16 for Challenge Data Entry conditions.
Related condition fields: acsUiType.
Format and scope
Type: String · Length: Variable, maximum 45 · Maximum length: 45
- Source components
- 3DS SDK
- Device channels
- 01-APP
- Message categories
- 01-PA, 02-NPA
Reference notes
- Contains comma-separated selection keys. v2.2.0 has max 45 chars total. If challengeSelectInfo keys exceed this, Cardholder multi-selection cannot be returned. — FAQ 62 (EMVCo FAQ)
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 233, 234
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