---
title: "Static Verification Policies"
description: "Predefined and covering a variety of common use cases, enabling developers to verify credentials easily."
stack: "Community Stack (open source) — 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/community-stack/verifier/credential-verification/policies/static-verification-policies
generated: 2026-07-20
---
# Static Verification Policies

## Static Verification Policies

Predefined_ and covering a variety of common use cases, enabling developers to verify credentials easily.

### Signature

Used as `signature`, it verifies the signature of the W3C VC.

### Expired

Used as `expired`, it verifies the VC based on the expiration date.

### Not Before

Used as `not-before`, it verifies VC based on the valid-from date.

### Schema

Used as `schema`, it verifies against the associated JSON schema. Note that the attribute credentialSchema must be
set and the JSON schema must be accessible by the http URL.

### Revoked Status List

Used as `revoked-status-list`, it verifies VC status based on Verifiable Credentials
[Status List v2021](https://www.w3.org/TR/2023/WD-vc-status-list-20230427) standard, against the following values:

* purpose = revocation (case-sensitive)
* expected valid value = 0x0 (unset)

### Holder Binding

Used as `holder-binding`, it check that presenter (Issuer of Verifiable Presentation) is the correct subject throughout
the credentials contained within the presentation; so that you can't just present a credential of a different user you
ve found somewhere within your Verifiable Presentation.