Revoke a document

Revoking a document makes it permanently invalid: verifiers that check its status, including LutraID checks by default, reject it once the change is published. It can't be undone. LutraID issues documents with a status list, which is what makes them revocable.

Revoking one

  1. Open Records and open the issuance record for the offer.
  2. In the record's Documents section, find the document the wallet added.
  3. Choose Revoke document, fill in Reason (optional) if you like, and confirm with Revoke document.

The reason is shown on the record to your team. The record also keeps who revoked the document and when. Revoking can't be paused or reversed; there is no suspend. To give the customer a valid document again, send a new offer.

Owners and admins can revoke documents. Other roles see the record but not the button.

Whether a document can be revoked

A document that can't be revoked shows "This document was issued without a status list, so it can't be revoked." in the record's Documents section.

What happens after

Revocation is recorded straight away. Publishing it to the status list that wallets and verifiers check takes a little longer, and the record shows where it stands:

Status on the recordMeaning
Revoked. Publishing the change nowThe change is being published
Revocation publishedChecks of this document fail within about five minutes, once verifiers refresh
Revoked, but not published yetPublishing failed for now. LutraID keeps trying; checks may still find the document valid until it succeeds

If publishing stays failed, ask support and include the record's reference.

What else affects validity

LeverEffect
Document lifetimeOne year for both SD-JWT VC and ISO mdoc: a natural backstop even without revocation
Signing certificateRetiring one affects every document it signed: a blunt instrument, not a substitute for revocation
CheckTighten what your own verifiers accept, independent of what the issuer has revoked

For high-stakes cases where a document can't be revoked, issue a replacement with correct data and treat the newer one as authoritative in your own systems.

Was this page helpful?