Revoke a credential
Revocation is not available yet. This page says what that means in practice and what to use instead.
LutraID does not publish status lists, and there is no endpoint that invalidates an issued credential. A credential that is already in a wallet stays valid until it expires.
What you can control
| Lever | Effect |
|---|---|
| Offer expiry | An unclaimed credential offer stops working; the wallet never receives a credential |
| Credential lifetime | Fixed at one year for SD-JWT VC and 365 days for mdoc |
| Issuer signing key | Retiring a key affects credentials it signed, but it is a blunt instrument — it invalidates every credential under that key |
| Verification profile | Tighten what your own verifiers accept |
What to do meanwhile
If the facts behind a credential change, issue a replacement with the correct data and treat the shorter-lived one as authoritative in your own systems. For high-stakes cases, keep the credential lifetime as short as your process allows.
When this changes
Revocation status lists and external revocation checks are on the roadmap; assurance policies already carry a requireRevocationChecks flag that is not yet enforced. See Revocation for the concept and Trust and production for the full list of what is not yet implemented.