3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

SDK Ephemeral Public Key (Qc)sdkEphemPubKey

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

Read in message AReq

Baseline in AReq Required

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 and conditions

Public key component of the ephemeral key pair generated by the 3DS SDK and used to establish session keys between the 3DS SDK and ACS. In AReq, this data element is present as its own object. In ARes, this data element is contained within the ACS Signed Content JWS Object. See Section 6.2.3.1 for additional detail.

Conditional inclusion — source text

For the ARes message, see ACS Signed Content.

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 256 · Maximum length: 256

Source components
3DS SDK
Device channels
01-APP
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.

sdkEphemPubKey — SDK Ephemeral

sdkMaxTimeout — SDK Maximum

sdkReferenceNum — SDK Reference

Message inclusion

Baseline inclusion. Effective requirements depend on transaction context. Check the field’s conditions and FAQ qualifications; select channel and category in the explorer.

MessageBaseline inclusion
AReqRequired

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 281

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