> 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/implement-tokenization/post-tokenization-requests/visa-cloud-token-framework-ctf/cardholder-verification.md).

# Cardholder verification

This feature allows the Merchant to request end user verification from the Issuer at any time after a card is tokenized and, optionally, bound.

The objective of this feature is to give the Merchant a way to authenticate the end user. For example, the Merchant can use it after detecting suspicious activity on the end user account.

The following diagram shows a high-level flow and highlights the Issuer's involvement in the process.

<figure><img src="/files/mubNwywORLVy3rSHPS4e" alt=""><figcaption><p>High-level cardholder verification flow.</p></figcaption></figure>

The diagram references [Approve with step-up authentication](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/approve-with-step-up-authentication.md).

This is the same flow used for Tokenization processing, with the following exceptions:

* The `Customer service` ID\&V method is not supported.
* The `In-app` ID\&V method can be supported through the D1 SDK. In particular, please refer to the section  [In app authentication for Visa CTF](/push-provisioning/implement-push-provisioning/implement-view-and-control/in-app-authentication-for-visa-ctf.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/visa-cloud-token-framework-ctf/cardholder-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
