3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Split-SDK Server IDsplitSdkServerID

DS assigned Split-SDK Server identifier. Each DS can provide a unique ID to each Split-SDK Server on an individual basis.

Explore this field with transaction context

Allowed and reserved values

ValueMeaningIntroduction tag
DS-specificAny individual DS may impose specific formatting and character requirements on the contents of this field.Not tagged

Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.

This is a contained member of sdkServerSignedContent, not a separate top-level message field. Read the parent’s requirements.

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
AReqConditional

Conditional inclusion — source text

See SDK Server Signed Content.

Format and scope

Type: String · Length: Variable, maximum 32 characters · Maximum length: 32

Source components
Split-SDK Server
Device channels
01-APP
Message categories
01-PA, 02-NPA

Reference notes

  • Conveyed within the sdkServerSignedContent JWS object rather than as a top-level message field. See Section 6.2.2.3.

Version history

Field introduction tag: 2.3.1.1. Introduction tags are curated metadata, not a full history of changes. Compare versions and understand coverage.

Source and review status

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.

Source document fingerprint

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf

6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b

Official EMVCo specifications · Methodology and coverage limits