Revocation
Each credential carries a revocation number. To revoke, the issuer marks that number as revoked on its own service. Revocation is permanent; a revoked credential cannot be restored. Revocation needs a database on the issuer service. Without one, the issuer has no record to mark.How verifiers learn about it
The issuer publishes revocation status in one or both of these ways:
A verification program can ask AIR to check revocation during verification. Verifiers can also check it themselves on their backend.
Token status list in brief
- The list is split into partitions of a fixed size. Each credential knows its partition and position.
- The issuer republishes the list on a schedule: every few minutes for urgent cases such as fraud, hourly or nightly for routine changes.
- The partition size cannot change after issuing starts, because each credential already records its position.
- It only represents valid or revoked. There is no “suspended” state.
Updating a credential
To change a claim, such as a tier upgrade, the issuer revokes the old credential and issues a new one. Deduplicate by recipient and program so a user does not hold two current versions.Expiry
Every credential has an expiry date set at issuance. After it passes, verification fails without any action from the issuer. Short-lived credentials reduce how much revocation is needed.Common issuance failures
For revocation commands and status list setup, see Managing your credentials.