> 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/release-notes/sdk/may-2025/merchant-tokenization-v3.0.0.md).

# Merchant Tokenization v3.0.0

### Supported platforms and architectures

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

* Android 8.0 or later
* Architectures: `armeabi-v7a`, `arm64-v8a`, `x86`, `x86_64`
  {% endtab %}

{% tab title="iOS" %}

* iOS 15 or later
* Architectures: `arm64`, `x86_64`
  {% endtab %}
  {% endtabs %}

#### ⚠️ Deprecations & Breaking Changes

* Introduce the v3.0.0 API (breaking). Migrate using the guides for [Android](https://thales-dis-dbp.stoplight.io/docs/tsh-cof-token-gateway/o1s0933vidmbi-migration-2-x-to-3-0) and [iOS](https://thales-dis-dbp.stoplight.io/docs/tsh-cof-token-gateway/1d2932c2fe2ea-migration-2-x-to-3-0).
* Unbind tokens bound with versions earlier than v3.0.0. Rebind them in your end user flow.
* Disallow publishing the debug build to Google Play.
* Remove the `deviceId` parameter from `createBinding`. See API references for [iOS](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/ios/latest/Classes/VisaCTFHelper.html#/s:6TMGSDK13VisaCTFHelperC13createBinding22forVProvisionedTokenID011correlationI027deviceAuthenticationHandler010idvSessionM0010completionM0ySS_SSyAA06DeviceL0CcyAC10IDVSessionCcyAMSg_AA8TMGErrorOSgtctF) and [Android](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/latest/com/thalesgroup/tmgsdk/visa/VisaCTFHelper.html#createBinding\(java.lang.String,java.lang.String,com.thalesgroup.tmgsdk.visa.TokenBindingListener\)).
* Remove support for device keyguard. Require biometric authentication on Android and iOS.

#### 🐛 Bug Fixes

* Fix build failures caused by dependency conflicts when integrating with other Thales SDK.


---

# 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/release-notes/sdk/may-2025/merchant-tokenization-v3.0.0.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.