Pending Challans Can Block Your RC Transfer

For years, Indian used car buyers treated pending e-challans as a seller problem. That calculation changed this year. Under MoRTH's tightened 2026 procedure, the RTO will not issue Form 28 approval — the transfer NOC that moves the car from seller to buyer — if the Parivahan eChallan portal shows any unpaid e-challans, court-pending challans, or FASTag dues against the vehicle's registration number. The rule is simple, the enforcement is now digital, and a single Rs 500 challan that the seller forgot about is enough to stall your ownership transfer by three to six months. This piece explains what changed, how to check the eChallan portal before you pay a token, how challan liability flows between seller and buyer after the sale, and how a pre-payment verification report can keep you out of the worst category of used-car disputes — the ones where the car is in your garage but the RC is not in your name.

What Changed in the 2026 MoRTH Procedure

The underlying law has not changed. Section 50 of the Motor Vehicles Act 1988 and Rules 55-56 of the Central Motor Vehicles Rules 1989 have long required Form 28 (an NOC from the issuing RTO), Form 29 (notice of transfer from the seller) and Form 30 (application for transfer from the buyer) to move an RC from one name to another. What has changed is the integration between the eChallan database and the RTO's transfer back-end. As of 2026, every Form 28 application now triggers an automated lookup against the Parivahan eChallan portal before it is processed. If the lookup returns any pending entries — paid-but-not-reconciled, court-pending, or outstanding — the application is held in a queue until the vehicle shows a clean status.

In the older workflow, a polite seller could often get Form 28 signed off with an undertaking to clear challans later. That margin has disappeared. The transport department's internal SOPs now flag any pending dues automatically, and the counter clerk can no longer waive the check even if the parties agree between themselves. The logic is defensible — challans recorded against a vehicle accompany the RC, and moving ownership while dues are pending simply shifts the enforcement problem onto the new registered owner — but the practical consequence for buyers is that every transfer now turns on the quality of a pre-sale challan check.

Anatomy of an E-Challan — Who Issues It and Why It Shows on Parivahan

Not every fine against a vehicle comes from the same authority, but they all end up in the same place. Traffic-police challans under Sections 177 to 210 of the Motor Vehicles Act — speeding, red-light violation, no-helmet, wrong-way, no-seatbelt, overloading — are issued by the state police and uploaded to the state's eChallan interface, which then syncs to the central Parivahan eChallan portal. NHAI's FASTag system records VRN-mismatch and unpaid toll events directly into the same database. State road-tax arrears, permit violations under Section 66 for commercial vehicles caught running without permit, and registration-tampering notices under Section 39 are logged by the state transport department and also sync across.

The important detail for buyers is that all of these, regardless of origin, attach to the vehicle's registration number rather than to the individual driver's name. The MV Act does hold the person at the wheel at the time of offence legally liable — but the challan itself sits against the VRN on Parivahan. For unmanned camera challans, FASTag mismatches, and most road-tax arrears, the driver is never identified at all; the vehicle takes the fine. When a buyer takes delivery of a car with unresolved entries of this kind, those entries follow the car into the new ownership unless they are explicitly cleared and reconciled before the transfer.

How to Check Pending Challans Before You Pay a Token

The official source of truth is the Parivahan eChallan portal at echallan.parivahan.gov.in, which is free, open to the public, and returns the pending list against a registration number in under a minute. This should be the first thing a serious buyer does after viewing a car — ideally before even negotiating the price. Our in-depth walkthrough on how to check car challans and loans in India covers the portal navigation step by step.

1. Open echallan.parivahan.gov.in in a browser. No login or account is required.
2. Click Check Challan Status, then enter the vehicle's registration number exactly as it appears on the RC (for example, MH12AB1234 with no spaces).
3. Enter the last four digits of the chassis number, which is printed on the RC and the windshield VIN plate. This step prevents casual lookups against random VRNs.
4. Complete the captcha and click Get Detail. The portal returns a list of all pending and paid challans, court-pending cases, and FASTag dues linked to that VRN.
5. Save a screenshot of the result with the timestamp visible. If the sale goes ahead, this is your pre-sale record of challan status — useful for civil recovery if the seller later disputes liability.

The portal output covers the Motor Vehicles Act challan database but can occasionally lag by a day or two on the most recent entries, particularly in states where the state transport system syncs to the central portal on a scheduled basis rather than in real time. For that reason, a lot of cautious buyers pair the free portal check with a paid report that pulls the same underlying data plus RC status, insurance validity, PUC, and ownership history in a single PDF. Vahan Verify is one such tool — it returns the SurePASS CarReg report with the live pending-challans list alongside RC status, owner name, insurance expiry, and PUC validity in a single Rs 49 PDF, giving a buyer a consolidated snapshot that can be shown to the seller before any token money changes hands. For the price of the report, the downside protection is straightforward: it is meaningfully cheaper than getting stuck with an un-transferable car.

Who Pays for a Pre-Transfer Offence — The Liability Flow

The legal principle is clean in theory and messy in practice. Under the MV Act, the person driving at the time of the offence is the one who is liable. In practice, the challan is recorded against the vehicle's registration number, so the seller is the person of record for every pre-sale entry until it is cleared. The RTO treats the matter as a vehicle-level pending due and will not move the Form 28 application until that due is settled, regardless of who was at the wheel.

