3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Device Binding Data EntrydeviceBindingDataEntry

Device Binding Data Entry in Challenge Request (CReq).

Source edition: Core 2.3.1.1 · Type: String · Length: 1 character · Minimum length: 1 · Maximum length: 1

Baseline in CReq Conditional

Varies by context. Requirement or applicability varies by channel or message category. Select a specific context to resolve it. Usage and conditions ↓

Jump to values ↓Explore in context →

Valid values

CodeMeaning
YConsent given to bind device
NConsent not given to bind device

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

Usage in CReq

Indicator provided by the 3DS SDK to the ACS to confirm whether the Cardholder gives consent to bind the device.

Conditional inclusion — source text

Required if • Device Binding Information Text was present in the previous CRes message AND • Challenge Cancelation Indicator is not present

Format and scope

Type: String · Length: 1 character · Minimum length: 1 · Maximum length: 1

Source components: 3DS SDK. Channels: 01-APP. Categories: 01-PA, 02-NPA.

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 244

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 244

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

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b