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, OCR, face match and liveness are separate endpoints, so you call and pay only for those your journey needs.
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 and deepfake detection on the selfie step. Signzy publishes no DHS RIVTD or iBeta result, so ask for the certification and its date.
Company identity, GST verification and beneficial-ownership checks for onboarding merchants and businesses — different documents, often forgotten.
One no-code journey over individual check APIs — PAN, Aadhaar, CKYC, liveness and KYB called only where needed.
Signzy Onboarding & KYC verifies with individual APIs — PAN, Aadhaar, CKYC and the rest of the Signzy portfolio.
The identity checks Indian regulation requires, as individual API calls; CKYC avoids re-collecting documents filed elsewhere.
Reads PAN cards, Aadhaar, passports and licences captured in poor light at an angle, where completion rates are decided.
Checks liveness and compares the selfie with the photo on the document. No certification is published prominently, so ask for it and its date.
Identifies synthetic and manipulated faces at capture. Scope injection-attack handling too, since a virtual camera bypasses the lens.
Company identity, GST verification and beneficial ownership for business onboarding, with its own document set.
Sequencing, branching and exception handling without an engineering ticket for each change, as flows are edited constantly.
Here’s what genuinely sets it apart — and exactly where it stops.
Unlike bundled platforms, each verification is a separate API with its own per-call price. A lender needing PAN, Aadhaar eKYC, bank account checks and AML screening buys just those four. But a quote naming a category, such as ‘Onboarding’, tells you little; get a rate for each endpoint.
PAN, Aadhaar, CKYC, GST and UIDAI checks are native endpoints, not a bolted-on country module. CKYC is underused: a record filed once by any institution can be reused, skipping document collection. Ask how CKYC is handled and what share of your applicants it covers — it moves completion and cost.
Onboarding flows change often after launch as drop-off data, regulation and fraud patterns shift. Whether your team edits the flow or raises vendor tickets matters every fortnight. The no-code builder exists for that, so confirm who in your organisation will be trained to use it.
Two gaps. Signzy publishes no liveness certification — no DHS RIVTD result or iBeta ISO 30107-3 level — so ask for the certification, level and date; that isn’t proof the detection is weak. And ask about injection attacks separately: a virtual camera feeding synthetic video never presents anything to a lens.
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 share covered moves completion and cost more than most checks.
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 commitment in writing before signing.
Test on mid-range Android, weak connections and poor light. Put easy steps first; ordering moves completion more than accuracy.
Per-call pricing means retries cost money. Track retries by check and device tier, as poor completion adds billable calls.
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 review-site grids score satisfaction, not fit for your estate. 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.