Valid values
| Code | Meaning |
|---|---|
01 | No preference |
02 | No challenge requested |
03 | Challenge requested (3DS Requestor preference) |
04 | Challenge requested (Mandate) |
05 | No challenge requested (transactional risk analysis is already performed) |
06 | No challenge requested (Data share only) |
07 | No challenge requested (strong consumer authentication is already performed) |
08 | No challenge requested (use Trust List exemption if no challenge required) |
09 | Challenge requested (Trust List prompt requested if challenge required) |
10 | No challenge requested (use low value exemption) |
11 | No challenge requested (Secure corporate payment exemption) |
12 | Challenge requested (Device Binding prompt requested if challenge required) |
13 | Challenge requested (Issuer requested) |
14 | Challenge requested (Merchant-initiated transactions) |
Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 190, 191, 192. Read usage and conditions.
Reserved values
| Code | Meaning |
|---|---|
15–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) |
80–99 | Reserved for DS use |
Usage in AReq
For 01-PA, a 3DS Requestor may have concerns about the transaction, and request a challenge. For 02-NPA, a challenge may be necessary when adding a new card to a wallet. Note: When providing two preferences, the 3DS Requestor ensures that they are in preference order and are not conflicting. For example, 02 = No challenge requested and 04 = Challenge requested (Mandate).
When omitted
If the element is not provided, the expected action is that the ACS would interpret as 01 = No preference.
Format and scope
Type: Array · Array item type: String · Minimum items: 1 · Maximum items: 2
Source components: 3DS Server, DS. Channels: 01-APP, 02-BRW, 03-3RI. Categories: 01-PA, 02-NPA.
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 190, 191, 192
Related FAQ notes
- Value '13' (Challenge requested by Issuer) is used after a 'soft decline' from the Issuer during authorization. — FAQ 40 (EMVCo FAQ)
- The exemption in transChallengeExemption may differ from what was requested—ACS may apply a different exemption or apply one even if not requested. — FAQ 55 (EMVCo FAQ)
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 190, 191, 192
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b