> 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/es/casos-de-uso/postinscripcion/visa-cloud-token-framework/verificacion-del-titular-de-la-tarjeta.md).

# Verificación del titular de la tarjeta

La verificación del titular de la tarjeta permite que un solicitante de token pida al emisor que verifique al usuario final.

Use este flujo cuando detecte actividad sospechosa en una cuenta de usuario final.

Para iniciar el flujo, el solicitante de token solicita la lista de métodos de ID\&V compatibles. Envía la solicitud a Visa Token Service (VTS). VTS luego llama al emisor.

El Servicio de Tokenización traduce esta solicitud a [`getIDnVMethodList`](/classic-tokenization/es/referencia-de-la-api/api-de-la-pasarela-del-emisor/saliente-al-emisor.md). Como en el [flujo de vinculación del dispositivo](/classic-tokenization/es/casos-de-uso/postinscripcion/visa-cloud-token-framework/vinculacion-del-dispositivo.md) , Visa exige que el emisor admita al menos uno de estos métodos:

* OTP vía SMS o correo electrónico
* Verificar en la aplicación del emisor
* 3DS

Si utiliza la verificación mediante la aplicación del emisor, aplique las mismas consideraciones de protocolo que para la vinculación del dispositivo.

El diagrama de secuencia muestra el flujo de extremo a extremo.

Verificación del titular de la tarjeta solicitada por el solicitante de token:

<figure><img src="https://3204989413-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>Verificación del titular de la tarjeta solicitada por el solicitante de token</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/es/casos-de-uso/postinscripcion/visa-cloud-token-framework/verificacion-del-titular-de-la-tarjeta.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.