> 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/classic-tokenization/use-cases/post-enrolment/token-life-cycle-management/renew-tokens-from-the-tsp.md).

# Renew tokens from the TSP

Token renewal applies only to existing tokens. These tokens are already provisioned and activated in a digital wallet application.

Agree with your payment network on the **LCM** policy to apply to issued tokens. Based on that policy, the **TSP** issues tokens with an appropriate expiration date.

When a token expires, the payment network **TSP** can reprovision it. It provisions a new token with a new expiration date.

You can opt in to receive a callback when the renewal completes (or fails).

### Flow

This diagram shows the token renewal flow. It also shows the callback used to confirm the result.

<figure><img src="/files/rdG2WSzhbi63YiPn66zT" alt="Payment network TSP token renewal flow."><figcaption><p>Token renewal initiated by the payment network TSP.</p></figcaption></figure>

### Handle the callback

When the renewal completes (or fails), you receive `notifyVirtualCardChange`.

See [`notifyVirtualCardChange`](https://thales-dis-dbp.stoplight.io/docs/digital-payment/b3A6MjU4Nzg1MjE-notify-issuer-about-any-virtual-card-token-change).

**notifyVirtualCardChange** parameters:

| Parameter          | Description                                                              |
| ------------------ | ------------------------------------------------------------------------ |
| `x-correlation-id` | Correlates this callback with the related token renewal operation.       |
| `virtualCardId`    | Identifies the updated token.                                            |
| `action`           | Specifies the action performed. For token renewal, the value is `RENEW`. |

{% hint style="info" %}
Handle `notifyVirtualCardChange` idempotently. Callbacks can be duplicated or delayed.

This currently applies to:

* Mastercard
* Visa
  {% endhint %}

### Related documentation

* [Update token state from issuer backend](/classic-tokenization/use-cases/post-enrolment/token-life-cycle-management/update-token-state-from-issuer-backend.md)
* [Update token state from wallet provider](/classic-tokenization/use-cases/post-enrolment/token-life-cycle-management/update-token-state-from-wallet-provider.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:

```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/post-enrolment/token-life-cycle-management/renew-tokens-from-the-tsp.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.