Steps 1–6
For universities & accredited issuers
Registrars, professional bodies and training providers issue single credentials or whole graduating classes in minutes, signed with their own published key.
Open the issuer portalW3C Verifiable Credentials · No holder data stored
Issue credentials anyone can verify in seconds
Universities, accreditation bodies and training providers use VeriCert to issue digitally signed credentials that employers and admissions offices can trust at a glance.
- W3C VC 2.0
- Open Badges 3.0
- ES256 / P-256
- did:web
- Bitstring Status List
Two sides, one standard
Built for issuers and verifiers alike
VeriCert connects registrar offices with the employers, admissions teams and authorities who need to trust their credentials.
Steps 7–8
For employers, admissions & verifiers
Recruiters, admissions offices, embassies and licensing boards check a credential in seconds — free, with no account, straight against the issuer's keys.
Go to public verificationHow it works
From issuing to verifying, step by step
Everything VeriCert does, in the order you'll use it. Personal details such as the holder's name and date of birth stay inside the signed document — never in the registry.
- 1 Onboard your institution
- 2 Set up your issuer profile
- 3 Issue a single credential
- 4 Issue a whole class in bulk
- 5 Manage & revoke
- 6 Keep a full audit trail
- 7 Verify anywhere, in seconds
- 8 Integrate with the API
- 1
Step 1 · Issuer
Onboard your institution
The platform administrator registers and approves your institution, then invites your first issuer. Every staff account is protected by two-factor sign-in.
How to do it
- 1The VeriCert administrator creates your institution and generates its signing key.
- 2Your registrar opens the invitation link, sets a password and accepts.
- 3Scan the QR code with an authenticator app and enter the 6-digit code.
- 4Invite colleagues from Portal → Staff.
- 2
Step 2 · Issuer
Set up your issuer profile
Add the people whose names appear on the signature lines. Your institution's public key is published in its did:web document, so anyone can check your signatures.
How to do it
- 1Open Portal → Settings.
- 2Add signatories with their name and title; retire them when they leave.
- 3Your ES256 public key is published at your did:web address automatically; its thumbprint is on the dashboard.
- 3
Step 3 · Issuer
Issue a single credential
Fill in one credential and watch the certificate take shape in the live preview. On issue it is signed with your key and its hash is registered.
How to do it
- 1Open Portal → Credentials → New.
- 2Enter the holder, achievement, type, department and dates; pick up to two signatories.
- 3Check the live preview, then select Sign & issue.
- 4Give the holder the PDF (with the signed credential embedded) and the .jwt file.
- 4
Step 4 · Issuer
Issue a whole class in bulk
Upload a spreadsheet for a graduating class. Every row is checked before anything is signed, and the whole batch is issued in one click.
How to do it
- 1Open Portal → Bulk issuance and download the CSV template.
- 2Fill one row per holder and upload it as CSV or XLSX.
- 3Fix any rows flagged by the check, then issue the batch.
- 4Download every PDF at once; the batch stays in the batch history.
- 5
Step 5 · Issuer
Manage & revoke
Find any credential in your registry and revoke it if it was issued in error. The revocation is written to your signed status list and verifiers see it on the next check.
How to do it
- 1Open Portal → Credentials and search or filter by status, type or department.
- 2Select one or more credentials and choose Revoke, with a reason.
- 3Export the registry to CSV whenever you need a report.
- 6
Step 6 · Issuer
Keep a full audit trail
Who issued, revoked or invited what — and exactly when — is recorded automatically and can be exported for your auditors.
How to do it
- 1Open Portal → Audit log.
- 2Read the events newest first and follow links to the affected credential.
- 3Export any date range to CSV for compliance reviews.
- 7
Step 7 · Verifier
Verify anywhere, in seconds
Anyone can check a credential for free: scan the QR code, type the credential ID, or upload the PDF for a full cryptographic check.
How to do it
- 1Go to Verify and choose ID, QR scan or PDF upload.
- 2VeriCert checks the issuer key, signature, registered hash, revocation and expiry.
- 3Download a PDF receipt that records when the check was made and its outcome.
- 8
Step 8 · Developer
Integrate with the API
Applicant-tracking and admissions systems can verify credentials automatically through the public API — no key required.
How to do it
- 1Look up a credential with GET /api/v1/verify/{credentialId}.
- 2Run a full check by sending the signed JWT to POST /api/v1/verify.
- 3Request a PDF receipt from POST /api/v1/verify/receipt.
Security guarantees
Trust without compromise
Built on digital signatures, published keys and a public revocation registry.
No holder data stored
The registry keeps only the credential ID, hash, status and issuer. Names and dates of birth exist only in the signed document the holder controls.
Tampering detected
Changing a single character — a name, grade or date — breaks the digital signature and the registered hash, and verification fails.
W3C VC 2.0 & Open Badges 3.0
Credentials are standard verifiable credentials with did:web issuer identifiers, so they stay portable and independently verifiable.
Accountable issuance
Only invited issuers with two-factor sign-in can issue, and every issuance, revocation and staff change is in an exportable audit log.
| Verification | Paper diplomas | Manual registrar checks | VeriCert |
|---|---|---|---|
| Time to verify | Weeks, by post | Days, by email or phone | Seconds |
| Personal data held | Uncontrolled paper copies | Central student records | None in the registry |
| Forgery | Easy to edit or reprint | Relies on staff spotting it | Edits break the signature |
| Revocation | Not possible | Only if someone asks | Signed status list, immediate |
Live
Platform activity
ES256 · P-256 · did:web · BitstringStatusList
- Credentials issued
- 8
- By 1 approved institution
- Verifications · 30 days
- 6
- ID lookups and document checks
- Came back valid
- 83.3%
- 5 valid verifications · 30 days
- Forged or altered
- 0
- Failed the signature, DID or hash check · 30 days
Ready to make your credentials verifiable?
Sign in to the issuer portal, or check a credential now — no account needed.