Integrate in 4 steps

One npm package. A component for the frontend, plus two short routes on the backend: one opens the session with your API key, one verifies the proof, so the attendee can't fake the result.

Install the package

npm i @digigo/verify

One dependency. Works in any React app.

Open sessions with your API key

// your key opens the session, server-side; the browser never sees it
import { createSessionRoute } from "@digigo/verify/server";

export const { POST } = createSessionRoute({
  apiKey: process.env.DIGIGO_API_KEY!,
});

Your key is a secret and stays here, in your server env. The browser only ever gets a short-lived session token, good for one verification.

Drop the component in your frontend

// one component runs the whole QR flow; hand the proof to your route
import { DigiGoVerify } from "@digigo/verify/react";

<DigiGoVerify
  onResult={(c) => fetch("/api/verify", {
    method: "POST",
    body: JSON.stringify({ proof: c.proof }),
  })}
/>

Calls that route, renders the QR and runs the mint → poll flow, styled out of the box. onResult fires once with the credential; POST its proof to your route.

Verify on your backend

// app/api/verify/route.ts: one re-export, verifies on your backend
export { POST } from "@digigo/verify/server";

That one line is the whole endpoint. It fetches DigiGo's public JWKS once, then verifies every proof's signature locally. No key, no callback. This is the real gate: a browser can be tampered with, your server can't.

What you receive

{
  "format": "jws",
  "proof":  "eyJhbGciOiJFZ…",
  "publicSignals": {
    "indian": "INDIAN",
    "ageAbove18": true,
    "nullifier": "a3f9…"
  }
}

indianINDIAN · NOT_INDIAN
nullifierper-event pseudonym for de-dup not an identity
ageAbove18only if the event asks for it

⚠ Absence is not "not Indian"

No smartphone, a failed face scan, a lapsed session, or someone who simply walked away all produce no credential which is NOT_ESTABLISHED, not a negative. Treating a missing credential as "not Indian" wrongly rejects real Indians. Only ever act on a credential you received and verified.

Minimal-disclosure identity

Prove you're Indian.
Reveal nothing.

Scan the code with the new Aadhaar app and complete a face check. The vendor gets a signed, verifiable result, Indian or not, never your Aadhaar number, name, or photo.

✓ Nothing to install for the event✓ Your Aadhaar data never leaves your phone✓ One scan, done in seconds

How to verify

Get the new Aadhaar app

Install UIDAI's new Aadhaar app. On first launch it sets up your profile with a quick face scan.

Scan the QR

Open the app, tap Scan, and point it at the code on the right. It refreshes every few minutes, regenerate if it expires.

Approve the share

Review the details being requested and confirm with Face Authentication. Your Aadhaar number is never shown or shared.

You're verified

The card turns green. DigiGo issues a signed credential that says only that you're Indian, nothing about who you are.

Minimal disclosure by design

The attendee verifies their identity with DigiGo. The vendor receives only the result, never the person behind it.

Attendee → DigiGo

Face-auth via UIDAI's Aadhaar app. DigiGo reads only the minimum claims needed to decide Indian / not.

DigiGo → Vendor

A signed credential: indian yes/no, optional age-over-18, and a per-event nullifier.

Vendor verifies

Offline, against DigiGo's public JWKS. No secret and no callback to DigiGo, nothing to leak or phone home.

The nullifier is not an identity

It's a per-event salted hash. It lets a vendor de-dup attendees within one event, but can't be linked across events or back to an Aadhaar number.

Minimal disclosure, by construction

Privacy comes from what never leaves DigiGo, not from hiding it after the fact. The vendor gets a signed indian yes/no plus a nullifier, your Aadhaar number, name, DOB and photo stop at DigiGo.