> 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/get-started/manage-cards/manage-card-life-cycle.md).

# Manage card life cycle

### Card life cycle and operations

The diagram below shows the different life cycle states of a card.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/L9kY7F0TAewuShMgZ4YR" alt=""><figcaption><p>Card life cycle state diagram.</p></figcaption></figure>

In addition to the state, each card exposes an `ongoingOperation` property.

This property indicates whether renewal has been initiated and activation of the reissued card is expected.

`ongoingOperation` is available in both the D1 API and the D1 SDK.

#### Card life cycle operations

You can perform card life cycle operations through:

* D1 API
* D1 SDK
* D1 portal

For API details, use the D1 API reference pages under [Integrate D1 API](/secure-card-display/integrate-d1-api.md).

#### Life cycle operation reasons

Provide a reason every time you perform a card life cycle operation.

The tables below summarize the available reasons and their impact.

**Suspend reasons**

| Reason           | Description                                                                                                                                     |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| CARD\_LOST       | <p>The card has been reported as lost. You can:<br>- resume the card using the reason <code>CARD\_FOUND</code>.<br>- request a replacement.</p> |
| CARD\_STOLEN     | The card has been reported as stolen. The card remains suspended until you explicitly request a replacement.                                    |
| CARD\_BROKEN     | The card is damaged and no longer works. The card remains suspended until you explicitly request a replacement.                                 |
| FRAUD            | The card is compromised. The card remains suspended until you explicitly request a replacement.                                                 |
| USER\_DECISION   | The end user has decided to temporarily suspend the card. The card can be resumed with `USER_DECISION` or `ISSUER_DECISION`.                    |
| ISSUER\_DECISION | The issuer has decided to temporarily suspend the card. The card can be resumed with `ISSUER_DECISION`.                                         |

**Resume reasons**

| Reason           | Description                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------- |
| CARD\_FOUND      | The card has been found and was previously suspended with the reason `CARD_LOST`.                       |
| ISSUER\_DECISION | The issuer has decided to resume the card.                                                              |
| USER\_DECISION   | The end user has decided to resume the card and the card was previously suspended with `USER_DECISION`. |

**Delete reasons**

| Reason           | Description                                                                |
| ---------------- | -------------------------------------------------------------------------- |
| CLOSED\_ACCOUNT  | The end user has closed the account and the card must be deleted/canceled. |
| CLOSED\_CARD     | The card must be deleted/canceled.                                         |
| CARD\_LOST       | The card has been reported as lost and must be deleted/canceled.           |
| CARD\_STOLEN     | The card has been reported as stolen and must be deleted/canceled.         |
| CARD\_BROKEN     | The card is damaged and must be deleted/canceled.                          |
| FRAUD            | The card is compromised and must be deleted/canceled.                      |
| USER\_DECISION   | The end user has decided to delete the card.                               |
| ISSUER\_DECISION | The issuer has decided to delete the card.                                 |

**Replacement reasons**

| Reason           | Description                                 |
| ---------------- | ------------------------------------------- |
| CARD\_LOST       | The card has been reported as lost.         |
| CARD\_STOLEN     | The card has been reported as stolen.       |
| CARD\_BROKEN     | The card is damaged and no longer works.    |
| FRAUD            | The card is compromised.                    |
| ISSUER\_DECISION | The issuer has decided to replace the card. |

**Renewal reasons**

| Reason           | Description                                                             |
| ---------------- | ----------------------------------------------------------------------- |
| USER\_DECISION   | The end user has decided to renew the card.                             |
| ISSUER\_DECISION | The issuer has decided to renew the card.                               |
| CARD\_EXPIRED    | The card has been renewed because it has expired or is about to expire. |

#### D1 API operations

Use these D1 API endpoints for life cycle operations:

* [Suspend a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-suspend)
* [Resume a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-resume)
* [Delete a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-delete)
* [Replace a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-replace)
* [Renew a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-renew)

You can retrieve the card list using [Get card list](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#get-issuers-issuerid-consumers-consumerid-cards).

If you need card details, use [Get card details](https://thales-dis-dbp.stoplight.io/d1-caas/i1ljucrgwy26a-get-card-details).

#### Renewal and replacement flows

**Automatic renewal**

Automatic renewal is available only for cards created with D1.

D1 monitors card expiry dates and can trigger renewal a few weeks before expiration.

**Manual renewal**

Manual renewal is available for cards created with D1 and for registered cards.

Trigger manual renewal using the [Renew a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-renew) endpoint.

If the card is registered (not created with D1), provide the new PAN and/or expiry date so D1 stays up to date.

**Manual replacement flow**

Manual replacement is available for cards created with D1 and for registered cards.

Trigger manual replacement using the [Replace a card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-replace) endpoint.

If the card is registered (not created with D1), provide the new PAN and/or expiry date so D1 stays up to date.

**New card activation**

Depending on your card product configuration, after renewal or replacement the new card may be created in the `INACTIVE` state.

There are three ways to activate the card:

* Activation at first card-present transaction with a valid PIN (cards created via D1 only).
* Manual activation using the D1 API (not yet available).
* Manual activation from the issuer application using the D1 SDK (not yet available).


---

# 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:

```
GET https://docs.payments.thalescloud.io/secure-card-display/get-started/manage-cards/manage-card-life-cycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.