> 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/card-life-cycle.md).

# Card life cycle

Using the D1 API, your **issuer backend** can suspend, resume, and delete cards (see [API summary](/tokenization/integrate-the-d1-api/d1-api-summary.md) for details).

Suspending or resuming a card does not affect related digital cards. For example, an **End User** can keep using digital cards after you suspend a lost card.

Deleting a card deletes all related digital cards.

### Card replacement

Replace cards when they are lost or stolen.

To trigger a replacement, call [Replace card](/tokenization/integrate-the-d1-api/d1-api-summary.md).

D1 notifies the payment network **TSP** to keep existing digital cards linked to the replaced card.

Flow overview:

<figure><img src="/files/n7vO5grYoaX4Hxb1yrPy" alt=""><figcaption><p>Card replacement: D1 updates the payment network TSP and the Token requestor</p></figcaption></figure>

### Card renewal

Cards are renewed when they expire.\
For cards created by D1, D1 triggers renewal automatically.\
Your **issuer backend** can also trigger renewal using [Renew card](/tokenization/integrate-the-d1-api/d1-api-summary.md).

{% hint style="info" %}
**Note:**

For cards registered in D1, your **issuer backend** must notify D1 by calling [Renew card](/tokenization/integrate-the-d1-api/d1-api-summary.md).
{% endhint %}

D1 notifies the payment network **TSP** so existing digital cards keep working after renewal.

This uses the same flow as card replacement.

### End User notifications (optional)

D1 can also send notifications to the **End User** for some renewal scenarios. This is optional. See [End User notifications](/tokenization/implement-tokenization/end-user-notifications.md).


---

# 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/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.