> 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/e-commerce-enrolment-flow/token-for-token-provisioning.md).

# Token for token provisioning

Token for token provisioning is a Visa-only use case.

It lets a **token requestor** (merchant) request a **Card-on-file (COF)** token by providing a device token from **xPay Wallets** (for example, Apple Pay or Google Pay).

This improves the end user experience because the end user does not need to enter card details.

The diagram below shows the flow.

<figure><img src="/files/PMbsyQ7XCBG18tLj1yx7" alt=""><figcaption><p>Token for token provisioning flow (Visa only).</p></figcaption></figure>

The issuer backend handles the same API calls as a standard digitization.

Key differences:

* Identify this flow by checking the capture method:
  * `checkCardEligibility`: `captureMethod=TOKEN`
  * `requestCardDigitization`: `cardCaptureInformation.captureMethod=TOKEN`
* Retrieve the original token attributes in `requestCardDigitization`, `notifyVirtualCardChange`, and `notifyStandInProcess`:
  * `originalToken`
  * `originalTokenRequestorId`
  * `originalTokenReferenceID`
  * `originalTokenAssuranceLevel`

Attribute definitions:

* **`originalToken`**: Device token retrieved from xPay Wallets and used to request digitization.
* **`originalTokenRequestorId`**: Token requestor identifier associated with the original token.
* **`originalTokenReferenceID`**: Reference identifier of the original token.
* **`originalTokenAssuranceLevel`**: Assurance level of the original token.


---

# 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/e-commerce-enrolment-flow/token-for-token-provisioning.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.