For the complete documentation index, see llms.txt. This page is also available as Markdown.

Creating a Verifier

A Verifier is created inside your deployment's operator console — not as a separate portal deployment. It runs on the same service (and uses the same Keycloak login) as the Issuer; you register a Verifier by binding it to a DID.

  1. In the operator console sidebar, open Verifiers.

  2. In Available DIDs, select the DID the Verifier will use to sign authorization requests. If no DID is available yet, open DIDs first and create one (a did:key or did:web).

  3. Click Create Verifier.

  4. Your Verifier appears in the Verifiers list, identified by its DID. Open its Dashboard to view the Verifier's details (its Verifier ID).

Verifiers screen in the operator console
The Verifiers screen before any Verifier is registered
Create Verifier form with Available DIDs
The Create Verifier form — select the DID the Verifier will sign authorization requests with
Verifier details with the Verifications tab
Verifier details — the Verifier ID and the Verifications tab

Authorization (presentation) requests are created — and verification sessions tracked — from the Verifier's Verifications tab, or through the Verifier API: POST /verifiers/{verifierId}/authorization-requests (with /qr-code) and GET /verification-sessions/{id}. The Verifier shares requests as QR codes or deep links, verifies presented SD-JWT VC and JWT-VC-JSON credentials, and uses the same admin Bearer token as the rest of the deployment — see Verifying Credentials, the Verifier API, and Authenticating to Your Deployment.

You can also create a Verifier programmatically with POST /agent/verifier — see the Verifier API.

Last updated