Project Details
Home/Project Details
TrustVerify NG
Project description
Verification as a service for the credentials people fake
The Challenge
Certificates, transcripts and reference letters are verified by phone call or not at all. In a market where a forged degree is cheap and a background check is slow, the employer either waits three weeks or takes the document at its word — and both of those are expensive in different currencies.
A verification service is only worth anything if the institution's own record is the source, which means the product cannot be a document-checking tool; it has to be infrastructure the awarding institution participates in. That is a trust-and-onboarding problem before it is a technical one.
The Solution
Give every credential a reference and let the verifier resolve it against the issuer's own record rather than against the paper. The institution gets a console it can operate from its existing registrar workflow, and the verifier gets a result they can act on, with the issuer named and the check dated.
Skills and deliverables
Features delivered
The hard part
The privacy boundary. A verifier needs to know whether a credential is genuine, not what the holder's full transcript says, so the design returns the smallest true answer — and the holder has to be able to see who checked.
The Impact
Built and typed, with the verification pipeline and the institution console working against a PostgreSQL record. The repository is public and there is no hosted instance, so the cover and the record say that plainly rather than implying a service is running.
