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 | Conditional |
Conditional inclusion — source text
Required unless market or regional mandate restricts sending this information.
Format and scope
Type: String · Length: Variable, maximum 45 · Maximum length: 45
- Source components
- 3DS Server
- Device channels
- 02-BRW
- Message categories
- 01-PA, 02-NPA
Reference notes
- IPv4 representation per RFC 791, IPv6 representation per RFC 4291 Section 2.2. Should be the public IP address of the Browser connecting to the 3DS Requestor—key for ACS risk analysis. — FAQ 25 (EMVCo FAQ)
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 211
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