University solution - MVP

Issue credentials once.
Verify in seconds.

Modernize issuance without changing academic workflows. Provide instant verification for employers, embassies, banks, and partner institutions, backed by cryptographic proofs and lifecycle controls.

Instant verificationTamper-evidentPrivacy-preservingLifecycle controlsTDOC scan
University verification at a glance
1
Issue
Generate proofs at credential issuance
2
Share
Graduate shares PDF or physical document
3
Verify
Instant check via PDF upload or TDOC scan
The problem

Manual verification is a hidden cost center.

Every year, universities receive hundreds or thousands of verification requests from employers, embassies, banks, and partner institutions. Each request triggers a manual process, phone calls, emails, letters, internal lookups, that consumes staff time and creates delays for everyone involved.

Days
Average verification turnaround

Employers, embassies, and banks wait days or weeks for manual confirmation from registrars.

100s
Staff hours per year

Dedicated staff handle phone calls, emails, and letters, a hidden cost center that scales with graduates.

Growing
Fraud sophistication

Counterfeit diplomas are increasingly difficult to detect. Universities bear reputational risk when fakes circulate.

Fragmented
Cross-border recognition

No consistent way for international institutions to verify credentials across borders.

Stakeholders

Who it serves.

Every institutional stakeholder in the credential verification chain, from issuance to final employment or accreditation decision.

University Registrars

Problem: Drowning in manual verification requests

Issue credentials once with cryptographic proof. Verifiers check independently, no registrar involvement needed.

Employers

Problem: Waiting days or weeks for diploma confirmation

Instant verification via PDF upload or TDOC scan. Clear pass/fail verdict with issuer, field, and status details.

Embassies & Consulates

Problem: Relying on institutional trust for foreign credentials

Verify authenticity independently without contacting the issuing university. Evidence is defensible across jurisdictions.

Partner Institutions

Problem: No standard way to validate transfer credentials

Machine-readable verification for academic partnerships. Trust credentials from partner universities programmatically.

Banks & Financial Institutions

Problem: KYC requires education verification for certain products

Integrate credential checks into onboarding workflows via API. Automated verification without manual document review.

Graduates

Problem: Stuck waiting for verification responses

Share verifiable credentials directly. Employers and institutions verify without calling the university.

How it works

Three steps. Cryptographic certainty.

No changes to academic workflows. ANANKE integrates with existing issuance processes and adds a trust layer that makes every credential independently verifiable.

1
Issue
University issues credentials

The university issues diplomas, transcripts, or certificates through the ANANKE web application. Each credential is cryptographically protected, timestamped, and anchored. Optionally, a TDOC DataMatrix code is stamped onto the physical or PDF document.

Upload or generate credential PDF
Assign template (proof policy + metadata fields)
Cryptographic protection applied automatically (hash, timestamp, origin)
Optionally stamp TDOC code onto the document
Credential enters the ANANKE verification system
2
Share
Graduate or institution shares the credential

The graduate shares the PDF (by email, portal, or in person) or the physical document with the TDOC code. No special software needed to share, credentials are standard PDFs or printed documents.

Graduate downloads verified PDF
Shares via email, upload portal, or in person
Physical document carries TDOC code for instant scan
3
Verify
Verifier checks authenticity in seconds

Any verifier with an ANANKE LABS account (employer, embassy, bank, partner institution) checks the credential using one of two methods: PDF upload or TDOC scan. They receive an immediate verdict, authentic or not, along with approved metadata fields.

Upload PDF to the ANANKE web application
Or scan TDOC DataMatrix with the ANANKE Mobile app
System compares cryptographic fingerprint, checks lifecycle status
Clear verdict: Authentic / Tampered / Revoked / Unknown
Approved metadata fields displayed — university controls what verifiers see
Verification

Two ways to verify.

Digital or physical. Both produce the same cryptographic verdict. Verifiers choose the method that fits their workflow.

PDF Upload

Upload the credential PDF to the ANANKE verification gateway. The system rehashes the document and compares it against the stored cryptographic proof. If the file has been altered, even a single byte, the verification fails.

How it works
1Verifier uploads the PDF file
2System computes the cryptographic fingerprint of the uploaded file
3Fingerprint is compared against the stored record
4Lifecycle status is checked (active, suspended, revoked, replaced)
5Clear verdict displayed with approved metadata
Best for

Digital workflows, email-based sharing, bulk verification

TDOC Scan

Scan the DataMatrix code on the physical or printed document using the ANANKE Mobile app. The TDOC code carries or points to a cryptographic payload that resolves to the full verification record. Works for in-person verification at reception desks, interviews, and embassy counters.

How it works
1Verifier opens the ANANKE Mobile app
2Points camera at the TDOC DataMatrix code
3App decodes the stamp and connects to verify
4Verification result displayed immediately
5Shows issuer identity, document status, approved fields, and digital twin access
Best for

