UbID Verifier
Request. Review. Trust.
The cryptographic verification layer that lets any application request proof from verifiable credentials — with the holder always in control of what is shared.
How Verification Works
An OpenID4VP flow the holder controls — step by step.
Login triggered
The user selects Login or another verification action inside the client application.
Request created
Verifier generates an OpenID4VP presentation request with the required policy and claims.
Holder reviews in Vault
The request opens in UbID Vault. The holder sees the requesting party, purpose, and every field that will be disclosed.
Credential selected
The holder picks a matching credential and confirms — or cancels at any time with no consequence.
Cryptographic validation
Verifier checks holder binding, issuer signature, audience, disclosures, validity, and the applicable policy.
Session established
The client application receives a controlled verification result and creates its own authenticated session.
Privacy & Holder Control
The application defines what it needs. The holder decides what is shared.
Consent before disclosure
Vault shows the exact credential and fields requested. The holder must authorise before anything is sent.
No credential in callback
The browser callback carries only a short-lived code and state — never names, emails, or cryptographic evidence.
Cancel at any step
Cancelling in Vault stops the presentation without deleting the credential or affecting the Vault account.
Server-side session only
The client creates its session only after exchanging the code and validating the signed Verifier result through a trusted server channel.
Presenting Credentials
Open the request
Scan the QR code with Vault on another device, or tap Open with UbID Vault on the same device.
Review the request
Check the requesting party, stated purpose, and which credential and fields are being asked for.
Select & confirm
Choose the credential, review every disclosed field, then tap Send to authorise — or Cancel to stop.
Verification Result
After a successful presentation the Verifier returns a structured, tamper-evident result. The client application uses it to establish a protected session — not the raw credential.
The verified UbID subject identifier associated with the presentation.
The verification policy applied — for example, UbidBasic.
The assurance mechanism; typically openid4vp+dcql.
Correlates the end-to-end verification transaction for audit.