You needed four checks. You licensed forty — Signzy sells each verification as a separate API — so you buy the four checks your journey needs rather than a licence covering forty capabilities you will never call.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Onboarding & KYC — the core verification APIs. The rest of the marketplace:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Verification checks bought as individual APIs — PAN, Aadhaar, CKYC, OCR, face match, liveness and KYB, assembled into a journey with a no-code builder.
What consolidation actually replaces, dimension by dimension.
| Dimension | A licence covering everything | Onboarding & KYC (Signzy) |
|---|---|---|
| What you buy | A platform licence | Individual APIs, per call |
| What you pay for | Forty capabilities | The four checks you call |
| India identity | A country module | PAN, Aadhaar, CKYC as endpoints |
| Repeat documents | Collected every time | CKYC reuse where a record exists |
| Journey changes | A vendor ticket | No-code, by your own team |
| What it is NOT | — | Not a published liveness benchmark — ask |
Get the API list INTO the contract with a rate for each: a category name tells you nothing about what you licensed. And ask for the liveness certification level and date — Signzy does not publish one.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
PAN, Aadhaar, CKYC, GST, bank account, document OCR, face match and liveness are individual endpoints. You call and pay for the ones your journey needs, which is the difference between this and a platform licence.
A visual layer for sequencing checks, branching on results and handling exceptions without engineering time for every change. Onboarding flows get edited constantly, so who can edit them matters.
Presentation-attack detection and deepfake identification on the selfie step. Signzy does not publish a DHS RIVTD or iBeta result, so ask for the specific certification and its date rather than assuming one.
Company identity, GST verification and beneficial-ownership checks for onboarding merchants and businesses. Different documents, different failure modes, and often forgotten until a merchant programme starts.
One telemetry fabric across endpoint, cloud, and network — threats correlated once, not chased console to console.
Signzy Onboarding & KYC verifies with individual APIs — PAN, Aadhaar, CKYC and the portfolio, and paired with the human firewall.
The identity checks Indian regulation asks for, as individual API calls. CKYC in particular avoids re-collecting documents a customer has already filed elsewhere.
Reading PAN cards, Aadhaar, passports and licences captured in poor light at an angle. The awkward captures are where vendors separate and where your completion rate is decided.
Matching the selfie to the document photo and checking the face is live rather than a photo or replay. Ask for the specific certification and its date — none is published prominently.
Identifying synthetic and manipulated faces at capture. Worth scoping alongside injection-attack handling, since a virtual camera never presents anything to a lens at all.
Company identity, GST verification and beneficial ownership for merchant and business onboarding. A separate problem from individual KYC, with its own document set.
Sequencing, branching and exception handling without an engineering ticket per change. Onboarding flows are edited constantly as drop-off data arrives, so this is an operational saving.
Here’s what genuinely sets it apart — and exactly where it stops.
This is the structural difference from most identity vendors and it changes how you evaluate. With a bundled platform you licence a capability set and configure what you use; here each verification is a separate API with its own per-call price. A lender needing PAN verification, Aadhaar eKYC, bank account verification and an AML screen buys exactly those four, and never pays for the thirty-six capabilities they will not call. The saving is real for a focused use case. The corresponding risk is that a quote written at category level — naming 'Onboarding' rather than the APIs inside it — tells you almost nothing about what you bought or what it costs at volume. Enumerate the endpoints and get a rate for each.
PAN, Aadhaar, CKYC, GST and UIDAI checks are native endpoints rather than a country module layered onto a global template. CKYC deserves particular attention because it is underused: India's Central KYC registry means a record filed once by any financial institution can be reused, which removes an entire round of document collection for a customer who has onboarded anywhere before. Most journeys still ask for documents the registry already holds. When scoping, ask specifically how CKYC is handled and what proportion of your expected applicants would be covered by it, because that number changes both the completion rate and the per-application cost more than most individual check choices do.
Onboarding flows are not built once. Drop-off data arrives, a regulation moves, a fraud pattern emerges, and the sequence needs changing — often several times in the first quarter after launch. Whether your team can make those changes directly or must raise a request with the vendor is an operational difference that never appears in a licence comparison and shows up every fortnight in practice. The no-code builder exists for exactly this. Confirm during evaluation who in your organisation would actually hold that capability, because a builder nobody is trained on defaults back to vendor tickets and the advantage evaporates quietly.
Two gaps worth naming. First, Signzy does not prominently publish a liveness or presentation-attack certification the way some competitors do — no DHS RIVTD result, no iBeta ISO 30107-3 level stated on the marketing pages. That does not mean the detection is weak; it means the evidence is not public, so ask for the specific certification, its level and its date rather than assuming. Second, ask about injection attacks separately from liveness: a virtual camera feeding synthetic video into the app never presents anything to a lens, so presentation-attack testing does not cover it. Both are reasonable questions for any vendor in this category, and a vendor that answers them precisely is telling you something useful.
Not the categories. This is a marketplace, so the endpoint list is what you are buying and what you will be billed for.
A filed record removes a whole document step for that applicant. The proportion covered changes both completion and cost more than most check choices.
Certification level and date, plus how injection attacks are handled separately from presentation attacks. None of it is published, so ask.
India is a named region and in-country storage is available on request. Get the specific commitment for your deployment written down before signature.
Mid-range Android, weak connection, poor light. Sequence easy steps first and escalate conditionally — ordering moves completion more than accuracy does.
Per-call pricing means retries cost money. Track the retry rate by check and device tier; a journey with poor completion generates more billable calls than forecast.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“Buying four APIs instead of a platform licence halved what we expected to spend. The flexibility is genuine if you know exactly which checks you need.”
“CKYC coverage was the surprise. A meaningful share of our applicants already had a filed record, which removed a whole document step for them.”
“Get the API list into the contract. Ours said 'onboarding' and the first invoice was a conversation we should have had before signing.”
“Ask for the liveness certification specifically. It was not on the marketing pages and we had to request the detail during security review.”
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.
Per-API buying; India residency named.
The grid nobody publishes — depth within the category vs fit with Indian identity infrastructure.
Deep India endpoints, bought per call.
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.
Against HyperVerge, a global IDV vendor and an in-house build — on the buying model, India coverage and published evidence.
| Dimension | Signzy Onboarding | HyperVerge | A global IDV vendor | In-house build |
|---|---|---|---|---|
| Commercial model | Per API, per call | Bundled suites | Usually bundled | Build cost |
| India identity coverage | Native endpoints | Native | Configured | Yours |
| Published liveness evidence | Not published | DHS Track 2 + iBeta | Varies | None |
| India data residency | Named region | Not stated | Varies | Your servers |
| Journey changes | No-code builder | Platform builder | Varies | A sprint |
| Published pricing | Quote-only | Quote-only | Varies | Build cost |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Drag the sliders (monthly onboarding volume; cost of a lost application). Estimates model applications abandoned mid-journey plus the billable retries a poor completion rate generates. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Quote-only — Signzy publishes no price and bills per API call. TechBag scopes the endpoint list against your real volumes, including retries, then quotes in INR with GST.
Best when you know your check list
Best for a broader rollout
Best across the journey
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.
Does your contract enumerate the specific endpoints and a rate for each, or just name a category?
What share of your applicants would have a filed CKYC record? It removes a document step for each of them.
What certification does the liveness check hold, at what level, and dated when? None is published — request it.
How are injection attacks handled, separately from presentation attacks? A virtual camera presents nothing to a lens.
Is the India in-country storage commitment documented for your deployment, or only the general statement?
Who on your team will hold the no-code builder? A tool nobody is trained on defaults back to vendor tickets.
Are failed verifications that customers reattempt billable? Poor completion generates more of them than forecasts assume.
Can you approve without a list price? There is none — model your real call volumes including retries.
Write down the specific checks you need first — this is a marketplace and the endpoint list is what you buy — or let a TechBag advisor scope it and get the residency commitment in writing.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.