3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Acquirer Merchant IDacquirerMerchantID

Acquirer Merchant ID in Authentication Request (AReq).

Source edition: Core 2.3.1.1 · Type: String · Length: Variable, maximum 35 · Maximum length: 35

Baseline in AReq Payment · 01-PARequiredNon-payment · 02-NPAOptional

Varies by context. Requirement or applicability varies by channel or message category. Select a specific context to resolve it. Usage and conditions ↓

Explore in context →

Usage in AReq

Acquirer-assigned Merchant identifier. This may be the same value that is used in authorisation requests sent on behalf of the 3DS Requestor and is represented in ISO 8583-1 formatting requirements.

Format and scope

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

Source components: 3DS Server. Channels: 01-APP, 02-BRW, 03-3RI. Categories: 01-PA, 02-NPA.

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 200

Transaction context

This reference covers the published source edition. Use the explorer to inspect this field and any applicable transaction conditions. Scheme programme requirements are not inferred from the protocol edition.

Explore in context →

Sources and related references

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 200

Source review status: extracted. Carried-forward material has not acquired a new verification claim.

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b