3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

ACS UI TypeacsUiType

ACS UI Type in Challenge Response (CRes).

Source edition: Core 2.3.1.1 · Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2

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 ↓

Jump to values ↓Explore in context →

Valid values

CodeMeaning
01Text
02Single Select
03Multi Select
04OOB
05HTML
06HTML OOB
07Information

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

Reserved values

CodeMeaning
08–79Reserved for EMVCo future use (values invalid until defined by EMVCo)
80–99Reserved for DS use

Usage in CRes

User interface type that the 3DS SDK will render, which includes the specific data mapping and requirements.

Conditional inclusion — source text

Required except for the Final CRes message.

Format and scope

Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2

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 206

Scoped FAQ qualifications

  • FAQ 31 — Applicable app-based protocol versions

    App-based CRes; distinguish final from intermediate messages

    UI-related elements, including acsUiType, are supplied during the challenge. The final CRes excludes UI-related elements; use Table B.5 for final-message content.

    EMVCo_3DS_Specification_FAQs_8-April-2026.pdf, page 11

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 206

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b