In-person verification, physical documents, reception desks, field verification

What verifiers see

Clear verdicts, not cryptographic noise.

Verifiers do not need to understand cryptography. They see human-readable results that answer the questions they care about.

Status
Valid / Revoked / Replaced / Unknown
Integrity
Authentic / Tampered / Unverifiable
Issuer
University of [Name], verified origin
Approved fields
Degree title, graduation date, major (per issuer policy)
Timestamp
Issued on [date], anchored proof
Authentic

Document is genuine, unaltered, and currently valid. Issued by University of [Name] on [date]. Hash matches stored proof.

Integrity: Unchanged ✓
Origin: Verified ✓
Status: Valid ✓
Timestamp: Anchored ✓
Tampered or Unknown

Document hash does not match any known credential. Either the document has been altered, or it was never issued through this system.

Integrity: Mismatch ✗
Origin: Cannot verify ✗
Recommendation: Contact issuer directly
Guarantees

Trust guarantees for every credential.

Every credential issued through ANANKE carries these guarantees. They are verifiable independently, without trusting the issuer, relying on internal databases, or contacting the university.

Existence

This credential existed at or before a given moment. The timestamp is anchored to the blockchain and cannot be backdated.

Integrity

This exact content has not been altered since issuance. Even a single character change is detected automatically.

Origin

This credential was issued by the claimed university. Origin is cryptographically bound to the issuing organization.

Audit trail

Who did what, when, and why. Every action in the credential lifecycle is recorded with defensible accountability.

Lifecycle Status

Is this credential currently valid, revoked, or replaced? Status is checked at verification time.

Tamper-evident Audit Trail

Every issuance, verification, revocation, and replacement is logged in a tamper-evident trail.

TCODE & TDOC

The bridge between physical and digital.

T-CODE embeds a TDOC DataMatrix — a compact, machine-readable stamp — directly onto physical or PDF documents, binding the physical credential to its verified digital record.

When a verifier scans the TDOC DataMatrix with the ANANKE Mobile app, they get the full verification result — authentic or not — plus access to the digital twin for side-by-side comparison.

Not a QR code

T-CODE uses DataMatrix, a higher-density 2D barcode format with better error correction than QR. The TDOC DataMatrix encodes a compact payload — not just a URL — enabling richer verification.

Digital twin access

After scanning, verifiers can view the protected digital version of the credential — a sealed copy of the original PDF. Compare the physical document to the digital twin side by side.

Privacy & data handling

Student data stays private. Always.

ANANKE is privacy-preserving by architecture, not just policy. The system is designed so that sensitive data cannot leak, even to ANANKE itself.

No personal data on public networks

Only minimal verification references are shared externally. Student names, grades, and PII stay private within institution-controlled infrastructure.

Policy-controlled disclosure

The university decides which metadata fields verifiers see. A verifier might see the degree title and status, but not the student's grades or personal details.

Minimal verification

Verifiers get the answer they need, authentic or not, without accessing the full student profile or academic record.

Organization isolation

Each university operates in a separate trust domain. One institution cannot access another's credentials, proofs, or verification logs.

GDPR-aligned data handling

Designed for compliance with data protection regulations. Data minimization, purpose limitation, and access controls built in.

Pilot

Pilot approach

We start small and prove value fast. Each pilot scenario tests a different verification pathway.

Scenario 1: PDF Verification

University issues a batch of credential PDFs. Verification is tested via the PDF upload gateway. Focus: hash-based integrity, lifecycle status, and verifier experience.

Verification turnaround time reduction

Scenario 2: TDOC Physical

University issues physical diplomas with TDOC DataMatrix codes stamped on the document. Verification tested via ANANKE Mobile scan. Focus: physical-digital binding, scan reliability.

Scan-to-verdict time under 3 seconds

Scenario 3: Employer Integration

Select employers verify candidate credentials using the ANANKE gateway. Focus: verifier onboarding friction, verdict clarity, and workflow integration.

Employer verification completion rate

Important: What ANANKE is and is not

ANANKE provides verifiable evidence and tamper-detection, not legally qualified electronic signatures. The university product uses ANANKE Trust and TCODE. ANANKE Sign (remote qualified electronic signatures, DGSSI/eIDAS-aligned) is a separate product line and is not included in the university solution. No qualified signature or seal claims are made by ANANKE Trust or TCODE.

FAQ

Frequently asked questions.

Ready to modernize credential verification?

Interested in modernizing your credential verification? Get in touch to discuss a pilot program tailored to your institution.

Instant verification for employers and institutions
Eliminate manual verification overhead
Tamper-evident credentials with lifecycle controls
Privacy-preserving, no student data shared on public networks
PDF upload and TDOC scan verification
Proofs outlive systems, defensible long-term