3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Challenge HTML Data EntrychallengeHTMLDataEntry

Data that the Cardholder entered into the HTML UI. Note: ACS UI Types 01, 02, 03, 04 and 07 are not supported.

Read in message: CReq

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 = 05 or 06, AND • Challenge Cancelation Indicator is not present, AND • OOB Continuatio n Indicator is NOT = 02

Related condition fields: acsUiType.

Format and scope

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

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

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 238

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