Vertical · Mobility · Taxi & ride-hailing

Run Ride-Hailing Where the match Is the Market

A captain matched in seconds, an upfront fare the rider sees before booking, cancellation rules that apply to both sides, and a safety layer from ride OTP to SOS. The same DeliveryStack core, configured for passengers rather than parcels.

Matching by distance, vehicle class, and acceptance, with radius expansion
Upfront fares with surge rules your ops team sets per zone
Cancellation and no-show policy applied to riders and captains
Ride OTP, live trip sharing, SOS, and route deviation alerts
Request Quote See the apps
Ride request · Sedan Surge 1.2×
3 min to pickup · 0.9 km
✓
Aman K. · KA 05 8821
Sedan · 4.9 ★ · accepted
0.9 km
#
Ride OTP
Share with captain at pickup
4821
!
Free waiting
Then $0.10 per minute
3 min
Share trip with a contact
Fare fixed upfront · $8.40
38 s
Median time to match a captain
< 4 min
Median pickup ETA in dense zones
6.5%
Cancellations after match, both sides
4–6 wks
To launch rides in a first city

Ride-Hailing Is a Supply Problem Before It Is a Software Problem

A rider opens the app and decides in a few seconds whether your service works. If no car is nearby, they switch apps and rarely come back. The platform's job is to keep captains online where demand is, match them fast, price fairly for both sides, and make every trip feel safe.

Supply

An empty map loses the rider

Riders judge the service on the first request. Without enough captains online in the right zones, marketing spend buys app installs that never become repeat trips.

Matching

The nearest captain is not always the right one

A radius set too wide sends captains on long pickups they then cancel. Too narrow and requests go unfulfilled. Radius, expansion, and acceptance rules need tuning per zone.

Pricing

Surge that feels unfair

Riders accept a higher fare they see upfront. They do not accept one that changes at drop-off. Surge has to be visible, capped, and set by rules ops can explain.

Trust

Safety is the product

Wrong-car boardings, route deviations, and unanswered SOS alerts end ride-hailing brands. Verification and live monitoring have to be there on day one.

The Trip Lifecycle

Six states. The first two decide whether the trip happens at all; most cancellations land between them.

  1. State 01
    Requested
    Rider sets pickup and drop; upfront fare shown per vehicle class.
  2. State 02
    Matched
    Nearest captain accepts; radius widens if nobody does.
  3. State 03
    Arriving
    Live ETA, masked calling, and a waiting timer at pickup.
  4. State 04
    On trip
    Started with the ride OTP; route shared, SOS available.
  5. State 05
    Completed
    Fare finalised, payment taken, both sides rate the trip.
  6. State 06
    Settled
    Commission taken, captain paid, incentives applied.
Median time to match 38 s in zones with healthy captain supply

Ride-Hailing Features, Not Delivery Features With a Passenger Seat

Matching engine

Requests offered by distance, vehicle class, and captain acceptance rate, with radius expansion and re-offer when nobody accepts.

Upfront fares and surge

Fare cards per city and class, with surge set by demand-to-supply thresholds, caps, and zones.

Cancellation and no-show rules

Grace periods, fees, and waiting charges applied to both riders and captains, with the reason recorded.

Ride OTP and safety layer

Trip start by OTP, live trip sharing, SOS for both sides, and automatic route deviation alerts.

Captain onboarding

Licence, permit, insurance, and vehicle documents collected in-app, checked, and tracked for expiry.

Incentives and payouts

Commission by class, incentive targets by hours or trips, and daily or weekly payouts with cash netted off.

Five Surfaces, Configured for Rides

Rides add two surfaces delivery does not need: a portal for fleet owners who run several vehicles and a safety console for live incidents.

Upfront fare by vehicle class

Price shown before booking for each class, including any surge, so the fare does not change at drop-off.

Pickup pin and saved places

Pickup points snapped to where cars can stop, with home, work, and recent places one tap away.

