Frequently asked questions

Bandi is preparing to launch soon in India and Germany, with the market auto-detected for each user. The current focus is pilot testing, captain onboarding, payment flows, safety workflows, and operations tooling before wider public availability.

Bandi is designed around direct rider-to-captain fare payment and no percentage commission. Captains pay a small flat per-ride fee plus insurance and keep the rest of the fare. The product also emphasizes ride PINs, support visibility, live tracking, and local onboarding quality.

No percentage commission. Captains pay a small flat per-ride fee plus insurance and keep the rest of the fare. These per-ride charges accrue as dues that the captain clears by the next day; the rider's trip fare is paid directly to the captain.

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

Because trip fare is usually paid directly to the captain, 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 captain/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.

Captains 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. Captains 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 captain cancels after accepting, the rider can choose whether to search for another captain. Notifications and support trails are created where needed.

You can end a ride mid-trip. You pay for the distance used so far plus a small closing fee (a percentage of the remaining estimate), shown before you confirm. You'll also be asked the reason, and if something went wrong you can flag it so the Bandi team reviews the ride.

If you're not at the pickup and not reachable, the captain waits a short grace period, tries to call you, and can then report a no-show, which cancels the ride. A no-show is not penalised automatically - it opens a case that the Bandi team reviews (looking at GPS, wait time, and call records). After review, a small no-show fee may apply before you can book again. Genuine cases (captain never arrived, wrong location) are not charged.

If the captain has a vehicle breakdown, you are not charged and Bandi looks for another captain from your current location. If the captain ends a ride for a safety or other reason, the case is escalated to the Bandi team for review before any charge or action.

Yes. When ending a ride you can flag that you need help, and a blocked account shows how to contact us. The Bandi team reviews each case manually - no fee or block is applied without a human review.

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.

Vehicle types depend on the market, which the app auto-detects. In India the platform supports bike, auto, hatchback, sedan, premium, and XL categories; in Germany rides are with licensed taxi and car partners. Actual availability depends on launch, approved supply, and configured fares.

Captains do not recharge or hold a wallet balance. After each completed ride, a small flat per-ride fee plus insurance accrues as dues, which the captain clears by the next day. It is not a subscription, a daily fee, or a wallet top-up.

The account may move into deactivation or settlement review. Admins check any outstanding per-ride dues, pending rides, disputes, 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.