Originally published at finovo.tech/blog/whatsapp-ekyc-zero-install-onboarding — the canonical version has the latest updates.
India already lives on WhatsApp. 500 million users, 80%+ daily-active, used by everyone from a Mumbai broker to a Tier-3 NBFC borrower. So when you ask a customer to "click this link, install our app, complete KYC there" — you've already lost a third of them by step three.
WhatsApp eKYC keeps the customer on the app they already have open.
The completion-rate gap
Track any standard web KYC funnel and you'll see the same drop-off shape:
- 100 customers click the SMS link
- 76 land on the page (mobile-network drops, browser blocks, etc.)
- 58 reach the OCR step
- 43 finish PAN + Aadhaar capture
- 31 complete the video-PD or selfie step
- 27 are KYC-cleared
That's a 27% end-to-end completion rate on a flow with no friction beyond the medium itself. Switching the same flow to WhatsApp typically lands at 70-85% completion — not because the regulatory steps got easier, but because the customer never left the app, never dealt with a "this site can't be reached" error, and never had to type their Aadhaar into a tiny mobile keyboard.
What "WhatsApp-native" actually means
"WhatsApp eKYC" gets used loosely. Some flows just send a WhatsApp link that opens a hosted KYC page — that's still a web flow with extra steps. A fully native flow looks like this:
- PAN capture via WhatsApp document upload — the user takes a photo of their PAN card or sends an existing PAN PDF.
- Aadhaar verification via OTP — the user types their Aadhaar number into a WhatsApp message; we POST to UIDAI eKYC API; the OTP comes back to the user's registered mobile and is entered as a WhatsApp reply.
- Video PD via WhatsApp video call — initiated from a Business API agent, recorded, time-stamped, geo-fenced.
- Form fields (signature, nominee, FATCA, occupation) via WhatsApp interactive list and quick-reply buttons.
- Final consent via WhatsApp's official confirmation message + audit trail.
The customer types nothing into a browser. The KYC packet — including all required SEBI / RBI fields — is built server-side from the WhatsApp conversation log.
Compliance posture
WhatsApp's Business API isn't a regulator-blessed channel by itself; it's a transport. The regulator cares about:
- Identity proof capture under their respective KYC Master Direction (UIDAI eKYC, OVD, video-PD where required) — same standards as web.
- Audit trail with timestamps, IP, geo, device-fingerprint — captured per-message via the Business API webhook.
- Consent: each step has an explicit yes/no quick-reply that's logged.
- Re-KYC (the periodic 6-month / 2-year refresh that SEBI Master Circular requires) — same evidence requirements as initial KYC.
Done right, the WhatsApp flow is easier to audit than web because the entire conversation is a single log. No browser-session ambiguity.
Where most teams get stuck
The hard parts of WhatsApp eKYC aren't the regulatory steps — those are the same as any compliant KYC. They're:
- Building the conversation orchestrator that handles every user-error case: "what if they send a blurry PAN photo? what if the Aadhaar OTP times out? what if they reply with a sticker?"
- The Business API templates for every transactional message, pre-approved by Meta — easy to overlook how strict Meta is about marketing-vs-utility template categories.
- The fallback path for the 3-5% of customers who can't complete on WhatsApp — usually old phones, blocked accounts, or regulator-mandated face-to-face cases. You still need the web flow for them.
We've shipped this for 50+ Indian brokers. Customer-side completion is consistently in the 80%+ range; ops teams typically see a 60-70% reduction in support tickets vs. their previous web flow.
Try it
If you want to see the WhatsApp KYC flow end-to-end, we have a privacy-mode demo on the homepage that walks through 21 steps with auto-redacted PII so it's safe to share. Or jump straight to WhatsApp eKYC and book a 30-min walkthrough.
Built specifically for Indian financial regulation. Works for brokers (SEBI), NBFCs (RBI), and insurers (IRDAI) with the right configuration per vertical.
Top comments (0)