Offline mode: actions are saved locally and will sync when online.
Pending sync:
Verify once. Reuse everywhere.
Verify once. Apply faster. Stay accountable.
DigiLocker stores your documents. VerifyOnce stores your trust. No re-uploads, no re-checks, ever. Government portals can instantly use already verified documents with simple consent.
500M+DigiLocker users in India
5-10xidentity re-verifications per citizen
Zerore-uploads, reused instantly
*Illustrative/estimated figures for demo purposes
How this fits into existing government websites
example-govportal.gov.in
🏛️ State Citizen Services Portal · Citizen Login
OR
VerifyOnce isn't a separate app — it's a feature any government portal can add to their own login page, similar to 'Sign in with Google.'
Why doesn't this already exist?
DigiLocker already offers document-sharing APIs, but adoption is optional per department. The real bottleneck isn't technology — it's adoption incentives and unresolved liability questions (who's responsible if shared data is wrong). VerifyOnce assumes this trust-sharing layer as a default, not an opt-in afterthought. Closing this gap fully requires two things: (1) formal DigiLocker/API Setu partnership for real issuer trust, and (2) fuzzy-matching fraud detection beyond exact-match checks — both are our next milestones, not final claims.
Service portal · Ration Card
Verify your identity
Verify once. No re-uploads, no re-checks, ever. Your verified identity can be reused instantly across services.
Step 1 of 3: Phone number
Checking documents securely…
Identity verified
Verification is valid for 90 days. Other services must ask for your consent before using it.
View verification proof (Technical detail)
Signed and verified using the Web Crypto API (ECDSA P-256) — real cryptography running in your browser. In production, signing would happen server-side via HSM/KMS.
Note: In this demo, VerifyOnce acts as both the issuer and verifier for simplicity. In a real deployment, the issuing authority would be a registered entity (e.g., DigiLocker/MeitY) with a publicly verifiable key, checked against a trust registry — not self-issued. In production, this would follow the W3C Verifiable Credentials standard, using Decentralized Identifiers (DIDs) and a public trust registry maintained by the issuing authority (e.g., DigiLocker/MeitY).
Issuing Authority Public Key (ECDSA P-256 · SPKI Base64):
Simulate an attacker editing the citizen ID or payload in localStorage. Because ECDSA signatures are cryptographically bound to the data, any alteration causes crypto.subtle.verify() to genuinely fail across consuming portals.
Status: Signature Valid
Service portal · Scholarship
Start scholarship application
Zero re-uploads required. Instantly reuse your verified identity from other services.