Question 1

Can we keep the certificate design we already use?

Accepted Answer

Yes. Upload a photo of your existing paper certificate and the AI design assistant reconstructs it as an editable template - fonts matched, colours extracted, name and date placeholders detected. You can then adjust anything on the canvas; it never becomes a flat image.

Question 2

How large a batch can we issue at once?

Accepted Answer

Batches are built for 10,000 records and more. Rows render in parallel with live progress; you can stop a run at any point and retry only the rows that failed.

Question 3

Can we issue to just a few people, without a spreadsheet?

Accepted Answer

Yes. Type a handful of people straight into the batch - or paste rows from Excel - and every entry is checked the same way a spreadsheet row is. Preview any certificate, then issue.

Question 4

Can our student, HR or learning system issue certificates automatically?

Accepted Answer

Yes. Create an API key for the designs it may issue, send each person as JSON, and receive the finished certificate at your callback URL - signed, retried until your system accepts it, with PDF and preview links that keep working even after you rotate the key. Every design shows the exact request to send.

Question 5

What happens if an entry is wrong?

Accepted Answer

Nothing generates until every entry is clean. Missing fields, malformed emails and phone numbers, bad dates and duplicates are flagged with the reason, and can be skipped or corrected and re-checked before any credential is rendered. Through the API, a request with any problem is refused whole, so nobody is half-issued.

Question 6

How does verification actually work?

Accepted Answer

Each credential carries a unique, non-guessable code and a QR that opens a public verification page with your institution's branding. The page checks the document against the registry and shows the recipient, credential, issuer, issue date and current status - including if it has been revoked.

Question 7

Can a credential be revoked or reissued?

Accepted Answer

Yes. Revoking flips the public verification page to a revoked state immediately, and reissuing supersedes the old record while keeping both in the audit history. The original code never silently starts pointing at different data.

Question 8

Do recipients need an account to receive a credential?

Accepted Answer

No. Recipients are emailed a link to their credential and its public verification page - no account, no app. You can also download a whole batch as one ZIP to share or print.

Contact us

USA

South Africa

Kenya

Frequently asked questions