> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/device-binding-flow.md).

# Token binding

Typically, a token requestor, such as a merchant, starts a token binding request through the TSP. It does so when the end user is ready to pay with a token. It can also bind the token to a device or passkey. Token binding restricts token use and increases confidence in its legitimacy.

D1 receives the request and orchestrates the workflow by using the registered data. The issuer backend does not need new APIs. The level of issuer backend involvement depends on the integration model selected by the issuer.

Because token binding involves a device, the issuer can define untrusted device types during D1 onboarding. D1 uses this data to decline a binding request when the TSP provides the required device information.

The following table lists the information that the issuer can use to define untrusted devices:

| Rule name                        | Description                                                                                      |
| -------------------------------- | ------------------------------------------------------------------------------------------------ |
| Device types not trusted         | The issuer can select device types that it does not trust. For example, devices of type `WATCH`. |
| Device manufacturer              | The issuer can list device manufacturers that it does not trust.                                 |
| Device manufacturer - OS version | If known, the issuer can specify an OS version that it does not trust.                           |
| Device manufacturer - FW version | If known, the issuer can specify a firmware version that it does not trust.                      |

Without rules for untrusted devices, D1 always requires **step-up authentication** for each binding request.

### Sequence diagrams

The following sequence diagrams show the full flow orchestrated by D1 and the level of involvement of the issuer backend.

<figure><img src="/files/KC5GhVYy1bAXeuDzVKBI" alt=""><figcaption><p>Overview of the token binding flow.</p></figcaption></figure>

If no untrusted devices have been defined, or if no device matches the defined rules, D1 always performs **step-up authentication** and provides the list of available ID\&V methods.

For ID\&V prerequisites, see [Prerequisites for ID\&V methods](/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md#prerequisites-for-id-and-v-methods).

#### OTP verification by SMS or email

The following sequence diagram shows the flow when the end user chooses OTP by SMS or email for verification:

<figure><img src="/files/kGDX7BBYH4n80BxK9On6" alt=""><figcaption><p>OTP verification flow for token binding.</p></figcaption></figure>

If the issuer backend manages OTP delivery, it can use the `otp.reason` field to distinguish this request from a Tokenization request. It can use `deliveryChannel` to determine the message type:

* `otp.reason` = `DEVICE-BINDING`
* `deliveryChannel` = `SMS` or `EMAIL`

#### Verification by the issuer application

The following sequence diagram shows the flow when the end user chooses the issuer application as the verification method:

<figure><img src="/files/WPDxvlWAiCSj9H3qlC8O" alt=""><figcaption><p>Issuer application verification flow for token binding.</p></figcaption></figure>

As described in the [High-level flow](/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md#high-level-flow) section, the issuer backend must handle the integration required in step `[02]`. The shared data depends on the TSP. Compared with a Tokenization flow, use the following mapping to populate `StepupAuthenticationResult` correctly:

<table><thead><tr><th width="228.45458984375">D1</th><th width="261.727294921875">Mastercard</th><th>Visa</th></tr></thead><tbody><tr><td><code>authenticationId</code></td><td><code>authenticationCorrelationId</code></td><td><code>lifeCycleTraceID</code></td></tr></tbody></table>

#### Verification by issuer application with issuer-managed trigger

The issuer can support verification in the issuer application by using a PUSH message as the trigger instead of relying on the merchant application to trigger the issuer application.

{% hint style="warning" %}
This option is supported only under these conditions:

* The issuer supports Mastercard cards. Only Mastercard can propagate this type of ID\&V option to the merchant.
* The issuer does not rely on the D1 OBO service to send messages to the end user. In that case, Thales cannot send the PUSH message on behalf of the issuer.
  {% endhint %}

The following diagram shows this flow:

<figure><img src="/files/wRjmCqUqhzIAC9xqWP5I" alt=""><figcaption></figcaption></figure>

To identify this case, the issuer must check the following fields in the `Deliver OTP` API:

* `otp.reason` = `DEVICE-BINDING`
* `deliveryChannel` = `PUSH`
* `deviceInformation.deviceReference`
* `digitalCardId`

To report the result through `StepupAuthenticationResult`, the issuer must send the following value along with `digitalCardId`:

* `authenticationId` = `deviceInformation.deviceReference`

{% hint style="warning" %}
In this case, no `otp.value` is provided.

The issuer is free to manage the PUSH message content and format.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/device-binding-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.