3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Merchant Category Codemcc

Merchant Category Code in Authentication Request (AReq).

Source edition: Core 2.3.1.1 · Type: String · Length: 4 characters · Minimum length: 4 · Maximum length: 4

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 ↓

Jump to values ↓Explore in context →

Valid values

CodeMeaning
Payment System-specificThis value correlates to the Merchant Category Code as defined by each Payment System or DS.

Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 256. Read usage and conditions.

Usage in AReq

DS-specific code describing the Merchant's type of business, product or service.

Conditional inclusion — source text

Optional but strongly recommended to include for 02-NPA if the Merchant is also the 3DS Requestor.

Format and scope

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

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 256

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 256

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b