VAHAN Mobile Mandate: How a Missing Phone Number Blocks RC Transfer

Every year, thousands of used car buyers in India arrive at the RTO with the sale agreement, insurance, PUC, and both forms ready — only to discover that the transfer cannot proceed because the seller's registered mobile number on the VAHAN portal is dead. The number belongs to a SIM the seller discarded three years ago. Or it was the dealer's number when the car was originally registered. Or it is the seller's father's number, who has since passed away. In all three cases, VAHAN sends a transfer-consent OTP to a number that nobody can receive — and the entire ownership transfer comes to a halt. MoRTH's nationwide mobile number mandate, which requires every vehicle owner to link an active number to their VAHAN record, was issued specifically to clean up this problem. The mandate is real, the enforcement dependency is live, and an estimated 5 to 8 crore vehicles in India still have outdated or absent mobile records. For a buyer putting down token money on a used car, this is now one of the most material pre-purchase checks to run.

What the MoRTH Mobile Mandate Actually Requires

The Ministry of Road Transport and Highways issued a nationwide guideline directing all vehicle owners to register and maintain an active mobile number against their vehicle record on the VAHAN portal at vahan.parivahan.gov.in. The mandate is not a standalone piece of legislation; it operates as an operational directive integrated into the VAHAN 4.0 platform, which now treats the linked mobile number as a required field for all consequential transactions on a vehicle's record.

In practice, the mandate creates a dependency chain. RC renewal requires OTP verification to the registered mobile before the application can be processed. Ownership transfer under Form 29 and Form 30 triggers an OTP to the seller's registered number for digital consent before the transfer request enters the RTO queue. DigiLocker's RC pull and mParivahan's digital RC display both link to the mobile number on the VAHAN record — if that number is absent or outdated, neither app can show the document. PUC certificate linkage to the VAHAN database for 2026 renewals also requires a matching mobile record. The mobile number, in other words, is no longer administrative metadata on the VAHAN portal — it has become operational infrastructure for the vehicle's ability to transact.

Why Sellers Have Dead Numbers on VAHAN

The scale of the problem — an estimated 5 to 8 Crore vehicles with outdated or missing mobile records — is not caused by malice. It is caused by the ordinary churn of the Indian mobile subscriber base over the period that most used cars on the market today were originally registered.

None of these situations is unique, and none of them is something a seller typically knows to disclose. The seller who registered their Maruti Swift in their father's name in 2019, lost their father in 2022, and now wants to sell the car genuinely may not have considered that the mobile number on the VAHAN record is the number that will need to receive the transfer OTP. From the buyer's perspective, the risk is invisible until the RTO process begins.

The Transfer Process — Where It Breaks

Understanding the exact failure point requires tracing the Form 29/30 workflow as it operates in 2026. When a buyer and seller agree on a price and begin the formal transfer, the sequence runs as follows: the seller submits Form 29 — the notice of transfer — to the RTO, and VAHAN sends an OTP to the seller's registered mobile number to authenticate that the seller is confirming the transfer voluntarily. The buyer simultaneously submits Form 30 — the transfer application — with supporting documents. VAHAN may also send an OTP to the buyer's registered number for confirmation.

If the seller's number on VAHAN is dead, the OTP for Form 29 consent is never delivered. VAHAN holds the application in a pending state waiting for the consent OTP to be validated. The buyer's Form 30 application sits incomplete because it cannot proceed without the Form 29 consent. The RTO counter officer cannot bypass the OTP requirement in the system — it is an automated gate, not a manual discretion point. The application then sits in limbo until one of three things happens: the seller visits the VAHAN portal and updates their number (which itself requires receiving an OTP on the old number — creating a catch-22 if the old number is truly dead), the seller visits the RTO in person to complete manual identity verification and consent, or the buyer and seller agree to pursue a court-ordered transfer through a civil process that can take 12 to 18 months.

