MoRTH databases, Vahan RC checks, challan APIs, insurance verification — everything logistics platforms, fleet operators, and cab aggregators need to know about driver verification in India.
Priya Nair
Head of Product, Truvixx
India's logistics sector — worth over $215 billion and growing at 10% annually — is built on the back of millions of drivers: truck operators, delivery partners, cab drivers, and last-mile agents. Yet the industry's approach to verifying who is actually behind the wheel remains surprisingly fragmented. Manual DL checks, WhatsApp photo submissions, and agent-led RC verifications are still standard practice at many mid-sized operators.
This guide covers the complete driver and vehicle verification stack available in India in 2026 — the databases, what they can and can't tell you, the APIs, and how to build a verification workflow that scales.
The Ministry of Road Transport and Highways (MoRTH) maintains the Sarathi database, which is the authoritative source for driving licence data in India. A real-time query against Sarathi returns the DL number validity, expiry date, vehicle classes the driver is licenced to operate (LMV, HMV, MCWG, etc.), and the name and date of birth of the licence holder.
What Sarathi can tell you
DL validity and expiry date, licenced vehicle classes, holder identity (name, DOB, address), issuing RTO, and whether the licence has been suspended or revoked. What it cannot tell you: whether the driver has pending challans, whether their vehicle is insured, or whether they have a criminal record.
Vahan is the national vehicle registration database maintained by MoRTH. A Vahan lookup against a vehicle registration number returns the RC status (active, expired, cancelled), vehicle class, fuel type, engine and chassis numbers, registered owner name, RC expiry date, and fitness certificate status.
For logistics platforms, the fitness certificate (FC) is particularly important: a vehicle without a valid FC cannot legally operate on public roads. For passenger transport, the permit status is equally critical — an unlicenced cab or auto cannot legally carry passengers for hire.
Third-party insurance for commercial vehicles is mandatory under the Motor Vehicles Act 1988, yet insurance lapse is among the most common findings in driver verification. The Insurance Information Bureau of India (IIB) maintains a database of active policies that can be queried by vehicle registration number. A lapsed insurance policy on a commercial vehicle creates direct liability for the platform or operator if the vehicle is involved in an incident.
The e-Challan system, integrated across most states via the mParivahan platform, allows pending traffic violations to be queried by vehicle registration number or DL number. A driver with significant pending challans represents a regulatory risk — courts can seize vehicles with outstanding fines, and in some states, platforms are being held co-liable for violations committed by drivers during active deliveries.
Real case
A major logistics platform faced a police seizure of 11 vehicles in Bengaluru because the drivers had a combined ₹8.4 lakhs in unpaid challans. The platform had verified DLs at onboarding but had no challan screening process. The verification gap cost 3 days of operational disruption.
The Pollution Under Control (PUC) certificate is mandatory for all vehicles in India and must be renewed periodically. For fleet operators in cities with strict pollution controls (Delhi, Mumbai, Bengaluru), deploying vehicles without valid PUC certificates can result in challan, impoundment, and — for repeated violations — permit cancellation.
The Motor Vehicles (Amendment) Act 2019 mandates that aggregators conduct background checks on drivers. For passenger transport platforms, this is now a licence condition. The check should cover court databases and police records — FIR history, arrest records, and active cases. A clean DL record says nothing about whether a driver has a history of theft, assault, or fraud.
Modern verification APIs can complete the onboarding stack — DL, RC, insurance, challan, PUC — in under 60 seconds. There is no operational reason to delay a driver's first delivery for more than a day due to verification. The bottleneck is never the check; it's whether you've built the check into the onboarding flow.
Under the Motor Vehicles (Amendment) Act 2019, aggregators (platforms that use digital networks to connect drivers and passengers or shippers) are required to register with state transport authorities and comply with background verification mandates. States including Maharashtra, Karnataka, and Tamil Nadu have issued aggregator licensing rules that explicitly require driver BGV. Non-compliance risks licence suspension and significant fines.
Practical takeaway
If you operate a cab, delivery, or logistics aggregator platform in India, driver verification is not optional — it's a licensing requirement. Build it into your onboarding before your first operating city, not after regulatory scrutiny arrives.
Priya Nair
Head of Product, Truvixx
Writing about background verification, compliance, and workforce trust at Truvixx.
A fake licence, an undisclosed criminal record, and an unverified address are the three most common gaps in driver onboarding. Here's the full verification checklist — what to check, which databases to use, and how to complete it in under 24 hours.
Risk intelligence goes beyond a pass/fail background check. It's the ability to make nuanced hiring decisions based on verified data. Here's what it means, why it matters more than conventional BGV, and how leading Indian companies are building it into their hiring process.
Start background checks in minutes. DPDP Act compliant, API-ready, results in 24 hours.