#Overview

Verifier2 Service enables organizations to verify digital identity credentials. It sends a presentation request to a holder's wallet, receives the signed credential presentation in response, and validates it against configurable policies. Credential exchange runs over OID4VP v1.0, with additional support for the Digital Credentials API and ISO/IEC 18013-7. Supported credential formats include W3C VC, SD-JWT VC (IETF), ISO 18013-5 mDL, and ISO 23220 PhotoID.

#Supported Standards

#Features

• Credential Verification - Request and verify various digital credential types and formats (W3C, SD-JWT, mDL) via OID4VP V1.
• Policies - Apply built-in or custom policies to control validation checks such as expiry, schema conformance, and trust anchor verification.
• Callbacks & SSE - Get notified when a verification session completes via a webhook callback or a Server-Sent Events (SSE) stream, including the session status, policy results, and presented credentials.
• Session data ejection (MongoDB TTL) - Presentation sessions can contain PII (holder identifiers, disclosed attributes, device metadata). Finite sessions are deleted automatically by MongoDB TTL. See Session Data Ejection

#Getting Started

• Setup – Configure a verifier service (set default signing keys, certificate chains, and URL hosts during initial setup to simplify future verification sessions)
• 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
• Verify credentials via Digital Credentials API – Walkthrough on how to verify credentials using the DC API