> 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/classic-push-provisioning/get-started/key-concepts.md).

# Key concepts

Classic Push Provisioning Service is a digital payment solution. It simplifies enrollment by pushing cards from the issuer application to xPay Wallets and token requestors.

This gives end users control of their digital cards stored in multiple wallets and token requestors, from the issuer application.

These capabilities are delivered through an SDK you integrate into the issuer application:

<figure><img src="/files/9rZiuUfaMT4l5t7qikzm" alt=""><figcaption><p>Token Push &#x26; Control SDK overview.</p></figcaption></figure>

The Token Push & Control SDK lets you:

* Push provisioning to xPay Wallets
* Push provisioning via payment networks
* View tokens

This SDK is available for:

* iOS
* Android

The Push Provisioning SDK integrates with the Thales backend, which connects to VTS and MDES. It leverages the existing push provisioning service APIs and ITSP services APIs provided by Visa and Mastercard to the issuer.

Details for each capability are below.

### Push provisioning to xPay Wallets

End users can use push provisioning to add cards to xPay Wallets.

<figure><img src="/files/Ej9KFgXLkyXpoJMeKbN1" alt=""><figcaption><p>Push provisioning to xPay Wallets.</p></figcaption></figure>

### Push provisioning via payment networks

End users can add their cards to token requestors that are eligible with the payment networks.

<figure><img src="/files/KkhIxxZiQMazRMmDhXYz" alt=""><figcaption><p>Push provisioning via payment networks.</p></figcaption></figure>

### Token view

End users can view tokens that were previously created.

<figure><img src="/files/EMzdM1mmuiPnS5dCeoCO" alt=""><figcaption><p>Token view.</p></figcaption></figure>

The TPC SDK shows the following information for each token:

* Token requestor name
* Token requestor logo
* Token state (active or suspended)
* Device information (if available)

### Feature compatibility across payment networks and operating systems

The following table lists the supported combinations for the Push Provisioning SDK:

| Use case                                  | Visa                                                               | Mastercard                                                         | Amex                                                                       | Discover (2)                                                       | Domestic (1) |
| ----------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------ |
| **Push provisioning to xPay Wallets**     | <ul><li>Apple Pay</li><li>Samsung Pay</li><li>Google Pay</li></ul> | <ul><li>Apple Pay</li><li>Samsung Pay</li><li>Google Pay</li></ul> | <ul><li>Apple Pay</li><li>Google Pay (2)</li><li>Samsung Pay (2)</li></ul> | <ul><li>Apple Pay</li><li>Google Pay</li><li>Samsung Pay</li></ul> | Huawei Pay   |
| **Push provisioning via payment network** | -                                                                  | <ul><li>Android</li><li>iOS</li></ul>                              |                                                                            |                                                                    |              |
| **Token view and control**                | <ul><li>Android</li><li>iOS</li></ul>                              | <ul><li>Android</li><li>iOS</li></ul>                              |                                                                            |                                                                    |              |
|                                           |                                                                    |                                                                    |                                                                            |                                                                    |              |

(1) Supported only under specific conditions. Check with your Thales delivery team for details.

(2) Not yet tested in the Production Environment.


---

# 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/classic-push-provisioning/get-started/key-concepts.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.