# Revoke by issuer

In this phase, the Issuer revokes the VDC after it has been
issued to a user. This will remove the local VDCs from
**all** devices. The user will no longer have the option to add the
VDC to another device (including the same one) in the
future.

> [!NOTE]
> **Note:** This scenario is different from a [user deleting the VDC](https://developers.google.com/wallet/identity/provisioning/overview/delete-by-user) from their device. When a user deletes the VDC from their Google Wallet app, it is removed from **that** device only. The VDC remains active with the Issuer and can be added to another dvice (including the same one) in the future.

## Request flow

![](https://developers.google.com/static/wallet/identity/provisioning/overview/images/revoke-by-issuer.png)

## Flow description

| Step | Source | Description |
|---|---|---|
| 1 | Issuer servers | The Issuer revokes the VDC and notifies Google by calling the \`notifyCredentialStatusUpdateAvailable\` method. |
| 2 | Google | Google uses the \`getCredentialStatus\` method to request the new status of the VDC. |
| 3 | Issuer servers | The Issuer returns the \`revoked\` status. |
| 4 | Google | Google notifies the user's device(s) that the credential has been revoked. |
| 5 | Android-powered device | The user's devices delete the VDC from the Google Wallet app and notify Google on success. |
| 6 | Google | Google notifies the Issuer that the VDC has been deleted from the user's device(s). |