3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

Submit Authentication LabelsubmitAuthenticationLabel

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

Read in message CRes

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 ↓

Usage and conditions ↓Open in explorer →

Usage in CRes

Label to be used in the UI for the button that the Cardholder selects when they have completed the authentication. Note: This data element is not used for OOB authentication.

Conditional inclusion — source text

Required if ACS UI Type = 01, 02, or 03.

Related condition fields: acsUiType.

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

Format and scope

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

Source components
ACS
Device channels
01-APP
Message categories
01-PA, 02-NPA

Introduction tags

No field introduction version is tagged in the dataset. Introduction tags are curated metadata, not a full history of changes. An absent value tag does not establish when that value was introduced.

Compare source editions and understand coverage.

Sources and review status

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

This page describes the published source edition. Scheme programme requirements are not inferred from it.

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