Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
01 | RReq received for further processing | Not tagged |
02 | CReq not sent to ACS by 3DS Requestor (3DS Server or 3DS Requestor opted out of the challenge) | Not tagged |
03 | ARes (Transaction Status = C or D) not delivered to the 3DS Requestor due to technical error | Not tagged |
04 | 3DS Server will process Decoupled Authentication in a subsequent authentication | Not tagged |
05–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 |
|---|---|
| RRes | Required |
Format and scope
Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2
- Source components
- 3DS Server
- 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 279
Source review status: extracted. 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