> 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/home/card-creation-and-management/overview.md). # Overview D1 offer API and Web UI to manage the end user's virtual and physical card based on its data model. ### End User management As described in D1 Data Model it is mandatory to register the End User (Consumer) before creating any new card. During this registration it is mandatory to provides useful end user personal information so D1 can provides all the digital Tokenization services. The [Manage end users](/home/card-creation-and-management/manage-end-users.md) section explain in details how to register but also how to update personal information with D1. ### Card Management The Manage Card section explain how to create a physical or virtual card , but also how to manage the life cycle of the card. The physical card creation trigger the personalization and shippment of the card. ### Orchestration The card creation is not limited to PAN and expiry date allocation but also the orchestration of the enalbment of all digital services (Tokenization, registration to Click2PAy, 3DS enablment, ...) this without any additional implementation. --- # 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/home/card-creation-and-management/overview.md?ask=&goal= ``` `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.