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 |
|---|---|
| AReq | Required |
| ARes | Required |
| CReq | Required |
| CRes | Required |
| ORes | Conditional |
| PReq | Required |
| PRes | Required |
| RReq | Required |
| RRes | Required |
| Erro | Conditional |
Conditional inclusion — source text
• Required in the Error Message if available (e.g., can be obtained from a message or is being generated). • Required in the ORes message for a 3DS Server receiving an OReq message.
Format and scope
Type: String · Length: 36 characters · Minimum length: 36 · Maximum length: 36
- 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 196
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