> 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/es/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/device-binding-flow.md).

# Flujo de vinculación del dispositivo

Vincular una tarjeta digital a un dispositivo específico para transacciones de comercio electrónico.

El **Solicitante de token** inicia el flujo.

La red de pagos **TSP** impone la vinculación.

### Flujo a alto nivel

1. El solicitante de token solicita la vinculación del dispositivo para una tarjeta digital.
2. La red de pago solicita **Usuario final** autenticación, si es necesario.
3. Si la autenticación tiene éxito, el TSP actualiza la información de vinculación del dispositivo.

### Resultado de una vinculación exitosa

* La red de pago marca la tarjeta digital como vinculada al dispositivo.
* Señales de vinculación del dispositivo pueden enviarse en solicitudes de autorización.

Siguiente: [Flujo de verificación del titular de la tarjeta](/tokenization/es/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/cardholder-verification-flow.md).

{% hint style="info" %}
Los nombres de campo y la semántica de la vinculación varían según la red de pago.

Coordinar el comportamiento esperado durante el diseño.
{% 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/es/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.