MVAG 2025: What New Ride-Hailing Rules Mean for Your Taxi App
If you run, or are about to launch, a cab, auto or bike-taxi app in India, the Motor Vehicle Aggregator Guidelines 2025 (MVAG 2025) set the rules your app has to follow. The Ministry of Road Transport and Highways (MoRTH) issued them on 1 July 2025, replacing the 2020 guidelines, and states have been notifying their own versions since.
This guide explains the rules in plain English and, more usefully, what each rule means for the features your app needs. It's written for founders and fleet owners, not lawyers.
The Rules at a Glance
| Area | What MVAG 2025 says | What your app needs |
|---|---|---|
| Surge pricing | Up to 2× the base fare at peak times (earlier cap was 1.5×). Base fares are set by the state. | A surge engine with a configurable ceiling per city |
| Low-demand fares | Fares can drop to 50% of the base fare, but not lower. | A minimum-fare floor per city and vehicle class |
| Driver earnings | Drivers using their own vehicle receive at least 80% of the fare. A lower share (reported as 60%) applies to aggregator-owned vehicles. | Commission settings by vehicle ownership, plus clear per-trip earning statements |
| Cancellations | Riders and drivers who cancel without a valid reason pay 10% of the fare, capped at ₹100. Platforms must publish the valid reasons. | Reason-based cancellation flow, capped fee logic and automatic fee splits |
| Safety | Vehicles need AIS-140 GPS trackers and panic buttons, linked to a 24×7 control room. | In-app SOS, live trip sharing and a control-room view in the admin panel |
| Support & language | 24×7 customer support and regional-language support. | Multilingual apps, in-app tickets, optionally a voice bot for calls |
| Bike taxis | States may allow private (non-transport) motorcycles to be used for bike-taxi rides through aggregators. | Separate two-wheeler vehicle class with its own fares and checks |
| Enforcement | Licence suspension for up to 3 months; reported penalties from ₹1 lakh to ₹1 crore for serious or repeat violations. | Audit logs of fares, cancellations and SOS events |
1. Surge Pricing: Up to 2× Base Fare
The headline change: platforms can now charge up to twice the base fare during peak demand, up from 1.5×. The base fare itself is set by your state government, not by you, and fares can drop to half of the base fare when demand is low.
States can be stricter. For example, Maharashtra's draft rules proposed a 1.5× cap. So your surge engine must let you set the cap per state or city, not hard-code it.
What to check in your app: the surge multiplier must have a configurable maximum, the fare estimate shown to riders must respect that cap, and the minimum fare must never fall below the floor.
2. Driver Earnings: At Least 80% for Owner-Drivers
Drivers who own their vehicle must get at least 80% of the fare, so your platform commission on those rides is effectively capped at around 20%. Media reports put the driver share at 60% for aggregator-owned vehicles.
This matters for your business model. If your plan relied on a 25–30% commission, it no longer works for owner-drivers. Two alternatives that fit the rules better:
- Driver subscription model: drivers pay a fixed daily, weekly or monthly fee instead of per-ride commission, the model Rapido popularised.
- Fleet model: you or your vendors own vehicles, and the lower driver share applies.
Your admin panel should support different commission rules by vehicle ownership and show drivers a transparent breakdown of every trip.
3. Cancellations: 10% of Fare, Capped at ₹100
Both sides now pay for unjustified cancellations: 10% of the fare, up to ₹100. Platforms must publish the list of valid reasons (for example, driver not moving towards pickup, or rider not at the location) that waive the fee.
What to build: a cancellation screen that asks for a reason, fee logic that applies the 10% / ₹100 cap, automatic waivers for valid reasons, and a fee split between driver and platform. Log every cancellation, because disputes will come.
4. Safety: Panic Button, GPS Trackers, Control Room
Vehicles must have AIS-140 compliant GPS tracking devices and panic buttons, connected to a control room that runs 24×7. AIS-140 devices are hardware fitted in the vehicle, but your software still matters:
- An in-app SOS button for riders and drivers that alerts your control room and emergency contacts
- Live trip sharing so riders can send their route to family
- A control-room screen in your admin panel showing active SOS alerts on a map
- Driver KYC and document checks (DL, RC, permit, insurance) with expiry alerts
5. Support and Regional Languages
Platforms need 24×7 customer support and regional-language support. For a small operator, a 24×7 human call centre is expensive. A practical setup is in-app tickets and WhatsApp support during the day, plus an AI voice bot that answers calls in Hindi and English at night and escalates emergencies to a person.
6. Bike Taxis Get a Clear Path
MVAG 2025 lets states allow private motorcycles to be used as bike taxis through aggregators, subject to state rules. That opens the door for Rapido-style apps in more cities. It's still a state decision, so confirm your state's position before you launch a two-wheeler service.
Want an app that's MVAG 2025-ready from day one?
Appzur's taxi platform lets you configure surge caps, driver share, capped cancellation fees, SOS and driver KYC from the admin panel, with full source code and launch in 30 days.
See the MVAG-ready taxi platform →Your MVAG 2025 Launch Checklist
- Read your state's notification of MVAG 2025 and note its surge cap, base fares and licence process.
- Apply for an aggregator licence with the state transport department.
- Set the surge cap and minimum fare per city in your admin panel.
- Configure driver share (80%+ for owner-drivers) or switch to a subscription model.
- Publish your valid cancellation reasons and enable the 10% / ₹100 fee cap.
- Turn on SOS, trip sharing and a control-room view, and make sure vehicles carry AIS-140 trackers.
- Collect and verify driver documents with expiry reminders.
- Set up 24×7 support and regional-language apps.
- Keep logs of fares, cancellations and SOS events for audits.
Frequently Asked Questions
Do I need a licence to run a taxi app in India?
Yes. Aggregators need a licence from the state transport department of each state they operate in. Fees, security deposits and the process vary by state.
Does MVAG 2025 apply to small, single-city operators?
The guidelines apply to aggregators, meaning platforms that connect riders with drivers. If your app does that, plan to comply regardless of size, and check whether your state sets thresholds.
Can my existing app be updated for MVAG 2025?
Usually, yes. Most changes are configuration (surge cap, fees, commission) and a few new screens (cancellation reasons, SOS, control room). If your vendor won't give you the source code, updates depend entirely on them, which is one more reason to insist on source-code ownership.
Related Reading
- Taxi App Development Company: Features, Pricing & Compliance
- Taxi App Development Cost in 2026: Full Breakdown
- Uber Clone Script vs Custom Taxi App: Which Should You Build?
Sources
- Business Standard: Govt permits surge fares of up to 2x base rate for cab aggregators
- Entrackr: Govt revises ride-hailing rules: 2X surge cap, cancellation fee, and push for bike taxis
- The Week: New guidelines for cab aggregators
- Republic World: ₹100 cancellation fee, fare caps, panic button
- Outlook Business: Maharashtra issues draft rules to regulate ride-hailing platforms
