> 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/check-device-binding.md).

# Check device binding

Use the Thales SDK to check the current device binding state for a provisioned token ID.

Call this before you start a transaction flow. The returned state tells you if you must create a binding first.

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

```java
public void getBindingState(@NonNull MastercardTAFHelper mastercardTAFHelper, @NonNull String tokenID) {
    try {
        BindingState bindingState = mastercardTAFHelper.getBindingState(tokenID);
    } catch (TMGClientException e) {
        // Handle the error
    }
}
```

{% endtab %}

{% tab title="iOS" %}

```swift
let vProvisionedTokenID = ""
do {
    let state = try visaCTFHelper.bindingState(forVProvisionedTokenID: vProvisionedTokenID)
} catch let error {
    // Handle the error
}
```

{% endtab %}
{% endtabs %}

### Next steps by binding state

Use the returned value to choose the next call in your flow.

* `UNBOUND`

  The provisioned token ID has not been bound to this device yet.

  Create the binding between the client and server. See the [create device binding](/merchant-tokenization/mastercard-taf/implement-taf/create-device-binding.md).
* `BOUND`

  The provisioned token ID is already bound to this device.

  Use the provisioned token ID to authenticate the transaction. See the [authenticate a transaction](/merchant-tokenization/mastercard-taf/implement-taf/authenticate-a-transaction.md).


---

# 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/mastercard-taf/implement-taf/check-device-binding.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.