Questions we hear a lot

we-verifi is the parent platform behind a family of products that all share one idea: a signed, independently verifiable record. Cert Verifi is the first of those products — it's what issues and verifies digital certificates. Project Verifi and Art Verifi are sibling products built on the same verification model, currently in development.

Every certificate issued through Cert Verifi is cryptographically signed and includes a credential that follows the Open Badges 3.0 standard — it isn't just a PDF with a logo on it. Anyone holding a certificate can share a public verification link, and anyone checking it can confirm it's genuine without needing to create an account or contact us directly.

Pay-As-You-Go is built for smaller or simpler needs: buy a credit bundle, issue certificates against it, and choose from a small set of ready-made certificate designs you can add your own logo to. Enterprise is for organisations that need more: a full template builder for fully custom designs, your own branded subdomain, API access to issue certificates from your own systems, and the ability to organise staff and certificates across multiple internal departments.

Yes. Every new Pay-As-You-Go account starts with a small number of free trial credits, so you can issue real certificates and see exactly how verification works before you buy a bundle. No payment details are needed to get started.

Yes — every certificate includes a signed Open Badges 3.0 credential alongside the certificate itself. It's built to be portable: recipients can share it as a standalone, independently verifiable credential, including adding it to a LinkedIn profile, without that platform needing any special integration with us.

Pay-As-You-Go accounts choose from a small set of preset certificate designs and add their own logo. Enterprise accounts get a full visual template builder — complete control over layout, imagery, and branding, with as many designs as you need.

Yes, on Enterprise plans. You can issue certificates directly from your own systems using a dedicated API key, so certificate issuance can be triggered automatically — for example, the moment someone completes a course or assessment in your existing platform.

Yes. You can upload a spreadsheet of results and issue certificates for an entire group in one batch, rather than sending them one at a time. This works the same way whether you're issuing to a handful of people or several hundred.

You can revoke a certificate at any time. A revoked certificate stays on record and stays fetchable for reference, but its public verification page will clearly show it's no longer valid — so anyone checking it afterwards sees the correct, current status.

Certificates, account data, and templates are stored on Google Cloud infrastructure, encrypted both in transit and at rest, with access controlled per organisation so one customer's data is never visible to another. If you need more detail for your own security or procurement review, get in touch and we can walk through the specifics.