3DS Reference

EMV 3-D Secure · Core specification 2.3.1.1

Device Binding StatusdeviceBindingStatus

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

Read in message AReqAResRReq

Baseline in RReq Optional

Optional across all channels and categories. Usage and conditions ↓

Jump to values ↓Open in explorer →

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)

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

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

Usage in RReq

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
Device channels
01-APP, 02-BRW, 03-3RI
Message categories
01-PA, 02-NPA

Introduction tags

Field introduction tag: 2.3.1.1. Introduction tags are curated metadata, not a full history of changes. An absent value tag does not establish when that value was introduced.

Compare source editions and understand coverage.

Sources and review status

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 245, 246

This page describes the published source edition. Scheme programme requirements are not inferred from it.

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

6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b

Official EMVCo specifications · Methodology and coverage limits