3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

SPC Transaction DataspcTransData

SPC Transaction Data in Authentication Response (ARes).

Source edition: Core 2.3.1.1 · Type: Object

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

Information that the 3DS Requestor passes in the SPC API for display in the Smart Modal Window

Conditional inclusion — source text

Required if Transaction Status = S

Related condition fields: transStatus.

Format and scope

Type: Object

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

Object members

Nested presence rules apply when the parent is supplied. Consult the source for full conditions.

challenge — Challenge

challengeInfoText — Challenge Information Text

currency — Currency

displayName — Display Name

icon — Icon

issuerImageSpc — Issuer Image SPC

payeeName — Payee Name

payeeOrigin — Payee Origin

psImageSpc — Payment System Image SPC

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

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

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 285

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b