> 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/mastercard-taf/implement-taf/delete-device-binding.md).

# Delete device binding

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%2FozbbObU9MaFcQNNKZyem%2Fimage.png?alt=media&amp;token=f3c59a8f-a7dd-4d0f-92d2-ac41414fde9b" alt=""><figcaption><p>App-initiated device 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 merchant application calls the Thales SDK to delete the device binding for the token.</td></tr><tr><td>2-4</td><td>The Thales backend sends the deletion request to the payment network which coordinates the deletion with the issuer backend.</td></tr><tr><td>5-6</td><td>The Thales SDK returns the result to the merchant application.</td></tr><tr><td>7</td><td>The Thales backend sends a notification to the merchant or PSP backend.</td></tr></tbody></table>

## SDK integration

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

{% tabs %}
{% tab title="Android" %}

```java
mastercardTAFHelper.removeBinding(tokenID, correlationID, new RemoveBindingListener() {
    @Override
    public void onError(TMGClientException tmgClientException) {
        // Handle error
    }

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

{% endtab %}

{% tab title="iOS" %}

```swift
mastercardTAFHelper.removeBinding(forTokenID: tokenID,
                                  correlationID: correlationID) { error in
    if error == nil {
        // Update local binding state if needed
    } else {
        // Handle error
    }
}
```

{% endtab %}
{% endtabs %}

## Backend integration

The Thales backend notifies your merchant or PSP backend when the device binding is deleted.

* 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 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/mastercard-taf/implement-taf/delete-device-binding.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.