The clean resolution — seller updates VAHAN mobile number before the transfer — requires 24 to 48 hours after the update reflects on the portal and is then available for OTP delivery. For this reason, the pre-sale mobile number check, and the seller's ability to demonstrate active receipt of OTPs on their registered number, should happen during the negotiation phase, not after the token has moved. As the parallel issue of pending challans blocking RC transfer illustrates, the pattern of pre-transfer gate failures is consistent: the problem is always cheaper to identify before money changes hands than after.

DigiLocker and mParivahan: The Other Reason This Matters

The RC transfer OTP is not the only downstream consequence of a stale VAHAN mobile number. Two widely-used government apps — DigiLocker and mParivahan — both pull vehicle document data from the VAHAN backend, and both require the mobile number on the VAHAN record to match the user's registered mobile before the RC is displayed.

For daily use, this means a seller who cannot show their RC on mParivahan during a police check has a data gap in their VAHAN record that is visible and verifiable on the spot. Under Section 130 of the Motor Vehicles Act, a police officer can ask for the RC and insurance during a routine check; mParivahan is an officially accepted digital substitute for the physical document since the MoRTH notification of November 2018. A seller whose mParivahan shows no vehicle or shows a fetch error is almost certainly working with a number mismatch on the VAHAN portal — a detail a buyer can check during the physical inspection meeting by asking the seller to open mParivahan and show the vehicle details.

DigiLocker has a separate but related implication. Banks issuing hypothecation NOC letters, insurers processing renewal and claim documents, and RTOs handling duplicate RC requests all accept DigiLocker RCs as primary documents. A seller who cannot produce a DigiLocker RC — either because the number is missing or mismatched — will need to use a physical RC instead. If the physical RC is old, faded, or a duplicate from a previous loss, the buyer should treat the inability to produce a clean DigiLocker RC as a data signal about the health of the underlying VAHAN record. It does not indicate fraud by itself, but it warrants a closer look at the full record before proceeding.

How to Update the Mobile Number Before Selling

Sellers who are aware of the issue and want to resolve it before listing the car have a clear path. The VAHAN portal provides a self-service mobile number update facility that works without an RTO visit in most cases — provided the old number is still accessible for the initial OTP. For sellers whose old number is truly inaccessible, the RTO visit path is the fallback.

1. Go to vahan.parivahan.gov.in and click on the Services menu in the top navigation. Select Update Mobile Number from the services list.
2. Enter the vehicle's registration number exactly as it appears on the RC — state code, district code, series, and number with no spaces (for example, MH12AB1234).
3. Enter the last 5 digits of the chassis number. This is printed on the RC booklet on the front page under "Chassis No." and is also stamped on the vehicle's firewall or door jamb.
4. VAHAN sends an OTP to the currently registered mobile number. Enter it to authenticate the session. If this step fails because the old number is inaccessible, proceed to the RTO visit path below.
5. Enter the new mobile number and confirm it. VAHAN sends a confirmation OTP to the new number. Enter it to complete the update.
6. The update typically reflects in 24 to 48 hours. After reflection, verify by logging into DigiLocker with the new number and confirming the RC is accessible.

For sellers whose old number is not accessible — the SIM is discarded, the number belongs to a deceased relative, or the number was a dealer's corporate line — the process requires a visit to the concerned RTO with identity proof (Aadhaar), RC original, and a written request for mobile number update. The RTO verifier authenticates the owner in person and updates the record manually. This typically takes 3 to 7 working days after the RTO visit, depending on the state.

What a Buyer Can Check Before Paying Token Money

The VAHAN portal does not expose the registered mobile number publicly — for good reason, given the privacy implications. A buyer cannot directly verify whether the number is active by looking at the portal. But there are two practical steps that, used together, give a buyer a reasonable assurance that the VAHAN record is well-maintained and that the transfer will not stall.

