> 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/visa-ctf-and-daf/implement-ctf-and-daf/delete-binding/delete-a-binding-from-the-tsp.md).

# Delete a binding from the TSP

The issuer backend can delete a device binding through the TSP (VTS).

{% hint style="info" %}
Avoid device/server desynchronization.

Delete the binding locally in the merchant application when possible.

Use [Synchronize binding state](/merchant-tokenization/visa-ctf-and-daf/implement-ctf-and-daf/synchronize-binding.md) if binding states diverge.
{% endhint %}

## Flow

<figure><img src="/files/jEqrXHbh4XafK8Ai8uuU" alt=""><figcaption><p>Issuer-initiated binding deletion via the TSP.</p></figcaption></figure>

<table><thead><tr><th width="100">Step</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>The <strong>issuer backend</strong> requests that <strong>VTS</strong> delete an existing device binding.</td></tr><tr><td>2</td><td><strong>VTS</strong> forwards the deletion notification to the Thales backend.</td></tr><tr><td>3</td><td>The Thales backend notifies the <strong>merchant or PSP backend</strong> that the binding was deleted.</td></tr><tr><td>4–5</td><td>The <strong>merchant or PSP backend</strong> deletes the binding locally in the merchant application when possible.</td></tr></tbody></table>

## API

The notification about device binding deletion is sent to the merchant or PSP backend.

* API reference: [Notify binding update](/merchant-tokenization/backend-integration/apis/client-api/binding-notifications.md#post-notify-binding-update)


---

# 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/visa-ctf-and-daf/implement-ctf-and-daf/delete-binding/delete-a-binding-from-the-tsp.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.