3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

3DS Requestor Challenge IndicatorthreeDSRequestorChallengeInd

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).

Explore this field with transaction context

Allowed and reserved values

ValueMeaningIntroduction tag
01No preferenceNot tagged
02No challenge requestedNot tagged
03Challenge requested (3DS Requestor preference)Not tagged
04Challenge requested (Mandate)Not tagged
05No challenge requested (transactional risk analysis is already performed)2.2.0
06No challenge requested (Data share only)2.2.0
07No challenge requested (strong consumer authentication is already performed)2.2.0
08No challenge requested (use Trust List exemption if no challenge required)2.2.0
09Challenge requested (Trust List prompt requested if challenge required)2.2.0
10No challenge requested (use low value exemption)2.3.1.1
11No challenge requested (Secure corporate payment exemption)2.3.1.1
12Challenge requested (Device Binding prompt requested if challenge required)2.3.1.1
13Challenge requested (Issuer requested)2.3.1.1
14Challenge requested (Merchant-initiated transactions)2.3.1.1
15–79Reserved for EMVCo future use (values invalid until defined by EMVCo)Reserved
80–99Reserved for DS useReserved

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.

MessageBaseline inclusion
AReqOptional

Format and scope

Type: Array · Array item type: String · Minimum items: 1 · Maximum items: 2

Source components
3DS Server, DS
Device channels
01-APP, 02-BRW, 03-3RI
Message categories
01-PA, 02-NPA

Omission or default behaviour

If the element is not provided, the expected action is that the ACS would interpret as 01 = No preference.

Reference 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)

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 190, 191, 192

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

6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b

Official EMVCo specifications · Methodology and coverage limits