3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Challenge Data Entry 2challengeDataEntryTwo

Challenge Data Entry 2 in Challenge Request (CReq).

Source edition: Core 2.3.1.1 · Type: String · Length: Variable, maximum 45 · Maximum length: 45

Baseline in CReq Conditional

Varies by context. Requirement or applicability varies by channel or message category. Select a specific context to resolve it. Usage and conditions ↓

Explore in context →

Usage in CReq

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

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. Channels: 01-APP. Categories: 01-PA, 02-NPA.

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 234, 235

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.

Explore in context →

Sources and related references

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.

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b