> 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/tokenization/ja/integrate-in-app-id-and-v-for-xpay-wallets.md).

# xPay Wallet向けアプリ内ID\&Vを統合

Once the End User selects the in-app method for ID\&V, the digital wallet application must redirect the flow to the issuer application.

To do this, the TSP provides the following redirection information:

* The issuer application reference (configured by the issuer in the TSP during onboarding).
* An opaque payload that describes the reason for the ID\&V request.

This section provides details on:

* The information the issuer must provide to the TSP (application metadata).
* How to handle the redirection call from the digital wallet application.

The diagram below shows, at a high level, the main steps for this use case:

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/cx2OniFOnUhXjfShKoOF" alt=""><figcaption><p>In-app ID&#x26;V redirection flow for xPay Wallets.</p></figcaption></figure>

1. During onboarding, the issuer configures the application metadata in the TSP.
2. During Tokenization, when step-up authentication is required, the TSP provides the following data along with the method type:
   1. issuer application reference
   2. opaque payload
3. The digital wallet application uses the issuer application reference to open the issuer application. It passes the opaque payload in the call.
4. The issuer application parses the opaque payload to understand the request. It then prompts the End User to enter credentials.
5. The issuer application verifies the credentials.
6. The issuer application returns the verification result to the issuer backend.
7. The issuer backend reports the result to the TSP.


---

# 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/tokenization/ja/integrate-in-app-id-and-v-for-xpay-wallets.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.