> 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/es/implement-tokenization/post-tokenization-requests/marco-de-tokens-en-la-nube-de-visa-ctf.md). # Marco de tokens en la nube de Visa (CTF) {% hint style="warning" %} **Esta sección está obsoleta.** Consulte en su lugar la nueva sección [Verificación de tokens para comercio electrónico](/tokenization/es/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md). Esta nueva sección tiene como objetivo describir cómo la plataforma D1 admite los marcos de verificación pos-tokenización para comercio electrónico diseñados tanto por Visa como por Mastercard. {% endhint %} CTF es un marco propietario de Visa que tiene como objetivo mejorar la seguridad y la confianza en el ecosistema de comercio electrónico. Esto se logra mediante la incorporación de nuevas API en VTS que un comerciante o solicitante de tokens puede usar para enviar solicitudes específicas al emisor. En particular, CTF agrega las siguientes características: * Vinculación de dispositivo. * Verificación del titular de la tarjeta. CTF se aplica solo a tarjetas digitales Card-on-file (COF).

Descripción general de Visa Cloud Token Framework.

Las siguientes secciones ofrecen información sobre cómo la plataforma D1 orquesta ambos flujos. --- # 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/tokenization/es/implement-tokenization/post-tokenization-requests/marco-de-tokens-en-la-nube-de-visa-ctf.md?ask=&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.