Journal Certificate System: A Complete Overview
What the Journal Certificate System does, where everything happens, and a guide for each task.
On this page
The Journal Certificate System gives your journal professional, verifiable certificates for authors, reviewers and editors. Altechmind designs it, configures it and sets it up on your journal’s WordPress website, then hands it over to your team. It runs on your own domain, and your journal owns it.
This overview explains what the system does, where each part lives and which guide to read for each task.
What your certificate system does
- Creates branded PDF certificates in four types, each with a unique, unguessable ID and a QR code.
- Lets anyone verify a certificate on a public page on your website, by scanning the QR code or entering the ID.
- Gives authors their own access through a page where they sign in with their email and a one-time code to download their certificates.
- Keeps management in one place: an admin panel inside your WordPress dashboard for issuing, finding, emailing, revoking and exporting certificates.
The four certificate types
| Certificate | Issued to |
|---|---|
| Certificate of Publication | An author whose paper has been published |
| Certificate of Acceptance | An author whose manuscript has been accepted |
| Certificate of Review | A peer reviewer, for their review work |
| Editorial Board Certificate | An editor or board member, for their service |
Where things happen
| Place | Address | Who uses it |
|---|---|---|
| Admin panel | Inside your WordPress dashboard | Your editorial team |
| Verification page | yoursite.com/certificate-verify/{ID} | Anyone checking a certificate |
| Author portal | yoursite.com/my-certificates/ | Authors and other recipients |
“yoursite.com” stands for your journal’s own domain. Nothing runs on an Altechmind address.
How it protects your certificates
- Certificate IDs are random, so nobody can guess a valid one.
- Each PDF is tamper-evident: a content fingerprint (hash) shows whether the certificate has been altered.
- Destructive actions in the admin panel, such as revoking, need a second confirmation step.
- PDFs and signature images are kept in a protected folder outside the public part of your website. Signatures never go into the WordPress media library.
Verification checks a certificate against your journal’s own records. That makes the result authoritative for your journal, but it isn’t independent third-party verification.
Guides by task
Getting started
Issuing and managing certificates
- Issue a certificate
- Find and filter certificates
- Revoke a certificate
- Export and back up your certificates
Verification, author access and email
Questions
Where does the Journal Certificate System run?
On your journal’s WordPress website, on your own domain and hosting. Altechmind sets it up there and hands it over.
Do we have to set anything up ourselves?
No. Altechmind designs your certificates, configures the system and sets it up. Your team starts issuing certificates after the handover.
Who owns the system and the certificates?
Your journal does. The system, the records and the PDFs stay on your website and your hosting.
Is verification independent?
No. A certificate is checked against your journal’s own records. That proves it matches what your journal issued, but it isn’t third-party verification.
Can it work next to our OJS journal?
Yes. It runs on a WordPress site on your domain, alongside your OJS journal.
Give your certificates real proof
See how Altechmind designs and sets up a certificate system for your journal, on your own domain.
Explore the Journal Certificate System →Last updated on October 9, 2026