3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

3DS Requestor App URLthreeDSRequestorAppURL

3DS Requestor App declaring its URL within the CReq message so that the Authentication App can call the 3DS Requestor App after OOB authentication has occurred. Note: When providing the 3DS Requestor App URL, the 3DS Requestor needs to properly register the URL with the Operating System.

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
CReqConditional

Conditional inclusion — source text

Required in all CReq messages if 3DS Requestor App URL is provided by the 3DS SDK.

Format and scope

Type: String · Length: Variable, maximum 2048 · Maximum length: 2048

Source components
3DS SDK
Device channels
01-APP
Message categories
01-PA, 02-NPA

Version history

Field introduction tag: 2.2.0. 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 189

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