> 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/use-cases/push-provisioning-to-xpay-wallets.md).

# Push provisioning to xPay Wallets

End users can add eligible cards to xPay Wallets from the issuer application. Supported wallets include Apple Pay, Google Pay, and Samsung Pay.

The issuer application verifies the end user’s identity before activating the card.

### Step 1: Decide whether to show **Add to Wallet**

The issuer application uses the Push Provisioning SDK to check whether:

* The target xPay Wallet is supported on the device.
* A token already exists for the card on the device.

Based on the result, show or hide **Add to Wallet**.

Call `getToken` to decide whether to show **Add to Wallet**. Pass the last 4 digits of the PAN.

The SDK checks whether the card is already present in the wallet. Use the response to decide whether to display **Add to Wallet**.

<figure><img src="https://2043783750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC22AqJs7fn1cZC7pAaOE%2Fuploads%2FSh4u0cMSv4pNGRqTLgAR%2FUC_push-provisioning-01.png?alt=media&amp;token=f7d8c549-57f9-4a8b-b1ac-602b9d60b37f" alt=""><figcaption><p>Show or hide <strong>Add to Wallet</strong> based on card presence.</p></figcaption></figure>

The Push Provisioning SDK requires encrypted card data to verify with the issuer backend. See [Card data encryption (PKCS#7 format)](/classic-push-provisioning/developer-guide/data-encryption-and-authentication/card-data-encryption-pkcs-7-format.md).

### Step 2: Provision a card

After the end user taps **Add to Wallet**, start push provisioning. Call the SDK `provision` method.

Create an `authorizationCode` (JWT) for this flow. See [Authorization code (JWT format)](/classic-push-provisioning/developer-guide/data-encryption-and-authentication/authorization-code-jwt-format.md).

<figure><img src="https://2043783750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC22AqJs7fn1cZC7pAaOE%2Fuploads%2FHTew9jkahj9lDKChKLB4%2FUC_push-provisioning-02.png?alt=media&amp;token=c40a253b-822c-4a83-89fc-c3679de0612e" alt=""><figcaption><p>Provisioning flow with the Push Provisioning SDK.</p></figcaption></figure>


---

# 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/classic-push-provisioning/use-cases/push-provisioning-to-xpay-wallets.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.