> 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/cardholder-verification.md).

# Cardholder verification

Cardholder verification lets a token requestor ask the issuer to verify the end user.

Use this flow when you detect suspicious activity on an end user account.

To start the flow, the token requestor requests the list of supported ID\&V methods. It sends the request to Visa Token Service (VTS). VTS then calls the issuer.

Tokenization Service translates this request into [`getIDnVMethodList`](/classic-tokenization/api-reference/issuer-gateway-api/outbound-to-issuer.md). As in the [Device binding](/classic-tokenization/use-cases/post-enrolment/visa-cloud-token-framework/device-binding.md) flow, Visa requires the issuer to support at least one of these methods:

* OTP via SMS or email
* Verify in the issuer application
* 3DS

If you use issuer-application verification, apply the same protocol considerations as for device binding.

The sequence diagram shows the end-to-end flow.

Cardholder verification requested by the token requestor:

<figure><img src="https://2421315942-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OvNtPk6hurTTvkKLzkK%2Fuploads%2FJk2JtTqijgEbrWa72fUk%2Fcardholder-verification.png?alt=media&amp;token=1aeaa1d5-11b9-4cd3-b0ba-425d2fe0b184" alt=""><figcaption><p>Cardholder verification requested by the token requestor</p></figcaption></figure>


---

# 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/cardholder-verification.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.