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.

Available on Pro, they turn a certificate into a Web3-verifiable credential that stays provable without Verifycate. We anchor a fingerprint of the signed credential to Ethereum (Base) as an EAS attestation and timestamp the same root on Bitcoin with OpenTimestamps; the encrypted credential and a name-masked image are stored on Arweave. Each certificate also gets a name-masked NFT on Base that anyone can view and verify in OpenSea. The public page reports every channel with a downloadable Bitcoin proof that verifies offline. Blockchain adds an issuer-independent timestamp — authenticity still comes from the Ed25519 signature.

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.

Yes. Every workspace can customize the sender name, reply-to, CC, and BCC. On Pro, you can also send from a verified domain you control, connect your own provider (Cloudflare, Resend, Amazon SES, Postmark, SendGrid, or Mailgun), or use raw SMTP. Provider credentials are encrypted at rest, and customer-owned providers are activated with a test send.

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 Blockchain Verifiable Web3 Certificates, the Issue Request Form, Unlock Form, Correction Form, API, MCP, sponsors, custom domain, custom email senders, removing the Verifycate logo, and enterprise identity features — SSO (OIDC/SAML), SCIM provisioning, and audit logs. Monthly Pro includes 100 credits, three months includes 300, and a year includes 1,200. You can still issue certificates 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. Credits never expire and roll over — signup credits, the allowance included with Pro, and purchased credit packs all 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.

Yes, on Pro. Connect Okta, Microsoft Entra ID, Google Workspace, or another identity provider with OpenID Connect (OAuth 2.0) or SAML 2.0, enforce SSO for verified domains, provision members and roles with SCIM 2.0, and review security-relevant changes in an append-only audit log with CSV export.

On Pro, connect Okta, Microsoft Entra ID, Google Workspace, or another provider over OpenID Connect (OAuth 2.0) or SAML 2.0. Members sign in through your identity provider, and Verifycate keeps their existing workspace role. You can also verify your work-email domains and require SSO for them.

Verifycate does not run its own MFA. With SSO, MFA and sign-in policy are enforced by your identity provider. Email one-time codes and Google sign-in do not add a second factor, so enable MFA at your IdP if that is a requirement.

SCIM 2.0 lets your identity provider create, update, and deactivate workspace members automatically. You can map directory groups to admin, manager, issuer, or support roles, and deactivation revokes the member's sessions. SCIM works independently of SSO, so members can still sign in with email or Google.

The audit log is an append-only record of security-relevant actions: membership and role changes, API-key changes, certificate and recipient changes, webhooks, workspace settings, SSO and SCIM changes, and actions taken by Verifycate Admin. Workspace admins can filter the trail and export it as CSV.

Provider credentials and SMTP passwords are encrypted at rest with the application encryption key and are never returned by the API. When a workspace connects its own provider, that provider is controlled by the customer and is not a Verifycate subprocessor.

No. They are Pro features. If a Pro plan lapses, an existing SSO connection stays manageable so an admin can turn enforcement off instead of being locked out; SCIM provisioning stops until Pro is active again.

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 the Issue Request Form link. Applicants confirm their email with a one-time code, then submit their details. Choose Issue Automatically or Review Before Issuing; reviewed submissions appear in Issue Requests.

Yes, on Pro. Connect Okta, Microsoft Entra ID, Google Workspace, or another identity provider with OpenID Connect (OAuth 2.0) or SAML 2.0, enforce SSO for verified domains, provision members and roles with SCIM 2.0, and review security-relevant changes in an append-only audit log with CSV export.

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 (the glossary term is Certificate Unlock Form). When the certificate is published with the form enabled, recipients waiting for release and recipients added later receive a unique private link by email. Ask for feedback, a testimonial, project links, or files. Choose Release Automatically After Submission or Review Before Release in the form configuration; reviewed responses appear in Unlock Responses.

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.

The Issue Request Form (the glossary term is Certificate Request Form) is public. It lets applicants who are not on your recipient list ask for a certificate; applicants confirm their email with a one-time code. The Unlock Form (the glossary term is Certificate Unlock Form) goes to recipients you have already added, using a private link without sign-in or a code, and collects a response before their certificate is released.

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. On Pro, the page also reports the blockchain anchor on Ethereum and Bitcoin, so a verifier can check it independently of Verifycate.

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 Blockchain Verifiable Web3 Certificate also gets an ERC-721 record on Base with a name-masked image — a recipient's name is never written to the chain. Anyone can open it in OpenSea to see the collectible record, cross-check the matching transaction in BaseScan, or confirm the Bitcoin timestamp with the downloadable .ots proof. The certificate's public page links all three.

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. For Blockchain Verifiable Web3 Certificates, only a fingerprint of the credential and a name-masked image ever go to a public chain — the credential itself stays encrypted and off-chain.

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.