> 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/implement-tokenization/post-tokenization-requests/life-cycle-management/digital-card-life-cycle.md).

# Digital card life cycle

A digital card can move through several states until it is deleted.

Some payment network **TSPs** support digital card expiration and renewal. Align this behavior during **Tokenization** design with the issuer and the **Token requestor** (for example, **xPay Wallets**).

Use the sections below to understand who can trigger each **LCM** event.

### Life cycle management from the token requestor

A request to change a digital card state can come from the **Token requestor**.

This is often initiated by the **End User** in the token requestor UI or self-service tools.

In many implementations, the Token requestor only sends delete requests to the payment network **TSP**. Suspension and resumption are often handled locally by the digital wallet application.

<figure><img src="/files/XgtdS5Rr7ACQp9iPcylW" alt=""><figcaption></figcaption></figure>

APIs involved are:

* [Notify digital card operation](/tokenization/integrate-the-d1-api/d1-api-summary.md). Notifies your **issuer backend** that an event occurred on the digital card.
* [Get operation](/tokenization/integrate-the-d1-api/d1-api-summary.md). Optionally retrieves operation details.
* [Get details](/tokenization/integrate-the-d1-api/d1-api-summary.md). Optionally retrieves full digital card details.

Choose which APIs to call based on your servicing and fraud needs.

### Life cycle management from the issuer

Your **issuer backend** can also request digital card state changes.

For example, an **End User** can ask customer service to delete digital cards after a device loss.

<figure><img src="/files/4GxMt8xU3zxYwuDEyobJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/v8ZwY7XRSLJ87eX3TASZ" alt=""><figcaption></figcaption></figure>

With the `digitalCardId`, you can perform these operations:

* [Suspend](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md). Requests suspension from the payment network **TSP**.
* [Resume](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md). Resumes a previously suspended digital card.
* [Delete](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md). Permanently deletes the digital card.

{% hint style="warning" %}
You cannot resume a deleted digital card.
{% endhint %}

After digital card deletion, D1 can also send notifications to the **End User**. This is optional and might be required by some token requestors. See [End User notifications](/tokenization/implement-tokenization/end-user-notifications.md).

### Digital card renewal

A digital card can expire.

When supported, the payment network **TSP** renews the digital card and notifies the **Token requestor**.

Issuer notification is optional (opt-in).

<figure><img src="/files/rmuCBct1woUnW7dNWAZG" alt=""><figcaption></figcaption></figure>

APIs involved are:

* [Notify digital card operation](/tokenization/integrate-the-d1-api/d1-api-summary.md). Notifies that an event occurred on the digital card.
* [Get digital card credentials](/tokenization/integrate-the-d1-api/d1-api-summary.md). Optionally retrieves the renewed digital card credentials. The payment network **TSP** keeps the same `digitalCardId`.


---

# 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/tokenization/implement-tokenization/post-tokenization-requests/life-cycle-management/digital-card-life-cycle.md?ask=<question>&goal=<endgoal>
```

`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.