> 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/secure-card-display/es/get-started/mange-end-users/manage-end-user-life-cycle.md). # Gestionar el ciclo de vida del usuario final Esta página describe cómo su **backend del emisor** puede actualizar la información del usuario final y eliminar un usuario final en el **backend de D1**. Para el registro de usuarios finales, consulta [Registrar usuarios finales mediante API](/secure-card-display/es/get-started/mange-end-users/register-end-users-via-api.md). ### Actualizar la información del usuario final D1 permite que tu backend del emisor actualice la información personal almacenada para un usuario final (llamado un `consumidor` en la API de D1). #### Diagrama de secuencia

Flujo de actualización de la información del usuario final entre el backend del emisor y el backend de D1.

#### Punto final de la API Del backend del emisor al backend de D1: * [Actualizar consumidor](/secure-card-display/es/integrate-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#post-issuers-issuerid-consumers-consumerid-operations-update) ### Eliminar un usuario final D1 permite que tu backend del emisor elimine lógicamente a un usuario final. Cuando eliminas un usuario final: * El usuario final pasa al estado `ELIMINADO` estado. * Ya no puedes crear nuevas tarjetas para el usuario final. * D1 elimina todas las tarjetas vinculadas al usuario final, incluidas las tarjetas digitales. #### Diagrama de secuencia

Flujo de eliminación lógica de un usuario final entre el backend del emisor y el backend de D1.

#### Punto final de la API Del backend del emisor al backend de D1: * [Eliminar consumidor](/secure-card-display/es/integrate-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#post-issuers-issuerid-consumers-consumerid-operations-delete) --- # 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/secure-card-display/es/get-started/mange-end-users/manage-end-user-life-cycle.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.