Valid values
| Code | Meaning |
|---|---|
Y | Decoupled Authentication is supported and is preferred as a primary challenge method if a challenge is necessary (Transaction Status = D in ARes). |
N | Do not use Decoupled Authentication. |
F | Decoupled Authentication is supported and is to be used only as a fallback challenge method if a challenge is necessary (Transaction Status = D in RReq). |
B | Decoupled Authentication is supported and can be used as a primary or fallback challenge method if a challenge is necessary (Transaction Status = D in either ARes or RReq). |
Source: EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 193. Read usage and conditions.
Usage in AReq
Indicates whether the 3DS Requestor requests the ACS to use Decoupled Authentication and agrees to use Decoupled Authentication if the ACS confirms its use. Note: if the element is not provided, the expected action is for the ACS to interpret as N (Do not use Decoupled Authentication).
Format and scope
Type: String · Length: 1 character · Minimum length: 1 · Maximum length: 1
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 193
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 193
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b