Skip to content
Open source · Built for developers

Digital ID verification.
Your stack. Your rules.

Build digital ID checks into your own product. Verify signed credentials and decide which issuers to trust with open-source libraries for JavaScript, Kotlin, and Swift.

JavaScript Kotlin Swift
verification.flow
  1. 01

    Request what you need

    An age threshold. A name. A portrait.

  2. 02

    Verify the credential

    Signatures, digests, and device authentication.

  3. 03

    Establish issuer trust

    Your selected trust lists and issuer certificates.

Verified data. An explicit trust decision.
The libraries

Two libraries. One verification workflow.

Use ID Verifier for the credential flow, or use Trusted Issuer Registry independently when you already handle credential verification.

Credential verification

ID Verifier

Request selected information from digital IDs and verify the returned mdoc credentials. Issuer trust is handled through Trusted Issuer Registry.

  • Request individual claims, including yes/no age checks.
  • Check issuer signatures, signed data, validity, and device authentication.
  • Get per-document claims, validity, issuer trust, and failure reasons.
JavaScriptKotlinSwift
Issuer trust

Trusted Issuer Registry

Determine whether a document signing certificate was issued by an authority you trust. Use signed registry records, your own issuer certificates, or both.

  • Select AAMVA DTS, Universal Verify, or your own trusted issuer certificates.
  • Check certificate signatures and validity, with configurable CRL checks.
  • Get issuer metadata and specific reasons when trust cannot be established.
JavaScriptKotlinSwift

Open source under MPL-2.0. Source code, API documentation, and contribution guides live on GitHub.

Read the registry’s trust policy
Integration example · JavaScript

From a request to a verified answer.

Here’s a browser-based age check using the current ID Verifier API. Request just “over 21,” then verify the response and its issuer before accepting the answer.

Server · request.js

1. Create the request

Request an age threshold without asking for a full date of birth.

import {
  Verifier, DocumentType, Claim,
  generateNonce, generateJWK,
} from 'id-verifier';

const verifier = new Verifier();
const nonce = generateNonce();
const jwk = await generateJWK();

const request = verifier.createWebCredentialsRequest({
  documentTypes: [DocumentType.MOBILE_DRIVERS_LICENSE],
  claims: [Claim.AGE_OVER_21],
  nonce,
  jwk,
});

Browser · present.js

2. Ask the customer to share

Call from a user action, such as a button click. The customer reviews your request and chooses whether to share.

import { Verifier } from 'id-verifier';

const verifier = new Verifier();
const credentials = await verifier.requestCredentials(request);

Server · request.js (continued)

3. Verify and apply your policy

Verify the response against the saved context. Accept the age check only when the requested document is valid, its issuer is trusted, and the age claim is true.

const result = await verifier.processCredentials(credentials, {
  nonce,
  jwk,
  origin: 'https://your-app.example',
});

const document = result.processedDocuments.find(doc =>
  doc.valid &&
  doc.trusted &&
  doc.document.docType === DocumentType.MOBILE_DRIVERS_LICENSE
);

const ageCheckPassed =
  document?.claims[Claim.AGE_OVER_21] === true;

For best practice, keep nonce and jwk on your server.

Build with us

Better verification is a shared effort.

Try the libraries, inspect the implementation, or help improve interoperability. Bug reports, test cases, documentation, and code contributions are welcome.

Explore on GitHub