3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Challenge Data Entry 2challengeDataEntryTwo

Contains the data that the Cardholder entered in the Native UI text field. Note: Supported only for ACS UI Type = 01.

Explore this field with transaction context

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
CReqConditional

Conditional inclusion — source text

Required if: • ACS UI Type = 01; AND • Challenge Entry Box 2 object is provided by the ACS; AND • Challenge data has been entered in the second entry box/UI; AND • Challenge Cancelation Indicator is not present; AND • Resend Challenge Information Code is not present; AND • Challenge Additional Code is not present See Table A.16 for Challenge Data Entry conditions.

Related condition fields: acsUiType.

Format and scope

Type: String · Length: Variable, maximum 45 · Maximum length: 45

Source components
3DS SDK
Device channels
01-APP
Message categories
01-PA, 02-NPA

Version history

Field introduction tag: 2.3.1.1. 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 234, 235

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