> 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/sdk-integration/android-api/migrate-from-2.x-to-3.0.md).

# Migrate from 2.x to 3.0

Starting with Thales SDK 3.0.0, several public APIs have been simplified.

## Renamed Classes and APIs <a href="#renamed-classes-and-apis" id="renamed-classes-and-apis"></a>

* [PendingBindingSession.java](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/2.0.0/com/thalesgroup/tmgsdk/PendingBindingSession.html) to [IDVSession.java](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/IDVSession.html).
* [PendingBindingSession.submitIdvMethod()](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/2.0.0/com/thalesgroup/tmgsdk/PendingBindingSession.html#submitIdvMethod\(com.thalesgroup.tmgsdk.IDVMethod\)) to [IDVSession.selectIdvMethod()](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/visa/IDVSession.html#selectIdvMethod\(com.thalesgroup.tmgsdk.visa.IDVMethod\)).

## Renamed Packages <a href="#renamed-package" id="renamed-package"></a>

* Visa-specific classes were moved to the `visa` package: [VisaCTFHelper](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/visa/VisaCTFHelper.html), [TokenBindingListener](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/visa/TokenBindingListener.html), [IDVSession](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/visa/IDVSession.html), [IDVMethod](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/visa/IDVMethod.html), [IDVType](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/model/visa/IDVType.html), and [OtpActivationStatus](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/model/visa/OtpActivationStatus.html).

Because Visa and Mastercard class names are identical, we recommend the following changes to avoid ambiguous reference errors:

* In Java, separate the API calls for Visa and Mastercard into different classes. The use of fully qualified name (class name along with the package) to call both Visa and Mastercard APIs within a single class is not recommended.
* In Kotlin, use the package alias feature with the `as` keyword:

```kotlin
import com.thalesgroup.tmgsdk.visa.IDVMethod as VisaIDVMethod
import com.thalesgroup.tmgsdk.mastercard.IDVMethod as MasterCardIDVMethod

fun main() {
 var visaIDVMethod: VisaIDVMethod
 var masterCardIDVMethod: MasterCardIDVMethod
}
```

## Removed Classes and APIs <a href="#removed-classes-and-apis" id="removed-classes-and-apis"></a>

* [TMGClientConfiguration.Builder](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/2.0.0/com/thalesgroup/tmgsdk/TMGClientConfiguration.Builder.html): All configuration options were moved to the [TMGClientConfiguration](https://thalesgroup.github.io/d1sdk-docs/tmg-sdk/android/3.0.0/com/thalesgroup/tmgsdk/TMGClientConfiguration.html) constructor.


---

# 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:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/sdk-integration/android-api/migrate-from-2.x-to-3.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.