> 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/ecom/implement-d1-ecom-enablement/handle-card-lifecycle-events.md).

# Handle card lifecycle events

Card lifecycle events can affect token metadata over time. Common events include renewal, replacement, and deletion.

* If card details change (PAN and/or expiry date), D1 eCom Enablement notifies your merchant gateway to refresh token metadata.
* If a card is deleted, the issuer backend notifies D1 eCom Enablement.

### Card renewal or replacement

<figure><img src="/files/h3HVeHAda46sN1uCRuAU" alt="Card renewal or replacement flow"><figcaption><p>Card renewal or replacement notification</p></figcaption></figure>

{% hint style="info" %}
Integration between D1 eCom Enablement and the issuer backend is out of scope. It varies by issuer integration model.
{% endhint %}

### Card deletion

<figure><img src="/files/ZW6tCXX5Sp0LeRNCFsp3" alt="Card deletion flow"><figcaption><p>Card deletion notification</p></figcaption></figure>


---

# 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/ecom/implement-d1-ecom-enablement/handle-card-lifecycle-events.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.