Usage in AReq
Additional transaction information in case of multiple transactions or Merchants.
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.
merchantAmount — Merchant Amount
merchantCurrency — Merchant Currency Code
merchantExponent — Merchant Currency Exponent
sellerId — Seller ID
avValidityTime — AV Validity Time
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 260
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 260
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b