Questions about Verifycate?

Verifycate is a digital certificate platform for fests, courses, workshops, and training programmes. You design a template, import your recipients, and send certificates in one batch. Every certificate gets a QR code and a public page anyone can verify, with an Open Badge 3.0 credential behind it.

Anyone issuing certificates in bulk — college fests, hackathons, online courses, bootcamps, workshops, and employee training. If your recipients currently get a PDF in a group chat, Verifycate gives them a verifiable page instead.

No. Each certificate has a QR code and a public page anyone can open. It also has Open Badge 3.0 and an Add to LinkedIn button. A downloaded PDF still points back to that page.

Yes, if you set a date when you issue. After that day, the public page shows the certificate as expired. Leave the date empty and it does not expire.

Issued pages keep the original design, issuer name, and verification. We don't take those links down when a fest ends, or if you stop paying.

You start with 300 free credits on signup — no card required. Pro starts at ₹499 a month and includes credits (100 monthly, 300 on the three-month plan, 1,200 on the yearly plan). Extra credit packs are ₹1 per certificate.

One credit issues one certificate — the first send, or a reissue. Importing a list does not spend credits. Corrections do not spend credits. Unused credits stay with you.

A plan for the workspace, not per person. It unlocks Certificate Requests, Unlock Forms, Correction Forms, API, MCP, sponsors, custom domain, and removing the Verifycate logo. Monthly Pro includes 100 credits, three months includes 300, and a year includes 1,200. You can still send on Basics without Pro.

Buy a pack of 100 extra certificates for ₹100 — ₹1 each — and keep sending. Packs work on Basics and Pro, and credits don't expire.

No. Signup credits and purchased credit packs stay with your workspace until you use them.

Checkout is billed in INR through Razorpay. Dollar figures on the pricing page are shown for comparison — your card is charged in rupees.

Import your recipient list from a spreadsheet and map the columns once — name, email, and any custom fields your template uses. Add everyone in one batch and send. A wrong name is fixed by the recipient through a correction form you approve, and corrections never spend a credit.

Yes. Connect your Canva account and import a design as the template background. Add attribute placeholders like {{name}} and the verification QR in Verifycate's editor, since Canva can't fill in recipients on its own.

Yes. Share a Certificate Request link and recipients submit their own details. You can issue every valid request automatically or review each one before issuing.

Recipients who apply through a Certificate Request link land in your Issue Requests inbox. You accept or reject each request — with an optional reason. Accepting one issues the certificate and spends one credit.

There are two ways to fix it. The recipient opens the correction form on their certificate page, submits the right details, and you approve it — the certificate updates in place, and approved corrections never spend a credit. Or you can edit the recipient's details yourself from your workspace dashboard and the certificate updates the same way. Either way, the public page and QR stay the same link.

Fix the template, publish it, and reissue the affected certificates onto the new design. A reissue spends one credit, and the public page and links stay the same — only the artwork updates.

Yes. Verifycate tracks email opens, public-page views, downloads, shares, and verifications — per certificate and per batch — and shows them as a funnel so you can see where recipients drop off. You can filter recipients by their furthest engagement (never opened, opened, viewed, downloaded, shared) and check email delivery health.

Yes, with an Unlock Form. Enable it before adding recipients and each person you add automatically receives a unique, private link. Ask for a rating, testimonial, project link, file, or anything else you need. Their certificate is released when they submit, or after you review their response. Ordinary feedback forms get ignored; recipients complete this one because the certificate is waiting on the other side.

That's your choice. You can release the certificate the moment a recipient submits, or hold it until you've reviewed their response — useful when you're collecting testimonials you plan to publish.

Certificate Requests let new people apply through a public link. Unlock Forms collect a response from recipients you add yourself. Approving a Certificate Request issues the certificate directly — the recipient is not asked to complete an Unlock Form afterwards.

Yes — a REST API on Pro for creating templates, importing recipients, and issuing certificates. Documentation is at developers.verifycate.com.

Yes. Webhooks are included on Pro, so your systems can react when certificates are issued, claimed, or verified.

Yes. Verifycate ships an MCP server, so AI agents like Claude and Cursor can design templates, import recipients, and issue certificates on your behalf. See developers.verifycate.com/docs/api/mcp.

Yes — upload a CSV or Excel file and map the columns once. Imports don't spend credits; issuing does.

Every certificate has a QR code that opens a public page showing the issuer, the issue date, and the signature. Anyone with the link — or a phone camera — can confirm it's genuine. No account needed.

Yes — a PNG for sharing and a print-ready PDF. The QR code on the downloaded file still points back to the public verification page, so even the file itself stays verifiable.

Recipients click Add to LinkedIn from their email or the certificate's public page, and LinkedIn opens pre-filled under Licenses & certifications — issuer name, certificate title, and a link back to the public verification page. No screenshots, no manual uploads.

Yes. Every certificate is issued as an Open Badge 3.0 credential regardless of its shape or size, and every public page has an Add to LinkedIn button.

Each recipient gets their own private page for the certificate — they can view, share, and download it anytime, and request a correction if their name is wrong.

Our infrastructure and third-party services are listed on our Subprocessors page, with what each one does and why.

You can delete certificates and recipients from your workspace at any time. To delete your account and everything in it, write to [email protected] and we'll take care of it.

Email [email protected] and the product team will answer. Developer documentation lives at developers.verifycate.com.