3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Challenge Information HeaderchallengeInfoHeader

Challenge Information Header in Challenge Response (CRes).

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

Baseline in CRes 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 CRes

Header text that for the challenge information screen that is being presented.

Conditional inclusion — source text

See Table A.20 for presence conditions.

Format and scope

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

Source components: ACS. Channels: 01-APP. Categories: 01-PA, 02-NPA.

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 238

Scoped FAQ qualifications

  • FAQ 26 — 2.2.0

    App-based CRes, selected native UI template

    Table A.1 optionality does not override the UI elements required by Table A.18. Challenge Information Label must be present for the templates discussed; it may contain a single space.

    EMVCo_3DS_Specification_FAQs_8-April-2026.pdf, page 9

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 238

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b