> 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/update-token-state-from-wallet-provider.md).
# Update token state from wallet provider
Some events trigger a token state update initiated by the wallet provider or the payment network **TSP** (for example, VTS or MDES).
Typical examples:
* End user deletes the token from the digital wallet application.
* End user loses or finds their phone and uses the wallet provider portal to suspend, resume, or delete tokens.
* Issuer uses the payment network customer care interface (CCI) to suspend, resume, or delete tokens.
### Flow
Token state update initiated by the wallet provider or payment network TSP.
{% stepper %}
{% step %}
#### 1. Initiate the token state update
The wallet provider or payment network TSP initiates the token state change.
{% endstep %}
{% step %}
#### 2. Receive notifyVirtualCardChange
When the operation 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).
Key parameters:
| Parameter | Description |
| ------------------ | ------------------------------------------------------------------------- |
| `x-correlation-id` | Correlates this callback with the related token state update. |
| `virtualCardId` | Identifies the updated token. |
| `action` | Specifies the action performed by the payment network or wallet provider. |
| {% endstep %} | |
| {% endstepper %} | |
{% hint style="info" %}
Handle `notifyVirtualCardChange` idempotently. Callbacks can be duplicated or delayed.
{% 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)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/post-enrolment/token-life-cycle-management/update-token-state-from-wallet-provider.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
