3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

SDK App IDsdkAppID

Universally unique ID created upon all installations of the 3DS Requestor App on a Consumer Device. This will be newly generated and stored by the 3DS SDK for each installation. Note: In case of Split- SDK/Browser, the SDK App ID value is not reliable, and may change for each 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

Format and scope

Type: String · Length: 36 characters · Minimum length: 36 · Maximum length: 36

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

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