> 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-binding-from-merchant-application.md).

# Delete binding from merchant application

Delete a device binding from a merchant application using the Thales SDK.

## Flow

<figure><img src="https://1873847743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XBN1F9dv7Dl1ggilGWC%2Fuploads%2FsZ6mmuLBLIdGwX6MuBiJ%2FFlow%20-%20Delete%20binding%20from%20application.svg?alt=media&amp;token=fef2b759-a064-4be4-bf7c-817afadffbc1" alt=""><figcaption><p>App-initiated binding deletion flow.</p></figcaption></figure>

<table><thead><tr><th width="100">Step</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>The <strong>merchant application</strong> calls the Thales SDK to delete the binding.</td></tr><tr><td>2–4</td><td>The request is forwarded to the Thales backend, <strong>VTS</strong>, and the <strong>issuer backend</strong>. Each system deletes binding data for the token and device.</td></tr><tr><td>5</td><td>The Thales backend notifies the <strong>merchant or PSP backend</strong> that the binding was deleted.</td></tr></tbody></table>

## SDK integration

{% tabs %}
{% tab title="Android" %}
{% hint style="warning" %}
This call is asynchronous.

Invoke the `runOnUiThread(Runnable)` callback when you need to update the UI.
{% endhint %}

Call `removeBinding()` and handle the result in `onSuccess` or `onError`.

```java
visaCTFHelper.removeBinding(correlationId, 
                            vProvisionTokenId, 
                            new RemoveBindingListener() {
            @Override
            public void onError(TMGClientException exception) { 
                // Handle error
            }

            @Override
            public void onSuccess() {
                // Update local binding state if needed
            }
        });
```

{% endtab %}

{% tab title="iOS" %}
{% hint style="warning" %}
This call is asynchronous.

Invoke the `DispatchQueue.main.async` callback when you need to update the UI.
{% endhint %}

```swift
let vProvisionedTokenID: String = ""
let correlationID: String = ""

// 1. Start remove binding
visaCTFHelper.removeBinding(forVProvisionedTokenID: vProvisionedTokenID,
                            correlationID: correlationID) { error in
    // 2. Remove binding result
    if error == nil {
        // Update local binding state if needed
    } else {
        // Handle error
    }   
}
```

{% endtab %}
{% endtabs %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/visa-ctf-and-daf/implement-ctf-and-daf/delete-binding/delete-binding-from-merchant-application.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.