Presentation
A verifierThe party that checks a presented credential: signature, issuer in the trust list, status and policy. Also called relying party. (a website, an employer, a gate) asks the wallet for a credential; the person approves; the verifier computes the result locally, without asking the source. The protocol is OpenID4VP (OpenID for Verifiable Presentations)The protocol a verifier uses to request a credential from a wallet and receive the presentation. 1.0 (the EU profile HAIP (High Assurance Interoperability Profile)The OpenID4VC profile that fixes the choices for high-assurance use, as in the EUDI Wallet. 1.0) and the query language is DCQL (Digital Credentials Query Language)The query language a verifier uses in OpenID4VP to say which credentials and which fields it needs..
The request
- The request is signed. The verifier is identified by the fingerprint of its access certificateThe X.509 certificate a relying party signs its requests with; its client identifier is derived from this certificate's hash. (client_id = x509_hash:…A client identifier scheme from HAIP: the identifier is the base64url SHA-256 hash of the relying party's access certificate.); the wallet checks the signature, the certificate and the verifier's entry in the trust listA signed list of a country's root certificates, issuers and registered relying parties. Today trust in Tamga rests on these lists; a shared ledger comes later., and shows the person the registered purpose and the requested fields.
- A verifier may only ask for fields within the scope of its entry in the trust list.
- The response is encrypted with the verifier's key.
Channels
| Channel | When | Status |
|---|---|---|
QR code / link (openid4vp://) | a website or kiosk on another device | live |
| Digital Credentials API | a website in the browser on the same phone (the browser opens the wallet) | verifier ready; first listed wallet: Android code written, not yet built into the app or device-tested; no iOS yet |
| ISO 18013-5 proximity (BLE) | a gate, turnstile or counter — in person | implemented; device testing pending (until then a short-lived pass) |
Verification and three outcomes
The verifier checks, in order, the signature, the issuer's authorisation in the trust list, the holder bindingTying a credential to a key that only the holder's device has, so a copied credential cannot be presented., the validity period and the revocation status. The result has three values:
| Outcome | Meaning |
|---|---|
ACCEPTED | the credential is valid |
REJECTED | the credential is invalid; the failing step is reported |
INDETERMINATE | cannot be verified right now (e.g. the status list is stale) — it does not mean the credential is bad |
import { verifyPresentation } from "@tamga-network/verifier";
const { result, claims } = await verifyPresentation({
presentation, aud, nonce, policy, policyCredentialId: "diploma", trust, statusCache, // full example: Code examples
});
if (result.outcome === "ACCEPTED") {
// claims: only the fields the policy asked for. Log field names only, never values.
}Your own server or the hosted one?
- Tamga Verify (
verify.tamga.network): the hosted verifier and page kit; the result is given only to your server, and only once. Guide: GUIDE-0001. - Your own server:
@tamga-network/verifier. Guide: GUIDE-0002.
Details
- Protocol: SPEC-PROTO-0002, verification pipeline: SPEC-API-0001