> 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/wallet-enablement/ja/ysuksu/kdowodejitarusuru.md).
# カードをデジタル化する
カードのデジタル化（登録）セッション中に、ThalesはTSPがトークンを作成することを要求します。
カードのデジタル化中の典型的なトークン提供フロー。
{% hint style="warning" %}
エンドユーザーが同じカードを複数回デジタル化した場合、カードの詳細が最初のトークン作成リクエストにのみ含まれることがあります。
その後、TSPは共有カード識別子（`cardRefId`）を使用してPANデータではなく新しいトークンを作成する必要がある場合があります。
{% endhint %}
---
# 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/wallet-enablement/ja/ysuksu/kdowodejitarusuru.md?ask=&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.
