Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Successfully received messages | Not tagged |
02 | Message sequence is broken | Not tagged |
03 | Requested action is not supported or not executed by the 3DS Server or ACS when OReq message was received | Not tagged |
04–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 |
|---|---|
| ORes | Required |
Format and scope
Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2
- Source components
- 3DS Server, ACS
- Device channels
- Not specified
- Message categories
- Not specified
Version history
Field introduction tag: 2.3.1.1. 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 267
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