Live captain tracking

Captain, car, and plate shown on the map with a live ETA and masked calling.

Ride OTP

Trip starts only when the captain enters the rider's code, so nobody boards the wrong car.

Share trip and SOS

Live trip link for a contact and an SOS button that alerts the safety team with location.

Scheduled rides

Book ahead for a set time, with a captain assigned shortly before pickup.

Integrations

Maps and payments carry most of the weight here: one sets the fare and the ETA, the other decides whether a low-value trip still makes money.

Maps
Routing, ETA, and geofencing

Distance and time for fares, live ETAs, pickup snapping, and zone boundaries for surge.

Payments
Cards, wallets, UPI, and cash

Local gateways per market, with cash rides reconciled against captain wallets.

Verification
KYC and background checks

Identity, licence, and background-check providers connected to the onboarding queue.

Telephony
Masked calling

Rider and captain call each other without seeing phone numbers.

Messaging
OTP and trip notifications

SMS, WhatsApp, and push providers for login codes, ride OTPs, and trip sharing.

Accounts
Corporate billing

Company accounts with ride policies, cost centres, and monthly invoices.

Where Ride-Hailing Margin Actually Goes

Four levers the platform exposes as configuration. Every one of them is a rule your ops team changes, not a release.

Lever 01

Time to match

Every second a rider waits on the search screen raises the chance they cancel and open another app.
Past 60 seconds, abandonment climbs quickly.
Lever 02

Dead kilometres

Distance driven to pickup earns nothing. Matching radius and demand heatmaps keep it short.
Pickup distance tracked per zone and hour.
Lever 03

Cancellations

A cancelled match wastes a captain's time and a rider's patience. Fees and grace periods shape behaviour on both sides.
Grace periods set per city.
Lever 04

Incentive spend

Incentives buy supply hours. Spent without targets, they buy hours in places with no demand.
Targets tied to zones and peak windows.

Taxi & Ride-Hailing FAQ

Questions specific to running taxi and ride-hailing on DeliveryStack.

Still have questions? Contact our support team

How are fares and surge configured? +

Fare cards set base fare, per km, per minute, waiting time, night charges, and tolls by city and vehicle class. Surge is a rule on the demand-to-supply ratio per zone, with a cap. Ops changes both from the admin console, and the rider always sees the final fare before booking.

Can we onboard fleet owners as well as individual captains? +

Yes. Individual captains sign up and upload their own documents. Fleet owners manage several vehicles and drivers from the fleet owner portal, set how earnings are split, and receive payouts for the fleet.

What safety features come with it? +

Ride OTP to start the trip, live trip sharing, SOS for riders and captains, route deviation and long-stop alerts, masked calling, and a full trip replay for disputes. SOS alerts go to a live queue in the safety console with the trip's location.

Can we run bike taxi or delivery on the same captain pool? +

Yes. Bike and scooter taxi is another vehicle class on the same engine. Delivery jobs can be offered to the same captains between rides, with acceptance rules deciding who sees what. Settlement stays on one run.

What about local licensing? +

The platform provides the controls regulators usually ask for: document verification, trip records, fare transparency, and SOS. Operating permits and local approvals remain the operator's responsibility, and the configuration is adjusted per market to match them.

Related Verticals

All verticals →

Launch Your Ride-Hailing Platform

Three steps from fare card to live rides in one city.

1

Fare cards and zones

City boundaries, vehicle classes, fare cards, surge zones, and cancellation rules configured.

2

Captain supply

Captains and fleet owners onboarded with documents verified before launch, so the map is full on day one.

3

Launch one city

Open rides in the densest zones first, watch time to match, then widen the service area and add classes.

Taxi & ride-hailing · Quick Facts
Surfaces 5, including fleet owner and safety
Time promise Pickup ETA
Handover Ride OTP at start
Pricing Distance, time, and surge
Typical launch 4–6 weeks
Launching rides in a first city is typically4–6 weeks