Certificates and verification widgets can now be embedded

Certificates and verification widgets can now be embedded.

Until now, verification usually happened on Verifycate. An issuer's help page linked to the public certificate page, a recipient pasted a screenshot into a portfolio, and a reviewer followed a URL away from the page that made the claim. Both surfaces now bring verification to where the claim or the check already happens.

The issuer case is the larger one. A workspace can now put its own verification widget on its website: the same search behavior and branding as the public verify page, scoped to that workspace, with QR scanning for a certificate printed on paper. It drops into an alumni page, a results page, a conference programme, or a support article, and a visitor can check a credential without leaving the site. The widget follows the workspace's existing branding and Hide Verifycate branding setting.

The credential card covers the recipient and event-page case. One issued certificate can be embedded on any page with four layouts — Poster, Clean, Minimal, and Badge — including multi-page carousels and mixed page sizes without cropping. Status is read live, so a corrected or revoked credential updates in the embed instead of leaving a stale image behind.

A small script loader and oEmbed discovery cover hosts that would rather not hand-write an iframe.

Find the credential snippet under Share → Embed on a public certificate page. Issuers can configure the verification widget from Workspace → Integrations → Embeds. The developer guide covers both snippets and the oEmbed endpoint.

Embeds are available on every plan. Check the branding note above: the small Verifycate attribution is not a separate embed upgrade.