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 |
|---|---|
| CRes | Conditional |
Conditional inclusion — source text
See Table A.20 for presence conditions.
Scoped FAQ qualifications
- FAQ 26 — 2.2.0
App-based CRes, selected native UI template
Table A.1 optionality does not override the UI elements required by Table A.18. Challenge Information Label must be present for the templates discussed; it may contain a single space.
Format and scope
Type: Array
- Source components
- ACS
- Device channels
- 01-APP
- Message categories
- 01-PA, 02-NPA
Reference notes
- v2.2.0 requires total key length ≤45 characters across all options (keys are comma-joined in challengeDataEntry). v2.3.1.1 allows max 8 options with 4-char keys and 45-char values. — 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 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