Overview
walt.id's Verifier Service enables organizations to verify digital identity credentials in a secure, privacy‑preserving and standards compliant way. Users can also use a management GUI for handling multiple verifier configurations, creating credential requests, applying verification policies and viewing analytics.
This service is deprecated in favour of the new Verifier2 Service.
It is disabled by default and only available for existing integrations by enabling the verifier-draft-routes feature. The Verifier2 service is built around the stable release of the OID4VP 1.0 specification. We would recommend using the verifier2 service for new projects. Documentation for the verifier2 service can be found here.
Feature Flag
This legacy Verifier Service requires the verifier-draft-routes feature in _features.conf. The feature defaults to off. When it is disabled, creating a service with "type": "verifier" is rejected (use "verifier2" instead).
Enable it only if you need draft-protocol (OID4VP Draft 14/20) verifiers or existing integrations that depend on them.
Supported Standards
| Credential Formats: | SD-JWT VC (IETF), W3C VC (v1.1+, v2.0), ISO 18013-5 mDL |
| Credential Exchange: | OID4VP (Draft 14, 20), ISO/IEC 18013-7 |
| Signature Algorithms: | ed25519, secp256k1, secp256r1, RSA |
Core Features
Credential Exchange
Credential verification is performed via OID4VP. Authorization requests can be created using the Presentation Definition protocol. Multiple draft versions (14 and 20) are supported. Requests for ISO/IEC 18013-7 compliant mDLs are supported as well.
Credential & Attribute Request Definition
Credential requests define the credential formats, types and attributes that should be provided by a wallet. They can be expressed simply by combining credential types and formats, with full flexibility using Presentation Definition. Support for DCQL will be added soon.
Credential Validation
Received credentials are validated against configurable policies. Static checks such as signature verification and schema compliance are provided out of the box. Parameterized policies enable features like issuer allow lists and webhooks, and custom logic can be implemented with REGO policies executed by the Open Policy Agent. See the Policies section for details.
Management & Analytics
The Enterprise GUI allows creating and viewing credential requests, applying verification policies and monitoring sessions through the events dashboard.
Session data ejection (MongoDB TTL)
Presentation sessions (and related child documents such as token responses and verification results) can contain PII.
Finite sessions are ejected automatically by MongoDB TTL, controlled by expires_in_seconds when
creating the session. See Session Data Ejection
Getting Started
- Setup – Configure a verifier service
- Verify W3C credentials – Walkthrough on how to verify a W3C credential
- Verify SD-JWT VC credentials – Walkthrough on how to verify an SD-JWT VC credential
- Verify mDL/mDOC credentials – Walkthrough on how to verify an mDL/mDOC credential