Skip to contentVerifycate

Verification infrastructure

Put verification where the claim is made

Three ways to put Verifycate on a website: a live credential card, a workspace verification box, and oEmbed. One system for recipients, issuers, and CMSs.

Verifycate supports more than one kind of embed. A credential card shows one issued certificate on a portfolio or event page. A verification widget puts a workspace-scoped lookup box on an issuer's own website, with the same search behavior and QR scanning as the public verify page. oEmbed lets a CMS or collaboration tool render a certificate URL as a rich preview. All three read the public record and keep status current; none of them depend on a portal session or a third-party cookie.

In the glossary: Certificate Verification.

How it works

Embeds & Verification Widgets

  1. 01

    Choose the surface

    Use the credential card when the certificate itself should be visible. Use the verification widget when visitors should look one up. Use oEmbed when a URL is pasted into Notion, WordPress, or another CMS.

  2. 02

    Match the workspace

    Cards support four layouts and light, dark, or auto themes. The widget inherits workspace branding. Both follow the workspace's existing Hide Verifycate branding setting.

  3. 03

    Paste one snippet

    Every surface ships as an iframe, with a small embed.js loader for auto-height and camera access on the widget. oEmbed is discovered from the public certificate page automatically.

  4. 04

    Keep it live

    Embeds read the public certificate record, so corrections and revocations propagate within the short cache window. Only the dedicated embed routes are framable.

Event examples

Where this workflow helps

  • An issuer puts a verification box in its help centre or results page
  • An alumni page lists graduates and lets a visitor check any certificate
  • A recipient embeds their credential on a portfolio
  • A Notion or WordPress page renders a certificate URL as a card

Common questions

What is the difference between the card and the widget?
The card shows one specific certificate and works on any public credential. The widget is a workspace-scoped lookup box for an issuer's website, where a visitor enters a certificate ID or scans a QR code.
Are embeds available on every plan?
Yes. Credential cards, the verification widget, and oEmbed are available on every plan.
Do embeds use cookies or track visitors?
No. Embed routes use cookie-less public reads and do not load the site's analytics container.
Can the widget scan a printed certificate?
Yes. The verification widget includes a QR scanner with camera access, so a visitor can scan the QR code printed on a certificate.
Can I use a custom domain?
Yes. The snippets use the portal or the workspace's active custom domain, and the widget stays scoped to that workspace.
Does oEmbed need a plugin?
No. The public certificate page advertises an oEmbed endpoint, so hosts that support oEmbed can render the certificate URL directly.

Try embeds & verification widgets with your event

Start with 300 free credits. No card required.

Start for freeSee pricing