This creates three recovery patterns that buyers routinely face in used car transactions. In the cleanest case, the seller checks Parivahan, clears any pending challans before the sale, and the transfer goes through on schedule. In the second case, the buyer discovers pending challans only during the RTO transfer appointment; the seller agrees to clear them, pays on the portal, waits 24 to 48 hours for reconciliation, and the transfer resumes. In the third and most painful case, the seller has already disappeared or is refusing to clear the challans; the buyer ends up paying them to complete the transfer, and any recovery from the seller becomes a civil small-claims matter.

One protective clause to include in the sale agreement is a written undertaking that the seller is responsible for any challans issued before the transfer date, specifically listing the Parivahan snapshot date on which the vehicle was verified clean. If a retrospective challan appears — some state systems can take up to 45 days to upload a camera challan — the buyer then has a clean contractual basis to ask the seller to clear it. Pairing this clause with a pre-sale Parivahan screenshot or a Vahan Verify PDF gives the buyer both legal and evidentiary footing.

City-Wise Enforcement — Where the Check Matters Most

The eChallan database is national, but enforcement intensity varies sharply by state and city. Delhi, Maharashtra, Karnataka, Telangana and Tamil Nadu run the most aggressive automated enforcement programmes, and cars registered in these states typically carry the heaviest camera-challan footprints. Delhi's CCTV-based violation capture across the Ring Road corridors, Mumbai's speed-camera rollout across the Western and Eastern Express Highways, Bengaluru's integrated toll-plus-green-tax adjustments, and Chennai's signal-offence capture network all feed entries into the Parivahan portal at scale.

Used car buyers in Delhi should specifically check for CCTV over-speeding and red-light entries, which are the single largest category in the NCT. Buyers in Mumbai will see speed-camera and no-helmet entries dominate the list. In Bengaluru, the mix tilts toward toll mismatch and green-tax arrears, because Karnataka runs a state green tax that is often unpaid on older vehicles. In Hyderabad, the Telangana traffic enforcement pipeline has been digital for longer than most, and even small offences from several years back can surface. Bihar, Uttar Pradesh and West Bengal have historically lagged in eChallan integration, but the Parivahan Phase III rollout through 2026 is closing that gap, and buyers in these states should assume the check is now just as binding as it is in the south.

The RC Transfer Timeline — Where Challans Bite

Understanding the sequence of forms makes it clear why pending challans hurt the buyer more than the seller. The transfer starts when the seller submits Form 29 — the notice of transfer — to the RTO, acknowledging that the car has been sold and declaring the buyer's details. Simultaneously, the buyer submits Form 30 — the application for transfer — with the sale agreement, insurance certificate, and PUC. If the car is changing state, an additional Form 28 NOC is needed from the original registering RTO, consenting to the re-registration in the new state. Our step-by-step RC transfer guide walks through each form, and the NOC primer covers when Form 28 applies. For an inter-state move, the re-registration walkthrough is the companion read.

The challan check happens at the Form 28 stage for inter-state cases and at the equivalent pending-dues check for intra-state transfers. If the check returns any entry, the application enters a pending queue. The buyer has already paid the token, may have already taken delivery, and now has a car in the garage but no transfer in hand. Clearing the challan takes 24 to 48 hours to reflect on Parivahan in integrated states; in slower-state systems, 5 to 7 working days is realistic. If the seller is unavailable to pay the challan, the buyer either pays it themselves or waits indefinitely for the seller to comply. The cost of getting stuck in this loop is typically three to six months of a car sitting un-transferred — during which the original owner remains legally responsible for any fresh challan, insurance lapse, or accident, and the buyer has no legal ownership document in their name.

The Verification Habit — How Careful Buyers Handle It Now

The pattern that has emerged among experienced used-car buyers in 2026 is to split the verification into two moments. The first moment is before any money changes hands: a Parivahan eChallan check and, for buyers who want the consolidated view, a paid report that bundles challans, RC status, insurance, and PUC. The second moment is immediately before the RTO appointment: a repeat check to confirm nothing new has surfaced in the 45-day camera-challan lag window that some states run. The Vahan portal ownership history walkthrough is the companion piece for buyers who also want to verify ownership chain and hypothecation at the same time.

For sellers on the other side of the transaction, the calculus is similar but reversed. A seller who checks the eChallan portal before listing the car, clears any pending dues, and mentions the clean Parivahan status in the listing description consistently gets higher offers and faster closures. On VahanBazaar, the RC-verified listing pathway already pulls the SurePASS CarReg data at listing creation, which gives buyers the first-stage check automatically — but the final pre-token verification remains the buyer's responsibility, and should be dated close to the transaction.

The Cost of Getting Stuck

The direct cost is the value of the unpaid challans, which in isolated cases runs to tens of thousands of rupees on vehicles that have accumulated camera violations and FASTag mismatches over years. The larger cost is indirect. Every month that the transfer sits in limbo is a month of insurance premium paid by the buyer on a vehicle that is not registered in their name, a month during which any fresh accident puts the buyer in an ambiguous legal position, and a month during which the risk of the seller disappearing increases. For buyers in the most common price brackets — cars in the Rs 4 Lakh to Rs 12 Lakh range — the cumulative soft cost of a three-to-six-month stall often exceeds the cost of the original challan by a multiple.

Against this, the pre-token verification cost is negligible. The Parivahan portal is free. A paid consolidated report like Vahan Verify costs Rs 49 and returns the SurePASS CarReg data plus the live challans list in a single PDF. Neither option requires more than ten minutes of the buyer's time. The bargain being made is not "spend Rs 49 to save Rs 49" — it is "spend Rs 49 to avoid the one category of used-car dispute that takes months to unwind and sometimes never resolves cleanly". For anyone about to transfer meaningful money into a seller's account for a used vehicle, the arithmetic is straightforward.

Back to Auto News