Proving a remote person is who they claim to be — document and biometric verification built on Onfido, acquired April 2024. Note the boundary that costs the most: this is verification, not authentication.
Data residency & processing — two different questions
Where data lives
Yours — on-premises appliances in India
nShield HSMs are physical appliances in your own data centre, and private PKI can run on-premises too. Keys are generated and held in hardware you own, in India, under your administrators — you prove it with hardware records (a serial number, an access log), not with contract wording.
The constraint, stated plainly
No India region for the managed service
nShield as a Service runs in the UK, US, Germany and Australia. Entrust has live engineering hiring in Bengaluru and Pune, and that is people in India, not data in India — counting engineering staff as an answer on residency is the mistake an audit exposes.
For a residency-bound Indian buyer the answer is appliances you operate, which is very likely what your regulator wanted anyway. Note what does not exist so its absence is not misread: Gartner publishes no Magic Quadrant for HSM or key management at all, only Market Guides, which have no Leader quadrant — and we could not verify an HSM Leader placement for Entrust with any analyst. A search caution specific to this vendor: “Entrust India” surfaces several unrelated companies, including a Bengaluru wealth manager, so check you are reading about Entrust Corporation before drawing conclusions.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Entrust Identity Verification — remote identity verification. The rest of the Entrust portfolio on TechBag:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Document and biometric verification built on Onfido — checking an identity document and matching a live capture against it to establish who a remote person is.
What automated document and biometric checks change, dimension by dimension.
| Dimension | Uploaded ID scans & manual review | Identity Verification |
|---|---|---|
| Is the document real? | Eyeballed by an agent | Visual, data and metadata checks |
| Is it the holder? | Two photos compared by eye | Facial similarity score |
| Photo of a photo | Often missed | Motion liveness challenge |
| Same face, new name | Invisible | Known Faces match |
| Clean applications | Queue for manual review | Automated where checks pass |
| Foreign documents | The agent guesses | 2,500+ document types supported |
| Changing the flow | An app release | Edit in Workflow Studio |
| Regulated KYC in India | Your process | Still your process — this is a component |
Verification is one control in onboarding, not the whole KYC obligation. For RBI-regulated entities the KYC Master Direction decides the route; TechBag maps which parts this product can support.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
The applicant photographs an identity document and records a selfie video through Entrust’s mobile or web SDKs, or through a journey Entrust hosts via Workflow Studio.
Visual, data and metadata checks judge whether the document is authentic and unaltered, across 2,500+ document types; NFC chip reads add proof where supported.
Facial similarity compares the live capture with the document photo; Motion asks for simple head movements to confirm a real person is present.
Optional reports — device intelligence, Known Faces matching against earlier applicants, watchlist screening — add signals a document check alone cannot see.
Results return by API or webhook with a recommendation your onboarding logic acts on, alongside the evidence a reviewer or auditor may need later.
Document, face and fraud signals combine into one decision — the regulatory obligation around it stays yours.
What Entrust Identity Verification actually does — check the document, confirm the person, catch the fraud patterns around them, and fit it into your onboarding flow.
More than 2,500 document types across 195 countries, per Entrust — confirm the Indian documents you accept are on the supported list.
Where a passport or ID card carries a chip, reading it confirms the data was issued by the authority — stronger evidence than an image.
Compares the applicant’s live capture against the document photo to confirm the person holding the ID is the person it describes.
Extracts and checks address documents where your onboarding process needs evidence of address alongside identity.
A short selfie video with head movements; Entrust states Motion is iBeta PAD Level 2 compliant against masks, printed photos and screens.
Flags a face already used in earlier applications — the pattern behind repeat-applicant and synthetic-identity fraud.
Adds device and network signals to the decision, catching suspicious sessions that a clean-looking document would otherwise hide.
Screens applicants against sanctions and watchlists within the same flow, where your policy requires it.
Build and change verification journeys without engineering, and let Entrust host the flow instead of integrating SDKs into your app.
Native SDKs and a REST API for teams that want capture inside their own app, with webhooks to deliver results.
Data at rest can be kept in the EU, US or Canada region by calling that region’s API; there is no India region.
The Onfido platform reports SOC 2 Type II compliance and ISO 27001 certification by BSI — request the current reports in due diligence.
Document verification explained, then verification in practice — from Entrust’s own channel.
Document checks, explained.
Verification in practice.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Here’s what genuinely sets Entrust Identity Verification apart.
This is the misunderstanding that wastes the most money in this category, so it is worth being blunt. Identity verification establishes who somebody is the first time you meet them — checking a document, matching a face, deciding whether to open the account. Authentication confirms that whoever is signing in now is the same person who was verified then. A product that is excellent at one is not thereby useful for the other, and organisations regularly buy one having budgeted for the problem the other solves. Entrust sells both, which makes it easier to get right and also easier to be vague about. Be explicit about which problem you have before the demo.
Identity used to be established in person, by someone looking at a document and at a face. Almost nothing works that way now, and the controls that assumed physical presence do not transfer. Document and biometric verification is the replacement, and it is doing genuinely hard work — detecting forged or altered documents, detecting presentation attacks where somebody holds a photograph or a screen to the camera, and doing both across the enormous variety of identity documents the world issues.
Entrust acquired Onfido in April 2024, and that acquisition is what this product is. Onfido was an established specialist with real depth in document coverage and liveness detection, which is a category where depth matters disproportionately — the difference between a system that works on common documents in good lighting and one that works on unusual documents in poor lighting is most of the value. Buying an established specialist rather than building is the right call in this category, and worth knowing as the provenance of what you are evaluating.
We are going to be careful here rather than reassuring, because this is where the real risk sits. Remote customer onboarding in regulated Indian financial services operates within a framework RBI prescribes, and a vendor verification product is a component inside that framework rather than something that discharges the obligation. What a product can do technically and what satisfies a regulated KYC requirement are separate questions, and vendors on all sides have an incentive to blur them. Establish precisely which parts of your obligation this can serve, in writing, before you build a customer journey on top of it. If a vendor is vague about that boundary, treat the vagueness as information.
Buy this when you onboard people remotely and need to establish who they are with more confidence than a form provides — and when you have already separated that need from your authentication need. It is strongest as part of a wider Entrust relationship, since buying identity verification from a hardware-and-PKI vendor makes most sense when you are already there. If identity verification is your only requirement and you have no other reason to be with Entrust, evaluate the specialist market too. And if you are in regulated Indian financial services, settle the regulatory boundary before the technology evaluation, because that is the answer that determines whether any of this is usable.
Onboarding (who is this?) and sign-in (is it them again?) are different purchases. Write down which one this project is buying.
For RBI-regulated onboarding, identify which KYC route you use — V-CIP needs a live official — and which checks a vendor product can support.
Data at rest sits in the EU, US or Canada region. Agree the region and your DPDP cross-border position before any applicant data flows.
Use SDKs in your app or a Workflow Studio hosted flow; test Indian documents, low-end phones and poor lighting, not the demo passport.
Review false rejects and caught attacks monthly, and adjust which reports — Motion, Known Faces, device — run for which risk tier.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“Motion caught the printed-photo attempts our old selfie check waved straight through.”
“Studio let our product team change the onboarding flow without waiting for an app release.”
“It checks documents and faces well. It is not V-CIP, and our compliance team made us prove we understood that.”
“Storage was EU, US or Canada. Legal needed a week on cross-border transfer before we could sign.”
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the identity-verification market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
Onfido technology inside a wider identity portfolio.
How well a product fits Indian regulated onboarding vs how deep its global document and liveness coverage goes.
Global depth; no India storage region, and not V-CIP.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
HyperVerge, Signzy, Jumio and Veriff — honest lanes; the edge is global document depth and liveness inside Entrust’s wider identity portfolio, not Indian regulatory fit.
| Dimension | Entrust IDV | HyperVerge | Signzy | Jumio | Veriff |
|---|---|---|---|---|---|
| What it actually is | Onfido-based document and biometric verification | India-built identity, fraud and onboarding platform | India-built API marketplace for KYC checks | US-based global identity verification | Global identity verification with self-serve plans |
| Indian regulated onboarding | A component — not a V-CIP product | RBI, SEBI and IRDAI workflows | India KYC checks, including video KYC | Confirm India-specific support | Confirm India-specific support |
| Liveness certification | Motion — iBeta PAD Level 2 | iBeta / ISO 30107-3 Level 2 | Confirm certification level | Confirm certification level | Confirm certification level |
| Document coverage | 2,500+ types, 195 countries | India-first coverage | India-first coverage | Global coverage | Global coverage |
| India data residency | EU, US or Canada regions — no India region | Not published — ask | Named region; in-country on request | Confirm with Jumio | Confirm with Veriff |
| Published pricing | Quote-only | Quote-only | Quote-only, typically per API call | Quote-only | Self-serve plans from $49/month |
| The thing to plan around | No India storage region; not V-CIP | Residency not published | Checks bought individually — model the bundle | Quote-only; confirm India fit | Confirm Indian document coverage |
| Best fit | Global onboarding, already an Entrust customer | Indian regulated onboarding at volume | Indian KYC checks bought by API | Large global onboarding programmes | Teams that want a self-serve start |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Entrust Identity Verification works alongside the 21 encryption & rights management products TechBag carries. The encryption & rights management guide narrows them to a shortlist and shows the reasoning. →
Drag the sliders (applications reviewed by hand per year; loaded reviewer-hour cost). Assumes about 15 minutes of manual document review per application, most of it removed where automated checks pass — the larger, unpriced win is the fraudulent account never opened. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Entrust Identity Verification is quote-priced (no public list) — usage-based, shaped by verification volume and which reports run (document, facial similarity, Motion, Known Faces, watchlist, proof of address). TechBag models your report mix and quotes in INR with GST.
Best for standard remote onboarding
Best where fraud pressure is high
Best for teams that change flows often
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
Are we buying onboarding verification, sign-in authentication, or both — and have we written that down?
Which parts of our RBI, SEBI or IRDAI KYC obligation can this support, confirmed in writing?
If our route is V-CIP, where do the live official, geo-tagging and session recording come from?
Which region — EU, US or Canada — will hold applicant data, and is that acceptable for us under DPDP?
Are the Indian documents we accept on Entrust’s supported list, and how do they perform in a pilot?
Which liveness mode will we run, and what certification backs it?
Do we need Known Faces, device intelligence or watchlist reports, or only document and face?
SDK inside our app, or a Workflow Studio journey hosted by Entrust?
What false-reject rate do we see on our own applicant population, measured in a pilot?
How is each verification or report priced, and what minimums or commitments apply?
Settle the KYC boundary and the storage region, pilot on your real applicants, or let a TechBag advisor model the report mix and cost with you.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.