3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Transaction TypetransType

Transaction Type in Authentication Request (AReq).

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

Baseline in AReq Conditional

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
01Goods/ Service Purchase
03Check Acceptance
10Account Funding
11Quasi-Cash Transaction
28Prepaid Activation and Load Note: Values derived from ISO 8583-1.

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

Usage in AReq

Identifies the type of transaction being authenticated.

Conditional inclusion — source text

This field is required in some markets (e.g., for Merchants in Brazil). Otherwise, optional.

Format and scope

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

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

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

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 292

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b