3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

ACS URLacsURL

Fully Qualified URL of the ACS to be used for the challenge. 01-APP—3DS SDK will send the Challenge Request to this URL 02-BRW—3DS Requestor will post the CReq to this URL via the challenge iframe. For App-based, this data element is contained within the ACS Signed Content JWS Object. For Browser-based, this data element is present as its own object.

Read in message: ARes

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
AResConditional

Conditional inclusion — source text

• For 01- APP, see ACS Signed Content. • For 02- BRW, required if Transaction Status = C.

Related condition fields: transStatus.

Format and scope

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

Source components
ACS
Device channels
01-APP, 02-BRW
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 207

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