Frequently asked questions

Bandi is preparing for launch in Hyderabad. The current focus is pilot testing, driver onboarding, payment flows, safety workflows, and operations tooling before wider public availability.

Bandi is designed around direct rider-to-driver fare payment and zero ride commission. The driver keeps the ride fare, while Bandi monetizes through transparent subscription/platform fees. The product also emphasizes ride PINs, support visibility, live tracking, and local onboarding quality.

No. Bandi's intended model is 0% ride commission. Drivers pay applicable platform/subscription fees to use the service, but the rider's trip fare is paid directly to the driver.

Riders may pay the driver directly using cash or UPI details saved by the driver during onboarding. The rider app shows the driver's payment details during the ride and reminds the rider to confirm the driver received payment before using the end ride PIN.

Because trip fare is usually paid directly to the driver, refunds are not automatic in-app reversals. If there is a problem, Bandi support reviews the ride status, cancellation reason, payment proof, route/location context, PIN flow, and driver/rider reports before deciding the next action.

Airport fees, tolls, parking, waiting charges, entry fees, or government charges may be extra where applicable. These should be shown in the app, communicated by support rules, or agreed before the ride is completed.

Usually no. A QR code shown on the same device is mainly useful when the rider is paying from another phone. For same-phone payment, the app should prefer copyable UPI ID, payment phone, or a UPI deep link that opens installed payment apps.

Drivers must complete onboarding with identity details, date of birth validation, state/city details, vehicle information, document uploads, vehicle photos, payment details, OTP verification, and admin approval before they can operate.

Riders may use location for pickup and live trip tracking, but can also set pickup manually. Drivers need precise and background location permission while online or during active rides so riders and support teams can track the trip correctly.

Cancellation reason and actor are recorded. If a driver cancels after accepting, the rider can choose whether to search for another driver. Notifications and support trails are created where needed.

Bandi stores ride status, payment confirmation context, PIN workflow, support reports, notifications, and admin audit trails. The operations team can review the case and contact both parties.

The platform supports bike, auto, hatchback, sedan, premium, and XL categories. Actual availability depends on city launch, approved supply, and configured fares.

Driver wallet money is mainly used for Bandi platform fees and is not an on-demand withdrawal product. Refund or settlement flows are handled when an account is deactivated or closed, subject to admin review, pending dues, disputes, and saved payment details.

The account may move into deactivation or settlement review. Admins check wallet balance, pending rides, disputes, deductions, and payout details. Login or online access may be restricted until the settlement is completed or rejected.

Use the contact form, email narenderv7@gmail.com, or call +918142742972. Website requests are saved for the admin team to review.