What is Certivus Verify? - Certivus Verify

Certivus Verify is the self-serve age + identity verification product for platforms and retailers. It's the same engine that powers our regulated-firm KYC suite, but packaged for a different audience.

If you sell vape, alcohol, gambling, adult content, or anything else where you need to prove "this person is real, and they're over 18," Certivus Verify is for you.

Who it's for

Online retailers: age-gated purchases (vape, alcohol, knives, fireworks, restricted SKUs).
Gambling operators: UKGC-compliant age + identity at sign-up.
Adult-content platforms: Online Safety Act § 81 highly-effective age assurance.
Marketplaces: seller KYC, host vetting.
SaaS with KYC obligations: anywhere "is this a real human" is the question you actually need answered.

You don't need to be a regulated firm. You don't need a compliance officer. You just need to verify customers.

Two ways to use it

Verify ships with both a dashboard and an API. Pick the one that fits your stack:

Surface	When to use it
Dashboard (`/verify-app`)	Manual checks, ops team, low volume, no engineering needed. Send a verification link by email and watch the result land.
API (`/v2/verify/*`)	Programmatic, embedded in your checkout / sign-up / KYC step. Webhooks tell you when a check is done.

Both surfaces share the same accounts, the same API keys, the same billing, and the same Pass interop. You can switch between them or use both at once.

Sandbox vs live

Every Verify account starts in sandbox mode:

✅ Free: no card on file, no charges.
✅ Full feature surface: every API endpoint, every dashboard page, every webhook event.
✅ Deterministic results: sandbox returns canned outcomes you can rely on for testing.
❌ No real verification: the results are fake. They prove your integration works, not that your customer is real.

When you're ready, upgrade to live:

✅ Real provider: checks run through Certivus verification services.
✅ Live checks: confirm your account's billing terms with sales.
✅ Same code path: your integration doesn't change. The mode is set on the API key.

See Sandbox → live (upgrading) for the upgrade flow.

The Pass moat

The thing that makes Certivus Verify different: if the person has verified through Certivus before, you can reuse that verification.

A Certivus Pass holder can consent to share their existing identity

age proof with you, without repeating a fresh check. That's good for:

You: a result from an existing verification.
Them: no document upload, no selfie, no waiting.
Trust: the data was verified once, properly, and is being reused, not re-collected.

See Pass interop (the moat) for how it works under the hood.

Pricing

Contact sales for Verify-specific billing terms, including Pass reuse and age verification. See Verify billing.

How to start

Sign up at app.certivus.com/verify-app/signup: no card required, sandbox keys issued immediately.
Issue an API key, or start sending from the dashboard if you don't want to integrate yet.
Send your first check: UI or API, both work the same.
Wire a webhook so your system knows when a check finishes.
Upgrade to live when you're ready to bill real customers.

How Verify relates to Certivus Pass and the Firm suite

Same engine, three audiences:

Firm suite (/firm/*): for regulated UK firms (law, accounting), covering MLRO workflow, AML programme, audit packs.
Certivus Pass: the reusable consumer credential, issued once, reused everywhere.
Certivus Verify: the self-serve verification API + dashboard for non-regulated platforms.

A Verify check can lookup an existing Pass. A Firm-suite KYC can issue a Pass. A Pass can be shared with another Verify customer or another Firm. One Certivus Individual ID under the hood: every product talks to the same trust layer.