3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

Broadcast InformationbroadInfo

Source edition: Core 2.3.1.1 · Type: Object · Length: Variable, maximum 4096 · Maximum length: 4096

Read in message AReqARes

Baseline in AReq Optional

Optional across all channels and categories. Usage and conditions ↓

Usage and conditions ↓Open in explorer →

Usage in AReq

Structured information sent between the 3DS Server, the DS and the ACS.

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, maximum 4096 · Maximum length: 4096

Source components
3DS Server, ACS, DS
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.

category — Category

CodeMeaning
01General
02Certificate expiry
03Fraud alert
04Operational alert
05Transactional data
06Other
07–79Reserved for EMVCo future use (values invalid until defined by EMVCo)
80–99Reserved for DS use

description — Description

expDate — Expiry Date

severity — Severity

CodeMeaning
01Critical
02Major
03Minor
04Informational

recipients — Recipient(s)

CodeMeaning
013DS SDK
023DS Server
03DS
04ACS

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 210

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