The first step is to pull the full VAHAN record before the token. Vahan Verify returns the SurePASS CarReg report — the same government database that the VAHAN portal itself draws on — showing RC status, registered state, owner name, insurance validity, fitness certificate, road tax, loan and hypothecation, and all-India challans. The report does not display the mobile number (the SurePASS API intentionally masks it), but a comprehensive record with all fields populated — clean RC status, active insurance, valid PUC, no outstanding loan — strongly correlates with a VAHAN record that has been actively maintained, including the mobile number. Conversely, a record with multiple gaps, outdated insurance, or zero-field entries for PUC is a signal that the seller has not been interacting with the VAHAN ecosystem, which is the same condition that produces stale or dead mobile numbers. The broader VAHAN RC verification guide for used car buyers covers the full record check in detail.

The second step is to ask the seller, during the test drive or inspection meeting, to open mParivahan on their phone and show the vehicle listed under their number. If the vehicle appears in mParivahan with the correct registration number, the seller's current phone number is matched to the VAHAN record. If mParivahan cannot find the vehicle, or the seller hesitates, the buyer has identified the problem before paying anything. This is a two-minute test that requires no payment and no tool — just the presence of the seller with their phone during the meeting.

Red Flags in the VAHAN Record That Buyers Miss

Beyond the mobile number question, the VAHAN record surfaces several categories of data that buyers routinely overlook when they are focused on the car's mechanical condition and price. Each of these has a direct bearing on whether the RC transfer will proceed cleanly and whether the buyer will face post-transfer complications.

RC status other than ACTIVE. The VAHAN record shows an RC status field. The clean state is ACTIVE. SUSPENDED means a court or transport authority has placed a hold on the vehicle — possibly for accumulated challans, emissions violations, or a pending legal matter. CANCELLED means the RC has been cancelled, typically because the vehicle was declared a total loss, scrapped, or re-registered elsewhere. BLACKLISTED means the vehicle is flagged in the national database — often for use in a crime, VIN tampering, or insurance fraud. As the challan liability transfer guide explains, even a SUSPENDED status that is not disclosed by the seller can attach ongoing liability to the buyer once the RC moves to their name. Any status other than ACTIVE is a hard stop — verify the specific reason and get it in writing from the seller before proceeding.

Hypothecation not cleared. If the vehicle was originally purchased with a loan, the lender files a hypothecation entry on the VAHAN record. This entry remains until the borrower clears the loan and the lender files a hypothecation removal (HR) form with the RTO. A VAHAN record that still shows an active hypothecation entry cannot be cleanly transferred to the buyer's name without the lender's NOC. The hypothecation trap and NOC guide covers the exact documents required. This is one of the most common used car transfer complications in India and is fully visible in the VAHAN record.

Insurance expired or near-expiry. The VAHAN record shows the insurance policy expiry date. A vehicle with expired third-party insurance cannot be legally driven on Indian roads under Section 146 of the MV Act, and the buyer takes on a liability gap the moment they drive it home. Check whether the insurance expiry date is at least 30 days in the future, and budget for renewal as part of the transaction cost if not. Under IRDAI guidelines, a new owner must transfer the existing policy or take fresh cover immediately after RC transfer.

Fitness certificate (for older vehicles). Vehicles more than 15 years old require a valid fitness certificate from an authorised testing station. The VAHAN record shows the fitness certificate expiry. A vehicle with an expired fitness certificate cannot be renewed for RC and cannot legally be driven; the buyer inherits the need to pass the fitness test, which for older vehicles can require repairs. Confirming this field before purchase is particularly important for vehicles above the 10-year mark in metro cities where vehicle age restrictions apply.

Owner count mismatch. The VAHAN record shows the number of previous owners. If the seller says "single owner" but the VAHAN record shows three prior owners, the discrepancy needs explanation. Each ownership transfer should be documentable through the Form 29/30 records. A mismatch often means the RC transfers were not always completed formally — which in turn means the VAHAN record may have gaps that create complications for the current transfer.

Back to Auto News