Menu

VC use case

Proof of certification

This use case describes a graduate proving their education certification when applying for professional employment.

  • Education
Issuer authoritative source creates the claim
Holder person or organization presents proof
Verifier service checks status and makes a decision

Overview

Graduates prove qualifications to employers or regulators by presenting a verifiable degree or certification credential from their wallet.

The verifier can check that the qualification was issued by a trusted institution and is still valid without waiting for manual confirmation from the university.

Why it matters

Manual verification is slow and vulnerable to fraud. It can delay hiring, licensing, professional registration, and immigration processes while increasing the burden on education providers.

Verifiable Credentials create a cleaner model:

  • the graduate controls presentation of their qualification evidence
  • the employer or regulator verifies the credential at application time
  • the issuer remains the source of truth for award status
  • verification can happen without exposing unrelated student records

Ecosystem roles

  • Issuer: The education institution that issued the qualification.
  • Holder: The graduate.
  • Verifier: Employers, professional bodies, or platforms assessing eligibility.
  • Trust governance: The rules that define accepted institutions, credential schemas, award status, and replacement or revocation paths.

Trust decision

The verifier decision is narrow: does this applicant hold the qualification required for this role, registration, or assessment?

That decision may depend on qualification title, institution, completion date, status, equivalence, and any professional recognition rules.

Privacy and assurance

The verifier should request only the certification claims relevant to the assessment. For example, a role may require a specific degree or accreditation without needing transcripts or unrelated academic history.

Assurance depends on checking issuer trust, credential integrity, status, and whether the presented qualification satisfies the verifier’s policy.

Implementation notes

  • Define accepted qualification schemas and issuer trust lists for each recruitment or registration pathway.
  • Avoid retaining full credential payloads unless required for audit or compliance.
  • Support replacement credentials if an award is corrected or reissued.
  • Keep exception handling for overseas qualifications, unsupported issuers, and manual equivalence review.
Objective
Enable an employer or other verifier to validate a job applicant's degree certificate.
Description
A graduate presents a qualification credential so the verifier can confirm education certification.
Actors
Job applicant or graduate; education institution; employer, professional body, or platform verifier.
Dependencies
The applicant holds a digital degree or certification credential in their wallet, and the verifier can check issuer trust and status.
Preconditions
The applicant is applying for a position or registration pathway with education requirements.
Postconditions
The verifier receives a trusted certification result and can progress, deny, or escalate the application.
The university issues a degree credential to a wallet. The wallet presents it to an employer or verifier, which checks its status with the credential registry.

Credential sequence

The university issues a degree credential to the wallet. The graduate stores and presents it to a verifier, which checks the registry and confirms verification to the graduate.

Talk to UNIFY

Explore how this use case could work in your trust ecosystem.

Share the scenario you are testing and we will help map the issuers, holders, verifiers, and policy decisions involved.
Looks good!
Please enter your name.
Looks good!
Please enter your company.
Looks good!
Please enter your e-mail address so we can contact you.
This form uses Google ReCaptcha to ensure interactions with our site are from legitimate users. Please accept the use of recommended storage before submitting the form. Find out more at the Privacy Centre.
Your message could not be sent. Try again later.