---
title: "Overview"
description: "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,…"
stack: "Enterprise Stack (commercial) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/services/credential-status-service/overview
generated: 2026-07-20
---
# 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:

- [Bitstring Status List v1.0](https://www.w3.org/TR/vc-bitstring-status-list/)
- [StatusList2021](https://www.w3.org/TR/2023/WD-vc-status-list-20230427)
- [RevocationList2020](https://w3c-ccg.github.io/vc-status-rl-2020)
- [TokenStatusList](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-status-list-08) (only [Direct Trust](#trust-and-signing-models) model)

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

<table>
    <thead>
        <tr>
            <td rowspan="2">Format</td>
            <td rowspan="2">RevocationList2020 (w3c)</td>
            <td rowspan="2">StatusList2021 (w3c)</td>
            <td rowspan="2">BitstringStatusList (w3c)</td>
            <td colspan="2">TokenStatusList - <a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-status-list-15">draft#15</a> (ietf, mdoc)</td>
        </tr>
        <tr>
            <td>JWT</td>
            <td>CWT</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>JWT</td>
            <td>&check;</td>
            <td>&check;</td>
            <td>&check;</td>
            <td>&dash;</td>
            <td>&dash;</td>
        </tr>
        <tr>
            <td>SD-JWT</td>
            <td>&check;</td>
            <td>&check;</td>
            <td>&check;</td>
            <td>&dash;</td>
            <td>&dash;</td>
        </tr>
        <tr>
            <td>IETF SD-JWT VC<br>(x509 / did)</td>
            <td>&dash;</td>
            <td>&dash;</td>
            <td>&dash;</td>
            <td>&check;</td>
            <td>&check;</td>
        </tr>
        <tr>
            <td>ISO mDOC</td>
            <td>&dash;</td>
            <td>&dash;</td>
            <td>&dash;</td>
            <td>&check;</td>
            <td>&check;</td>
        </tr>
    </tbody>
</table>

&check; - supported
<br/>
&cross; - not supported
<br/>
&dash; - not available

**Note:**

For an overview on the credential lifecycle concept, please refer to the [credential lifecycle section](../../../community-stack/1.concepts/6.credential-lifecycle/credential-status-and-revocation.md).

#### Trust and Signing Models

We only support the Direct Trust model for the TokenStatusList standard.

* **Same Entity** (Direct Trust) - the entity issuing the credential also issues the Status List
  * Re-uses the same keys (JWK/DID/x5c) 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](https://docs.walt.id/enterprise-stack/services/credential-status-service/setup.md) - How to set up a credential status service
- [Manage](https://docs.walt.id/enterprise-stack/services/credential-status-service/manage.md) -  How to create, use and manage status credentials.