Usage in OReq
This data element provides additional information enabling the recipient to reference a prior transaction.
Format and scope
Type: Object
Source components: DS. Channels: Not specified. Categories: Not specified.
Object members
Nested presence rules apply when the parent is supplied. Consult the source for full conditions.
opStatus — Operation Message
| 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) | Not tagged |
80–99 | Reserved for DS use | Not tagged |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 268
Scoped FAQ qualifications
- FAQ 27 — Applicable object-bearing protocol versions
Only when the parent JSON object is present
Evaluate nested presence conditions when the parent object is present. In multiTransaction, merchantList is required when the object is supplied; merchantAmount remains optional.
- FAQ 73 — Applicable object-bearing protocol versions
An optional or conditionally optional field is sent empty
An empty optional field produces error 203 under Req 309. When the empty JSON object contains mandatory data, error 201 may be returned.
Transaction context
This reference covers the published source edition. Use the explorer to inspect this field and any applicable transaction conditions. Scheme programme requirements are not inferred from the protocol edition.
Sources and related references
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 268
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b