> 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/view-and-control/in-app-authentication.md).
# In-app authentication
The in-app authentication use case occurs during a tokenization flow where the end user chooses to be authenticated through the application of the issuer. The issuer can determine whether to support this ID\&V method. To support the ID\&V method, the Issuer has to consider a certain level of effort (development) to allow the interaction between the wallet and its applications, which is covered in this section.
The general flow is depicted in the following diagram:
> #### Note
>
> * In **step 4**, it is up to the Issuer to respond to a digitization request with an in-app ID\&V.
> * In **step 6**, issuer has to perform a configuration in the TSP.
> * In **step 9**, issuer has to manage the integration with the Wallet properly to identify the card and the token. This is explained in the following section.
> * In **step 10**, the application must show the `last4` of Card PAN as card identification.
> * In **step 12**, it is up to the issuer to perform the consumer authentication accordingly.
> * In **step 13**, it implies the knowledge of the token reference to allow the activation of the token where the token information is provided through the **step 9** . The activation can be accomplished through the [Token life cycle management](/classic-push-provisioning/use-cases/view-and-control/control-life-cycle-operation.md).
To redirect the end user to the issuer application, the wallet application needs the appropriate redirection information.
The redirection information is partially provided in the response of **step 4** and partially configured in the scheme TSP. To configure this information correctly, check with your contact in TSP team.
The following sections show the integration between the issuer application and the wallet.
---
# 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/classic-push-provisioning/use-cases/view-and-control/in-app-authentication.md?ask=&goal=
```
`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.