Usage in AReq
Merchant’s assessment of the level of fraud risk for the specific authentication for both the Cardholder and the authentication being conducted.
Conditional inclusion — source text
Optional, but strongly recommended to include.
Format and scope
Type: Object · Length: Variable
Source components: 3DS Server. Channels: 01-APP, 02-BRW, 03-3RI. Categories: 01-PA, 02-NPA.
Object members
Nested presence rules apply when the parent is supplied. Consult the source for full conditions.
shipIndicator — Shipping Indicator
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Ship to the Cardholder’s billing address | Not tagged |
02 | Ship to another verified address on file with the Merchant | Not tagged |
03 | Ship to an address that is different than the Cardholder’s billing address | Not tagged |
04 | “Ship to Store” / Pick-up at a local store (Store address shall be populated in shipping address fields) | Not tagged |
05 | Digital goods (includes online services, electronic gift cards and redemption codes) | Not tagged |
06 | Travel and event tickets, not shipped | Not tagged |
07 | Other (for example, gaming, digital services not shipped, emedia subscriptions, etc.) | Not tagged |
08 | Pick-up and go delivery | Not tagged |
09 | Locker delivery (or other automated pick-up) | Not tagged |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
transChar — Transaction Characteristics
threeDSReqAuthData — 3DS Requestor
threeDSReqAuthMethod — 3DS Requestor
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 257
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 257
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b