Appearance
Universal Verifier
The Universal Verifier API provides a unified interface for verifying Verifiable Credentials (VCs) and Verifiable Presentations (VPs). The Universal Verifier supports JSON-LD, JWT, SD-JWT VCs and VPs.
It supports two primary verification modes:
- Standard verification — verify credentials directly via the REST API.
- OID4VP-based verification — verify credential presentations using the OpenID for Verifiable Presentations (OID4VP) protocol.
Standard verification
In this mode, you call the Universal Verifier REST endpoints to check the authenticity, status and schema-compliance of VCs. This mode is suitable for back-end systems or services verifying credentials on your behalf.
No special configuration is required beyond having the verification endpoint and any necessary api keys.
OID4VP-based verification
In this mode, the Universal Verifier supports the OpenID for Verifiable Presentations (OID4VP) protocol, enabling interactive wallet-driven presentation flows.
To use OID4VP verification, your verifier must first be configured using the Verifier Configuration API. This one-time setup registers required VCs, claims (either all or selectively disclosable), request signing keys, supported formats, and any required proof mechanisms.
Once configured, you can use the endpoints described in Verifier OID4VP API to handle the OID4VP flow where wallets present credentials to your service.
Summary
| Verification Mode | Description | Requires Configuration? |
|---|---|---|
| Standard | Direct REST API verification | No |
| OID4VP | Wallet-driven presentation flow via OID4VP | Yes — via Verifier Configuration |
Next Steps
- To verify credentials directly, continue with the Standard Verification API.
- To enable wallet-driven presentation flows, first complete the Verifier Configuration.
API Reference
See API Reference.