1. Cancelling a booking
Open the relevant trip or booking in the app and use Cancel when the action is available. The host or guest can cancel an offered, requested, accepted or paid booking. The app rejects cancellation of a completed or already cancelled booking.
Cancel as early as possible and tell your co-rider in chat if plans change. Cancelling a seat is different from deleting a recurring ride offer.
2. If you have not paid
An unpaid booking has no captured in-app contribution to refund. A declined request or cancelled unpaid booking does not create a refund payment. If your bank shows a debit while the app does not show payment, keep the provider reference for investigation rather than paying repeatedly.
3. If the booking is paid
The current backend attempts to request a full refund of the booked contribution through Razorpay after a paid booking is cancelled. Cancellation can succeed even if that refund request fails; the app’s Cancelled status is not proof that money has been returned.
Refund completion depends on the payment provider and bank. This draft does not promise an instant refund, a fixed number of days or an additional cancellation fee. A reliable public support and refund-status process must be confirmed before taking live public payments.
4. Problems and records to keep
Keep the booking ID, ride date, amount and payment reference if a payment or refund looks wrong. Never send your card number, CVV, banking password, UPI PIN or sign-in OTP in chat or a support request.
The official support address is not yet available. For a private test, contact your test organiser with non-secret transaction references. Completed-trip disputes and payments made outside the app are not automatically handled by the current cancellation flow.