3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Challenge No EntrychallengeNoEntry

Challenge No Entry in Challenge Request (CReq).

Source edition: Core 2.3.1.1 · Type: String

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 ↓

Jump to values ↓Explore in context →

Valid values

CodeMeaning
YNo Data Entry

Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 240, 241. Read usage and conditions.

Usage in CReq

Indicator informing that the Cardholder submits an empty response (no data entered in the UI). Note: If present this field contains the value Y.

Conditional inclusion — source text

Required if: • ACS UI Type = 01, 02, or 03, AND • Challenge Data Entry is not present, AND • Challenge Data Entry 2 is not present when Challenge Entry Box 2 object was provided by the ACS, AND • Challenge Cancelation Indicator is not present, AND • Resend Challenge Information Code is not present, AND • Challenge Additional Code is not present

Related condition fields: acsUiType.

Format and scope

Type: String

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 240, 241

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 240, 241

Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b