Aadhaar (UIDAI)Aadhaar Fraud Management
Get a Demo

Aadhaar fraud management

Stop the fraud before it reaches UIDAI.

A fraud management system that checks every Aadhaar transaction twice: before your AUA sends it, and after the answer comes back.

  1. AUA Platformrequest assembled
  2. FMS · pre-checkip · device · place · time
  3. ASA → UIDAIresident verified
  4. FMS · post-checkvelocity · replay · alerts

Fraud Management System

Every transaction, checked twice.

Plugs into your AUA server with two calls. Blocks what shouldn't go out, flags what shouldn't have come back.

Get a Demo
Fraud Management · Live detections
  • FMS11Access via proxy refused — VPN exit node, request never left the AUAPRE
  • FMS19Device serial does not match the registered devicePRE
  • FMS90Daily success limit exceeded for one identity — alert emailedPOST
  • FMS18Operator outside the allowed geofence radiusPRE
  • PASS41 transactions cleared in the last minutePRE+POST
Illustrative data
PROXY · VPN · GEO-IP

From India, not through a tunnel

Every source IP is screened against proxy and VPN databases and resolved to a country. Traffic from outside India, or hiding behind one, is stopped before it leaves your AUA.

DEVICE · SERIAL MATCH

Only devices you registered

Biometric transactions are matched against your registered device list — provider, code, model and serial number. Unknown devices are quarantined and listed for review.

GEOFENCE · OFFICE HOURS

Right place, right time

Each operator works inside a radius you set, during working hours you set — evaluated on Indian time wherever your servers run. Overnight shifts handled.

DAILY · MONTHLY · YEARLY

Velocity limits per identity

Success and failure counts tracked per resident identity across three windows, computed in a single indexed query — the check stays fast at hundreds of millions of records.

REPLAY · UNKNOWN CODES

Nothing slips past the log

A repeated transaction id raises an alert instead of vanishing. A UIDAI error code nobody has mapped yet is recorded and flagged, never silently dropped.

PRIVACY BY DESIGN

No Aadhaar data at rest

Identities are stored only as SHA-256 token hashes; alert emails carry no Aadhaar number and no token. Verdicts are categorised fraud vs configuration, so an outage never masquerades as an attack.

How it works

  1. Hook in

    Your AUA server makes two calls: validate the request before the ASA, validate the response after it.

  2. Check

    IP, proxy, geography, device, operator and working hours — settled in milliseconds, before the transaction costs you anything at UIDAI.

  3. Watch

    Every answer updates the identity's velocity counters. Breaches raise notifications and email alerts on their own.

The evidence trail

  • Request logEvery attempt — cleared or blocked, with the reason
  • Response logEvery UIDAI answer, success or failure, per device and operator
  • Alert logEvery detection, with stage, code and notified recipients

Device-wise, operator-wise and modality-wise success reports, exported to Excel. Retention is policy-driven and protects the counters' full yearly window.

Fraud Management · Why it was blocked
  • INRequest received from registered device, operator in rangePRE
  • PASSIP resolved to India, no proxy detectedPRE
  • OKUIDAI verified the residentCIDR
  • FMS91Monthly success limit crossed — logged, alert sent, case openedPOST
Illustrative data

Your AUA is live. Make sure only the right transactions are.

Get a Demo