> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gr4vy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network token lifecycle management

> Managing the full lifecycle of network tokens

The system has been set up to automatically keep your network tokens up to date.
Updates are automatically received when the underlying card receives any updates, and these updates are
applied to the stored card details in the system.

The card holder can interact with their card in multiple ways which can result in these
lifecycle events.

* The contract with the issuer is terminated rendering all cards and related tokens
  invalid. In this case, all the associated network tokens are terminated and deleted.
* A user reports a card lost or stolen or damaged. In this case, the issuer issues a new card and all
  the associated tokens stay active but any data related to the underlying card number may
  change, for example, the last four digits of the card may change.
* The card expires. In this case, the issuer issues a new card and all
  the associated tokens stay active but any data related to the underlying card number may
  change, for example, the expiration date of the card may change.
* The user triggers a token revocation from the issuer side, for example from the issuer's
  mobile banking app. In this case, any of the associated network tokens may be
  terminated and deleted.

All of these events are automatically managed when you use the vault.

## Usage data

Using different instruments per transaction attempt
is possible. Insight is provided as to which instrument was used per
transaction attempt via the **retry event report**. This report can be fetched via the API or
via the dashboard. In the report, the used instrument is listed per transaction attempt.

If the first attempt was done using the original card, and a retry was done using a
network token, then the transaction shows as having used a "network token" in the dashboard.

## Manual lifecycle management

Using the following endpoints it is possible to manually manage the token lifecycle for
a stored token. Using these endpoints changes the status at the respective scheme
token service and notifies the issuer.

* [Suspend token endpoint][suspend] - Used to temporarily turn off a provisioned token. The token is temporarily suspended.
  The token can be resumed by using the `/resume` API. This API is only supported for Visa cards.

* [Resume token endpoint][resume] - Used to re-enable a provisioned token. The token status
  changes from its previously suspended state into the active state. This API is only supported for Visa cards.

* [Delete token endpoint][delete] - Used to permanently remove a provisioned token. The token is deleted and needs to
  be re-provisioned.

[suspend]: /reference/network-tokens/suspend-network-token

[resume]: /reference/network-tokens/resume-network-token

[delete]: /reference/network-tokens/delete-network-token