Field value definitions
Field-wide definitions. Check message-specific restrictions in usage and conditions.
| Code | Meaning |
|---|---|
Y | Authentication Verification Successful. |
N | Not Authenticated / Account Not Verified; Transaction denied. |
U | Authentication / Account Verification Could Not Be Performed; Technical or other problem, as indicated in ARes or RReq. |
A | Attempts Processing Performed; Not Authenticated/ Verified, but a proof of attempted authentication/verification is provided. |
C | Challenge Required; Additional authentication is required using the CReq/CRes. |
D | Challenge Required; Decoupled Authentication confirmed. |
R | Authentication / Account Verification Rejected; Issuer is rejecting authentication/verification and request that authorisation not be attempted. |
I | Informational Only; 3DS Requestor challenge preference acknowledged. |
S | Challenge using SPC |
Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 288, 289. Read usage and conditions.
Usage in CRes
Indicates whether a transaction qualifies as an authenticated transaction or account verification. The Final CRes message can only contain a value of Y or N or D. Transaction Status = C or S is not allowed for Device Channel = 3RI.
Conditional inclusion — source text
For 01-PA, see Table A.17 for Transaction Status presence conditions. For 02-NPA, requirements for the presence and values of Transaction Status are DS-specific.
Format and scope
Type: String · Length: 1 character · Minimum length: 1 · Maximum length: 1
Source components: ACS, DS. 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 288, 289
Related FAQ notes
- In CRes, only present in Final CRes with values Y, N, or D only. If received in non-Final CRes, ignore per Req 209. RReq contains full value range for detailed status. — FAQ 15 (EMVCo FAQ)
- Value 'I' is only valid when threeDSRequestorChallengeInd = 05, 06, or 07. — FAQ 23 (EMVCo FAQ)
- Value 'C' is not allowed for 03-3RI channel—Cardholder not present. Use 'D' (Decoupled) if challenge needed. — FAQ 29 (EMVCo FAQ)
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.
Sources and related references
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 288, 289
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b