The price is fixed before you book
Fares are calculated on our servers from distance, duration, vehicle type and any surcharges, then shown as one number. No meter, no surge surprise at the door.
Feature listing
Oye.cab is one system with four front doors: a rider app, a driver app, an operator console for taxi companies with their own fleet, and a business portal for invoiced accounts. Below is the full list, grouped by who uses it.
The short version
Fares are calculated on our servers from distance, duration, vehicle type and any surcharges, then shown as one number. No meter, no surge surprise at the door.
Once a driver accepts, their position updates live on your map, and the trip status moves with them: heading to pickup, arrived, on the way, completed.
Every trip has a personal PIN. The driver cannot start the trip until the code matches, so you always know the car at the kerb is the one you booked.
In-app chat is scoped to the trip, so you can say "I'm at the side entrance" without giving out a phone number. Messages are cleared on a retention schedule.
Card payments run through Stripe; cash is available where the region allows it. Business accounts skip payment at booking and settle on a monthly invoice.
Send a read-only link and whoever you send it to can follow the route and the arrival, without an account and without seeing anything else.
Booking a taxi should be a decision you make once, at a price you already know.
Distance, duration, vehicle type and surcharges are priced server-side and returned as one total before you confirm.
Pick the vehicle category that fits the trip; each class carries its own multiplier in the quote you see.
Flag needs such as extra assistance or additional luggage and the quote is itemised with the matching surcharges.
One-off booking without creating an account, with the same fixed fare and tracking.
Common point-to-point routes inside a service region are offered at a set price per region.
Reserve a vehicle and driver for a block of time instead of a single ride; the driver approves, then you pay and confirm.
The assigned driver's position and the route to you update in real time.
A personal code that must match before the trip can be started.
Message your driver inside the trip. No phone numbers exchanged, retained only as long as the policy allows.
A read-only page for anyone you send it to, scoped by token and limited to that trip.
Discounts apply to standard rides, fixed-route bookings, guest bookings and reservations.
Stripe checkout for card, or cash where the service region permits it.
An itemised receipt with the amount charged, generated after the trip closes.
Booking, acceptance, arrival and completion arrive by email and push notification.
Rate the trip afterwards; ratings feed back into driver standing on the platform.
Raise a dispute against a trip or receipt and have support review it, with refunds handled through the payment provider.
Take the rides you want, when you want them, and see what you earned.
Browse rides waiting in your region and accept the ones that fit your day.
Step-by-step setup that shows exactly what is still missing before you can accept work.
Upload licence, insurance and vehicle papers; requirements follow the rules of your service region.
Publish when you are available so work lands in the hours you actually drive.
List your vehicle and yourself for day hire and approve or decline each reservation request.
Move the trip through arrival, PIN-verified start and completion from your phone.
Every completed trip, what the platform took and what was paid out, in one ledger.
New rides in your region and reservation requests reach you without keeping the app open.
Session handling built for drivers who switch between a phone and a tablet in the car.
Move staff and clients without handing out a company card.
Approved business accounts book straight through; the ride opens for drivers without a payment step.
All rides for the period on one invoice instead of a receipt per trip.
Invoices are produced in bulk for the billing period and delivered as PDF.
A company is reviewed and approved before invoiced billing is switched on.
Each invoice line ties back to a trip, its route and its fare, so cost centres can be reconciled.
A dedicated portal for booking, trip history and invoices, separate from the rider app.
Bring your own fleet and keep dispatch, drivers and paperwork in one place.
A dashboard scoped to your company: your rides, your drivers, your vehicles.
Invite drivers to join your fleet and track invitations from sent to accepted.
Drivers attached to your company get their own portal for jobs, documents and agenda.
Assign incoming work to a specific driver instead of leaving it to the open marketplace.
Store and renew operator-level licences and insurance with expiry tracking.
Everything an operator sees and does is limited to the service regions they are approved for.
The machinery underneath every booking.
Bookings are validated against geofenced areas, so a ride cannot be created outside the zone that can serve it.
Payment methods, currencies and features are switched on region by region rather than globally.
Each region carries its own pricing configuration, with a global fallback.
Amounts are converted with refreshed exchange rates for display outside the home currency.
Ride, trip and location changes are pushed over persistent connections to riders, drivers and dashboards.
Cancellation and no-show fees are applied by a fee engine, with refunds issued through the payment provider.
Rate limiting, account lockout and authenticated real-time connections guard the booking paths.
A support desk with its own permissions handles disputes, refunds and account issues.
Stale rides are closed and unpaid reservations expire on their own instead of hanging in the system.
Where the numbers come from
Every fare, distance and duration on Oye.cab is calculated on our servers and sent to the app as a finished figure. The app renders it; it does not compute it. That is a deliberate design rule, and it is what makes a quote binding rather than an estimate that shifts between devices.
The same rule covers receipts and payouts: what a rider is charged and what a driver is paid are derived once, stored, and shown identically in the rider app, the driver app, the operator console and the invoice.
Tell us what your riders, drivers or dispatchers are missing. Email contact@oye.cab — feature requests from operators running real fleets carry the most weight.