Overview

The Credential Status service enables users to create, update, and manage status credentials. Status credentials can have different purposes depending on the use-case. The most common purpose is revocation. Currently, the API supports the following credential status standards:

You can refer to the table below on which standards are supported by which credential format

Format RevocationList2020 (w3c) StatusList2021 (w3c) BitstringStatusList (w3c) TokenStatusList - draft#08 (ietf, mdoc)
JWT CWT
JWT ✓ ✓ ✓ ‐ ‐
SD-JWT ✓ ✓ ✓ ‐ ‐
IETF SD-JWT VC
(x509 / did)		 ‐ ‐ ‐ ✓ ✓
ISO mDOC ‐ ‐ ‐ ✓ ✓

✓ - supported
✗ - not supported
‐ - not available

For an overview on the credential lifecycle concept, please refer to the credential lifecycle section.

Trust and Signing Models

  • Same Entity (Direct Trust) - the entity issuing the credential also issues the Status List
    • Re-uses the same keys (JWK/DID) resolution method used for the Referenced Token (credential)
  • Delegated Entity (X.509 Chain) - status management is outsourced to a different entity (Status Issuer)
    • Uses X.509 certificates
    • The Status Issuer's certificate contains the specific id-kp-oauthStatusSigning to prove it is authorized to sign status lists

Get Started

  • Setup - How to set up a credential status service
  • Manage - How to create, use and manage status credentials.
Last updated on January 26, 2026
SetupSetup