Allowed and reserved values
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Card authentication failed | Not tagged |
02 | Unknown device | Not tagged |
03 | Unsupported device | Not tagged |
04 | Exceeds authentication frequency limit | Not tagged |
05 | Expired card | Not tagged |
06 | Invalid card number | Not tagged |
07 | Invalid transaction | Not tagged |
08 | No card record | Not tagged |
09 | Security failure | Not tagged |
10 | Stolen card | Not tagged |
11 | Suspected fraud | Not tagged |
12 | Transaction not permitted to Cardholder | Not tagged |
13 | Cardholder not enrolled in service | Not tagged |
14 | Transaction timed out at the ACS | Not tagged |
15 | Low confidence | Not tagged |
16 | Medium confidence | Not tagged |
17 | High confidence | Not tagged |
18 | Very high confidence | Not tagged |
19 | Exceeds ACS maximum challenges | Not tagged |
20 | Non-Payment transaction not supported | Not tagged |
21 | 3RI transaction not supported | Not tagged |
22 | ACS technical issue | 2.2.0 |
23 | Decoupled Authentication required by ACS but not requested by 3DS Requestor | 2.2.0 |
24 | 3DS Requestor Decoupled Max Expiry Time exceeded | 2.2.0 |
25 | Decoupled Authentication was provided insufficient time to authenticate Cardholder. ACS will not make attempt | 2.2.0 |
26 | Authentication attempted but not performed by the Cardholder | 2.2.0 |
27 | Preferred Authentication Method not supported | 2.3.1.1 |
28 | Validation of content security policy failed | 2.3.1.1 |
29 | Authentication attempted but not completed by the Cardholder. Fall back to Decoupled Authentication | 2.3.1.1 |
30 | Authentication completed successfully but additional authentication of the Cardholder required. Reinitiate as Decoupled Authentication | 2.3.1.1 |
31–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) | Reserved |
80–99 | Reserved for DS use | Reserved |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
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.
Conditional inclusion — source text
For 01-PA, required if Transaction Status = N, U, or R. For 02-NPA, requirements for the presence and values of Transaction Status are DS-specific.
Related condition fields: transStatus.
Format and scope
Type: String · Length: 2 characters · Minimum length: 2 · Maximum length: 2
- Source components
- ACS, DS
- Device channels
- 01-APP, 02-BRW, 03-3RI
- 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 289, 290, 291
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
6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6bOfficial EMVCo specifications · Methodology and coverage limits