The Problem
Traditional credential verification is slow, paper-heavy, and fragmented. Every new employer, regulator, or partner ends up re-checking the same facts about the same person — wasting weeks and leaking personal data along the way.
KPMG wanted to give individuals and organizations a way to hold credentials themselves, present them selectively, and let any verifier confirm authenticity cryptographically without phoning home to the issuer.
Our Approach
We built Certify on W3C Verifiable Credentials and Decentralized Identifiers (DIDs), anchored to a distributed ledger for the trust registry and revocation. Credentials are issued once by an authority, held by the user in a secure wallet, and presentable anywhere — with selective disclosure so only the required attributes are revealed.
Every piece fits the SSI principles: users own their data, verifiers trust cryptography not middlemen, and issuers can revoke credentials without taking a system offline.
What We Shipped
- ─Issuer console for credential authorities
- ─Holder wallet for individuals and organizations
- ─Verifier SDK for third-party integrations
- ─Distributed-ledger trust and revocation registry
- ─Selective disclosure via zero-knowledge proofs
Outcomes
- ─Launched as KPMG's self-sovereign identity offering
- ─Credentials portable across issuers and verifiers with no centralized intermediary
- ─Foundation for a multi-party trust network open to everyone