3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Device Binding StatusdeviceBindingStatus

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.

Explore this field with transaction context

Allowed and reserved values

ValueMeaningIntroduction tag
01Device is not bound by CardholderNot tagged
02Not eligible as determined by IssuerNot tagged
03Pending confirmation by CardholderNot tagged
04Cardholder rejectedNot tagged
05Device Binding Status unknown, unavailable, or does not applyNot tagged
06–10Reserved for EMVCo future use (values invalid until defined by EMVCo)Reserved
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)Not tagged
12Device is bound by Cardholder (device is bound using hardware external to the Consumer Device. For example, an external FIDO Authenticator)Not tagged
13Device is bound by Cardholder (Device is bound using data that includes dynamically generated data and could include a unique device ID)Not tagged
14Device is bound by Cardholder (Device is bound using static device data that has been obtained from the Consumer Device)Not tagged
15Device is bound by Cardholder (Other method)Not tagged
16–79Reserved for EMVCo future use (values invalid until defined by EMVCo)Reserved
80–99Reserved for DS useReserved

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.

MessageBaseline inclusion
AReqOptional
AResOptional
RReqOptional

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

Version history

Field introduction tag: 2.3.1.1. 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 245, 246

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