> 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/post-enrolment/visa-cloud-token-framework.md).

# Visa Cloud Token Framework

{% hint style="warning" %}
**This section is deprecated.**

Please refer instead to the new section [Token Verification](/classic-tokenization/use-cases/post-enrolment/token-verification.md).

This new section is meant to describe how the issuer gateway supports the for e-commerce post-tokenization verification frameworks designed by both, Visa and Mastercard.
{% endhint %}

Visa Cloud Token Framework (CTF) is a Visa proprietary framework. It enhances security and trust for e-commerce token transactions.

CTF extends Visa Token Service (VTS) with APIs that a token requestor can use to send specific requests to the issuer.

CTF adds two capabilities:

* **Device binding**
* **Cardholder verification**

<figure><img src="https://2421315942-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OvNtPk6hurTTvkKLzkK%2Fuploads%2FpC1nQDjB8WgPXXYuzGY3%2Fctf-overview.png?alt=media&amp;token=aae0c7b8-8fde-42ed-9d2f-54f8383b274a" alt=""><figcaption><p>Visa Cloud Token Framework (CTF) overview</p></figcaption></figure>

### Device binding <a href="#device-binding" id="device-binding"></a>

Device binding lets the token requestor ask the issuer to bind a token to the device where the card tokenization occurred.

This helps prevent using a token on a different device. A device mismatch can indicate fraud risk.

Visa makes device binding **Optional** for token requestors.

### Cardholder verification <a href="#cardholder-verification" id="cardholder-verification"></a>

Cardholder verification lets the token requestor ask the issuer to verify the end user at any time after card tokenization. It can be used with or without device binding.

This provides a way to authenticate the end user when the token requestor detects suspicious activity.

Visa requires token requestors to support cardholder verification. The token requestor decides when to invoke it.


---

# 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/classic-tokenization/use-cases/post-enrolment/visa-cloud-token-framework.md?ask=<question>&goal=<user_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.