1 upload
from the honours list to every certificate
1 scan
for any registrar or employer to verify
2 languages
on one certificate, one layout
Arabic and English, first-class
True right-to-left design, bilingual layouts, and Arabic print fonts that render identically on screen and paper.
The institution's own identity
Your crest on the certificate, the email, and the verification page — white-label where policy requires it.
Verification without the registrar
Employers and other institutions confirm authenticity from the QR — no email to the records office, no waiting.
Scale for graduation day
Thousands of certificates render and send through a queue that retries failures and reports per student.
A credential, not only a PDF
Every certificate carries an Open Badges 2.0 assertion and a signed W3C Verifiable Credential, so a graduate can present it to a wallet, a portal or another institution without asking you for a copy.
Revoke, expire, correct
A withdrawn award or a misspelled name is fixed at the source: revoke the certificate, issue the corrected one, and the public page shows the current standing from that moment on.
A typical run
- 1
Design the institution's certificate
Start from a gallery template or describe the design in Arabic or English to the AI designer. Add the crest, the bilingual title, the dean's signature and the verification QR.
- 2
Upload the graduation list
Export the list from your student system as CSV or Excel. Map the columns to the certificate fields once; the same mapping serves every ceremony after.
- 3
Render, review, send
The queue renders every certificate as a vector PDF and emails it from the institution's own address. Failed deliveries retry, and the report names every student and outcome.
- 4
Answer verification requests with a URL
An employer scans the QR or opens the verification link and sees the standing, the issuer and the credential. The records office is not in the loop.
What teams ask before they start
Can the certificate be bilingual on a single page?
Yes. One element can hold Arabic and English lines, text runs right-to-left where it should, and the builder ships 31 print-safe fonts of which 15 are Arabic families. What you see on the canvas is what the PDF prints.
What happens to student data?
Recipient lists belong to your workspace and are used only to render and deliver the certificates you issue. The public verification page shows what the certificate shows, nothing more, and you can delete a list once a batch is done.
Do we still need the registrar to confirm authenticity?
Not for routine checks. Every certificate has its own verification page and QR, and the credential is cryptographically signed under your issuer identity. An offline verifier is available for checks without a connection.
Our student system is not on the integrations list. Can it still trigger issuance?
Yes, through the REST API and webhooks on a paid plan, or through Google Forms via a short Apps Script today. A CSV export from any system works on every plan, including the free one.
Bring your next ceremony
From the honors list to verified certificates in an afternoon.