> 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/merchant-tokenization/es/ctf-y-daf-de-visa/implement-ctf-and-daf/delete-binding/delete-binding-from-merchant-backend.md).

# Eliminar la vinculación desde el backend del comercio

Use este flujo para eliminar la vinculación del dispositivo de su backend de comerciante o PSP.

{% hint style="info" %}
Evite la desincronización entre dispositivo y servidor.

Elimine la vinculación localmente en el dispositivo cuando sea posible.

Utilice [Sincronice el estado de la vinculación](/merchant-tokenization/es/ctf-y-daf-de-visa/implement-ctf-and-daf/synchronize-binding.md) si los estados de vinculación divergen.
{% endhint %}

## Flujo

<figure><img src="/files/946090da5057661c88683a1c7491d607e75770e3" alt=""><figcaption><p>Flujo de eliminación de vinculación iniciado por el backend.</p></figcaption></figure>

<table><thead><tr><th width="100">Paso</th><th>Descripción</th></tr></thead><tbody><tr><td>1</td><td>El <strong>backend del comerciante o del PSP</strong> envía una solicitud de eliminación de vinculación al backend de Thales.</td></tr><tr><td>2–3</td><td>La solicitud se reenvía a <strong>VTS</strong> y el <strong>backend del emisor</strong> que eliminan los datos de vinculación del token y del dispositivo.</td></tr></tbody></table>

## API

Utilice la siguiente API para eliminar una vinculación en el lado del backend.

* Referencia de la API: [Eliminar vinculación](broken://pages/0c9e5bf07d40c12cd69b09e0add1c4e890cc70b3#delete-device-bindings-tokenid-deviceid)


---

# 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/merchant-tokenization/es/ctf-y-daf-de-visa/implement-ctf-and-daf/delete-binding/delete-binding-from-merchant-backend.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.