Skip to content

Glossary

What Is Branded Portal?

In Verifycate, the branded portal is the recipient-facing home for an organisation's certificates and forms, dressed in the organisation's own colours, name and domain instead of Verifycate's.

Also called: custom domain, recipient portal, white label

What it's for

Follow the links on most issued certificates and you land on someone else's brand: their logo in the corner, their signup form under the verification page, their name in the delivery email. For a training provider or an event organiser, that's a quiet leak — the moment of highest attention, handed to a vendor.

A branded portal closes the leak. Recipients see the issuer's colours, the issuer's name, on the issuer's own domain. Verifycate runs the machinery; it stops standing in the doorway.

How it works

The portal is where recipients land for everything they're sent: the certificate page, the unlock, request and correction forms, their list of certificates, and the delivery emails. Branding is set once per workspace and applied across all of it:

  • Brand colours — accent, text and background — carried through the portal pages and certificate emails.
  • Issuer name and profile — the organisation's name, logo and public details, shown on certificates and pages instead of the platform's.
  • Custom domain — the portal and verification pages served from a domain the organisation owns, set up with a DNS record.
  • Hide Verifycate branding — removes the platform's name from the surfaces recipients touch.

The distinction that matters: the workspace's internal name stays internal. What recipients see is the issuer's public name — an "Acme Corp" workspace can present to the world as "Acme Academy of Design" if that's what the certificate should say.

Branding costs nothing to set and nothing per recipient — it's part of the workspace, not a credit line. Custom domains are a Pro feature. The practical test of whether it worked: give a recipient the link with no context and ask them whose site they're on. If the answer isn't yours, the branding isn't on.

Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free

Common questions

What's the difference between the branded portal and a custom domain?
The portal is the surface — pages, forms, emails. The custom domain is one upgrade to it: serving those pages from your own address instead of a Verifycate subdomain. Branding works without a domain; the domain just removes the last visible trace of the platform.
Will recipients know a platform is involved at all?
Only where it protects them. The verification page shows the issuer's record on the issuer's brand; the cryptographic proof it carries doesn't need a logo. Hiding the branding hides marketing, not the mechanism.
Do forms and emails pick up the branding too?
Yes — unlock, request and correction forms all render in the workspace's colours, and certificate emails use the same palette with the issuer's name as sender. One setting, every surface.
Can I set up branding before issuing anything?
Yes, and it's the right order — branding is workspace settings, not a per-certificate choice. Every certificate issued afterwards inherits it automatically.

Related terms

Put your name — not ours — on every certificate.

Your colours, your domain, your forms and emails. Branding is free to set; 300 free credits to start issuing, no card.

We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF

Start for free

All glossary terms