3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Message Version NumbermessageVersion

Protocol Version identifier This shall be the Protocol Version Number of the specification used by the system creating this message. The Message Version Number is set by the 3DS Server which originates the protocol with the AReq message. The Message Version Number does not change during a 3DS transaction.

Explore this field with transaction context

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
AResRequired
CReqRequired
CResRequired
OReqRequired
OResRequired
PReqRequired
PResRequired
RReqRequired
RResRequired
ErroRequired

Format and scope

Type: String · Length: Variable, 5–8 characters · Minimum length: 5 · Maximum length: 8

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

Version history

No field introduction version is tagged in the dataset. 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 260

Source review status: extracted. 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