Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
03 | Instalment transaction | Not tagged |
04 | Add card | Not tagged |
05 | Maintain card | Not tagged |
06 | Cardholder verification as part of EMV token ID&V | Not tagged |
07 | Billing Agreement | Not tagged |
08 | Split shipment | Not tagged |
09 | Delayed shipment | Not tagged |
10 | Split payment | Not tagged |
11–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 |
|---|---|
| AReq | Required |
Format and scope
Type: String
- Source components
- 3DS Server
- Device channels
- 01-APP, 02-BRW
- 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 189, 190
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