> 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-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-c-activate-in-the-issuer-application/integrate-issuer-application-with-wallet.md).

# Integrate issuer application with wallet

### Overview

Issuer application activation happens during a Tokenization flow.

The end user is redirected from the wallet application to the issuer application for **ID\&V**.

Example: Apple Pay redirects to an issuer application (for example, “Antipolis Bank App”).

<figure><img src="/files/3s1bG0WFhJWWpJDRKBPS" alt=""><figcaption><p>Example wallet-to-issuer application redirect.</p></figcaption></figure>

This option requires issuer development work.

It enables the wallet application to open the issuer application and complete in-app ID\&V.

### End-to-end flow

<figure><img src="/files/ULOTEeM6V5wGNSkk28wG" alt=""><figcaption><p>Issuer application activation flow.</p></figcaption></figure>

### Integration points

1. In step 4, the issuer backend responds to the digitization request with ID\&V method `bank_app`.
2. In step 6, configure the payment network TSP to enable issuer application activation.
3. In step 9, the issuer backend stores the wallet identifiers required to link the card and token.
4. In steps 12–13, the issuer application performs end user verification.
5. In step 14, the issuer backend activates the token using [Update Card State](https://thales-dis-dbp.stoplight.io/docs/digital-payment/94126e1e7a5c5-update-virtual-card-state) with `action=RESUME`.
   * This call requires the token reference returned in step 9.

### Redirection information

The wallet application needs redirection data to open the issuer application.

The issuer backend returns part of this data in the step 4 response.

Configure the remaining data in the payment network TSP. You can use as guideline the following two sections:

* [Apple Pay in-app ID\&V](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-c-activate-in-the-issuer-application/integrate-issuer-application-with-wallet/apple-pay-in-app-id-and-v.md)
* [Google & Samsung Pay in-app ID\&V](/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-c-activate-in-the-issuer-application/integrate-issuer-application-with-wallet/google-and-samsung-pay-in-app-id-and-v.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:

```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-c-activate-in-the-issuer-application/integrate-issuer-application-with-wallet.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.