Tamil Nadu clears Matrimony.com for voluntary Aadhaar-based user verification

Matrimony.com has received Tamil Nadu approval to offer voluntary Aadhaar authentication, including Yes/No and eKYC checks, to curb impersonation and matrimony fraud. Users will retain alternatives including driving licence, passport and PAN verification.

— Source publishedMon, 28 Sept, 2026, 15:00 IST·First seen Mon, 28 Sept, 2026, 15:17 IST·Source Medianama

The development

Matrimony.com received Tamil Nadu approval on August 28, 2026 to offer voluntary Aadhaar authentication for platform user verification. The company can use Yes/No and/or eKYC authentication to curb impersonation and matrimony-related fraud, while offering driving licence, passport and PAN alternatives.

The numbers

  • August 28, 2026
  • September 16, 2026
  • May 25
  • 2014
  • 2018
  • 2025
  • 2021
  • 2016
  • 18th November, 2016
  • three
  • Section 4(4)
  • Rule 3(1)
  • Rule 3(2)
  • 2020

Why it matters to operators and investors

The authorization positions Matrimony.com as a more credible partner for identity, safety, and adjacent matchmaking-service collaborations, while potentially raising the verification benchmark for rivals.

What to watch next

  • Launch timing and the exact user experience for Aadhaar Yes/No versus eKYC checks.
  • Percentage of new and existing users electing Aadhaar verification versus PAN, passport and driving-licence options.
  • Changes in reported impersonation, scam complaints, account removals and customer-support costs.
  • Premium conversion, renewal and match-engagement metrics for verified versus unverified profiles.
  • Rival announcements involving UIDAI authentication, DigiLocker, document verification or stronger profile badges.
  • UIDAI, state or privacy-regulator guidance affecting consent, storage, display or permitted use of authentication outputs.
  • Prominently position Aadhaar verification as optional, consent-led and privacy-protected rather than mandatory.
  • Create visible verified-profile badges with clear distinctions between Yes/No authentication and full eKYC verification.
  • Use verification status in trust-and-safety ranking, messaging safeguards and fraud-review workflows without excluding users who choose alternative documents.
  • Measure verification adoption, paid conversion, match acceptance, complaint rates and fraud-loss reduction by verification method.
  • Seek comparable approvals or compliant verification pathways across other high-value Indian states and diaspora-facing user segments.

The counter-case

The approval may be operationally useful but is unlikely to create a durable competitive moat: Aadhaar verification is voluntary, rivals can offer comparable identity checks, and fraudsters can still exploit genuine identities, coerced verification, or off-platform communication. Added verification steps could also reduce signup conversion among privacy-conscious users without materially improving match quality or monetization.