Skip to content
Certopact

Who it's for

Just the verification — in your own system.

If you already run a visitor management system, an HRMS, an onboarding flow or a custom app and only need the identity check — not another product — Certopact Verify gives you the building blocks directly. Call the verification you need, get a source-verified result back, and keep your own UX.

1

Your system

Your VMS, HRMS or app collects the visitor's details.

Certopact Verify API 2

2.1

Aadhaar (OVSE)

2.2

Face Liveness

2.3

Verified

3

Back to your system

The verified result returns to your VMS — no Aadhaar number stored.

4

Entry allowed

Your flow continues — grant entry, onboard or proceed.

Your flow, your UX — Certopact handles the verification step.

The APIs

Verification APIs, ready to embed.

Identity verification

Available

Aadhaar (OVSE)

OVSE API — offline Aadhaar verification, no OTP, no live UIDAI call.

The OVSE API validates a UIDAI-signed secure QR or Aadhaar Paperless Offline e-KYC. Consent-based; the full Aadhaar number is never stored.

Available

Face Liveness

Face Liveness API — confirm a real, present person, not a photo or replay.

The Face Liveness API is an anti-spoofing check that can be matched to the photo in a verified record, so a credential can't simply be borrowed.

How it works

Call an endpoint, get a verified result.

Send the artefact or details to the endpoint, Certopact verifies against the authoritative source, and you get a clean result back — with no sensitive number stored. Certopact provides the technology to run offline Aadhaar verification (OVSE) via API, so you don't build your own UIDAI integration. The shape below is illustrative; the API reference will define the final contract. 

POST /v1/verify/ovse       # validate an offline Aadhaar artefact (QR / Paperless e-KYC)
POST /v1/verify/liveness   # run a face-liveness check

# → { "verified": true, "name": "…", "match_score": 0.96 }
#   Aadhaar number is never returned or stored

Security & DPDP

Consent-first, purpose-limited.

Every verification is consent-based and purpose-limited, encrypted in transit and at rest, with India data residency available. For Aadhaar OVSE the full number is never stored — see Aadhaar masking and the DPDP Act and visitor data.

Aadhaar and DPDP obligations — including who acts as the verifying entity — depend on your deployment. This is general information, not legal advice; confirm your obligations with your own counsel.

Prefer the full product?

Verification, already built in.

If you'd rather not build the UX yourself, Certopact Entry delivers the same verification with screens and workflows, and Certopact Access runs the whole visit. See Aadhaar visitor verification and KYC visitor management.

FAQ

Certopact Verify — questions, answered.

What is Certopact Verify?
Certopact Verify is the verification engine behind Certopact Entry, offered as an API. If you already run your own visitor system, HRMS or app and just need the identity checks — Aadhaar (OVSE), Face Liveness and more — you can call them directly instead of adopting the full product.
What is the OVSE API?
The OVSE API validates a UIDAI-signed offline Aadhaar artefact — a secure QR or Aadhaar Paperless Offline e-KYC — with no OTP and no live UIDAI call, returning a verified result without storing the Aadhaar number.
What is an OVSE Technology Service Partner (TSP)?
A Technology Service Partner provides the technology that lets an organisation run offline Aadhaar verification (OVSE). Certopact provides that technology via API, so you can verify UIDAI-signed artefacts without building your own integration. Your obligations as a verifying entity depend on your deployment; this is general information, not legal advice — confirm them with your own counsel.
Which APIs are available today?
Aadhaar (OVSE) offline verification and Face Liveness are available now, and more verifications are on the way.
How is it different from Certopact Entry?
Entry is the full identity-verification product with its own UI and workflows. Certopact Verify is the same engine unbundled as an API, for teams that want to embed verification into a system they already run.
Is Aadhaar data stored?
No. Aadhaar OVSE verification is consent-based and the full Aadhaar number is never stored — only the result and the attributes you need. This is general information, not legal advice; Aadhaar and DPDP obligations depend on your deployment, so confirm them with your own counsel.

Ready to embed verification?

Tell us which verifications you need, and we'll get you set up with API access.

Book a demo