Reducing Ride Cancellations on Rapido with Smart Incentives

✳The problem they went after

Daily commuters use Rapido to get to the office, and a cancellation sends them to a competing app at the moment they can least afford the delay. The submission stays on this segment on purpose, because time-sensitive commutes turn each cancellation into a retention event rather than an inconvenience, and repeated ones wear down trust in the platform.

✳What they actually did

Ten solutions were brainstormed and scored with RICE. The top two are a Cancellation Cashback Guarantee, paying riders in Rapido coins when a driver-initiated cancellation lands more than two minutes into the wait, and Guaranteed Driver Match, which pre-selects only high-reliability drivers with low cancellation histories. Supporting features include alerts based on peak-hour probability data and a driver reliability badge for frequent users. The cashback design carries its own controls: a fraud-check engine watching for rider-driver collusion, monthly caps, and a geo-location tracker flagging suspicious cancellation clusters.

✳What you can take from it

Worth stealing

Cashback triggers only after a two-minute cancellation wait
Matching restricted to drivers with low cancellation history
Fraud engine, monthly caps and geo-clustering ship with the payout
Guardrail: revenue per retained user must justify cashback

Read this if

Anyone designing a payout or compensation feature people will try to game

The transferable bitPayouts invite gaming, and this submission treats that as part of the design rather than something to handle later. Collusion detection, monthly caps and geo clustering ship alongside the feature. The guardrails follow the same logic, checking that cancellation rates do not rise after launch and that revenue per retained user covers what the cashback costs.