3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Device Binding StatusdeviceBindingStatus

Device Binding Status 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 Optional

Optional across all channels and categories. Usage and conditions ↓

Jump to values ↓Explore in context →

Field value definitions

Field-wide definitions. Check message-specific restrictions in usage and conditions.

CodeMeaning
01Device is not bound by Cardholder
02Not eligible as determined by Issuer
03Pending confirmation by Cardholder
04Cardholder rejected
05Device Binding Status unknown, unavailable, or does not apply
11Device is bound by Cardholder (device is bound using hardware / SIM internal to the Consumer Device. For instance, keys stored in a secure element on the device)
12Device is bound by Cardholder (device is bound using hardware external to the Consumer Device. For example, an external FIDO Authenticator)
13Device is bound by Cardholder (Device is bound using data that includes dynamically generated data and could include a unique device ID)
14Device is bound by Cardholder (Device is bound using static device data that has been obtained from the Consumer Device)
15Device is bound by Cardholder (Other method)

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

Reserved values

CodeMeaning
06–10Reserved for EMVCo future use (values invalid until defined by EMVCo)
16–79Reserved for EMVCo future use (values invalid until defined by EMVCo)
80–99Reserved for DS use

Usage in AReq

Enables the communication of Device Binding Status between the ACS, the DS and the 3DS Requestor. For bound devices (value = 11–14), Device Binding Status also conveys the type of binding that was performed.

Format and scope

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

Source components: 3DS Server, DS, ACS. 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 245, 246

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 245, 246

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b