> 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 provides APIs and a web UI to manage an end user's virtual and physical cards.

### Manage end users

Register an end user before creating a card. The end user profile stores the information needed for card management and Tokenization services.

Use [Manage end users](https://docs.payments.thalescloud.io/home/card-creation-and-management/manage-end-users.md) to register, update, and delete end user information.

### Manage cards

D1 supports virtual and physical card creation, personalization, delivery, and LCM.

Creating a physical card initiates personalization and shipment. D1 also orchestrates digital services, including Tokenization, 3DS, and Click to Pay enrollment.

### Use cases

#### Card management

| API                     | Description                                                                                                   |
| ----------------------- | ------------------------------------------------------------------------------------------------------------- |
| Register end user       | **Required.** Creates the end user profile used for issuing and managing cards.                               |
| Create card             | **Required.** Creates a virtual or physical card. Physical card creation starts personalization and shipment. |
| Get card status         | **Conditional.** Retrieves the card, personalization, and delivery status.                                    |
| Notify card operations  | **Conditional.** Sends card lifecycle and status updates to the issuer backend.                               |
| Renew and replace card  | **Required.** Renews or replaces a card and requests that the TSP links existing digital cards.               |
| Suspend and resume card | **Required.** Changes a card's operational status.                                                            |

#### Track card orders

| API                    | Description                                                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Get card status        | **Required.** Retrieves the current order status from card creation through personalization, shipment, and delivery.         |
| Notify card operations | **Optional.** Sends status changes to the issuer backend, enabling proactive end user communications and exception handling. |

#### Securely display card details

| API                   | Description                                                                                               |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| Display card metadata | **Required.** Retrieves non-sensitive card information for display in the issuer application.             |
| Display card details  | **Conditional.** Uses the D1 SDK to securely present sensitive card details to an authenticated end user. |
| Display PIN           | **Optional.** Uses the D1 SDK to securely display the card PIN to an authenticated end user.              |

#### Manage end user information

| API                         | Description                                                                    |
| --------------------------- | ------------------------------------------------------------------------------ |
| Update end user information | **Optional.** Updates the end user's registered information.                   |
| Delete end user             | **Required.** Permanently deletes the end user and associated child resources. |

#### Manage card settings

| API                    | Description                                                   |
| ---------------------- | ------------------------------------------------------------- |
| Get card settings      | Retrieves card limits and domain controls.                    |
| Update card limits     | Updates card spending limits.                                 |
| Update card controls   | Updates card domain controls.                                 |
| Notify card operations | Sends card status and settings updates to the issuer backend. |

#### Support card operations

| Capability                    | Description                                                                                     |
| ----------------------------- | ----------------------------------------------------------------------------------------------- |
| Search PAN                    | Searches PANs by using multiple criteria.                                                       |
| View PAN details              | Displays card information for a selected PAN.                                                   |
| View end user details         | Displays end user information for a selected card.                                              |
| View and update card limits   | Lets authorized operations users manage spending limits.                                        |
| View and update card controls | Lets authorized operations users enable or disable card channels, including NFC and e-commerce. |


---

# 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/home/card-creation-and-management/overview.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.
