Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Text | Not tagged |
02 | Single Select | Not tagged |
03 | Multi Select | Not tagged |
04 | OOB | Not tagged |
05 | HTML | Not tagged |
06 | HTML OOB | Not tagged |
07 | Information | Not tagged |
08–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) | Reserved |
80–99 | Reserved for DS use | 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.
| Message | Baseline inclusion |
|---|---|
| CRes | Conditional |
Conditional inclusion — source text
Required except for the Final CRes message.
Scoped FAQ qualifications
- FAQ 31 — Applicable app-based protocol versions
App-based CRes; distinguish final from intermediate messages
UI-related elements, including acsUiType, are supplied during the challenge. The final CRes excludes UI-related elements; use Table B.5 for final-message content.
Format and scope
Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2
- Source components
- ACS
- Device channels
- 01-APP
- Message categories
- 01-PA, 02-NPA
Version history
Field introduction tag: 2.1.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 206
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