3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

Cardholder Information TextcardholderInfo

Source edition: Core 2.3.1.1 · Type: Object · Length: Variable

Read in message AResRReq

Baseline in RReq Optional

Optional across all channels and categories. Usage and conditions ↓

Usage and conditions ↓Open in explorer →

Usage in RReq

Text provided by the ACS/Issuer to Cardholder during a Frictionless or Decoupled transaction. The Issuer can provide information to Cardholder. For example, “Additional authentication is needed for this transaction, please contact (Issuer Name) at xxx-xxx-xxxx” with optionally the Issuer and Payment System images. Refer to A.20 for UI example.

Conditional inclusion — source text

Required if ACS Decoupled Confirmation Indicator = Y Otherwise, Optional for the ACS.

Related condition fields: acsDecConInd.

Scoped FAQ qualifications

  • FAQ 27 — Applicable object-bearing protocol versions

    Only when the parent JSON object is present

    Evaluate nested presence conditions when the parent object is present. In multiTransaction, merchantList is required when the object is supplied; merchantAmount remains optional.

    EMVCo_3DS_Specification_FAQs_8-April-2026.pdf, page 9

  • FAQ 73 — Applicable object-bearing protocol versions

    An optional or conditionally optional field is sent empty

    An empty optional field produces error 203 under Req 309. When the empty JSON object contains mandatory data, error 201 may be returned.

    EMVCo_3DS_Specification_FAQs_8-April-2026.pdf, page 23

Format and scope

Type: Object · Length: Variable

Source components
ACS
Device channels
01-APP, 02-BRW, 03-3RI
Message categories
01-PA, 02-NPA

Object members

Nested presence rules apply when the parent object is supplied. These structures include carried-forward curation; consult the source for full conditions.

source — Source

CodeMeaning
013DS Server
02DS
03ACS

Introduction tags

Field introduction tag: 2.1.0. 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 225

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