Services · Ecommerce development · Taxi booking and payment sites

One booking and payment platform for taxi fleets operating across Saudi Arabia.

Codeeo provides taxi booking booking website development Saudi Arabia transport companies use to sell prepaid rides in several cities from one platform. A rider in Riyadh, Jeddah or Dammam chooses a route and vehicle class, sees the fare your company sets for that city, pays with mada, Apple Pay, STC Bank or a card, and receives a VAT invoice straight away. Your controllers in each branch see paid jobs for their own fleet, and head office sees the whole business in one set of reports.

Fleets that grow beyond one city often end up with a different booking method in each branch: a form in one, WhatsApp in another, cash on arrival in a third. A single platform with local fare tables and shared payment, invoicing and data rules brings that back under control without forcing every city to work the same way.

Built for
Licensed taxi, limousine and transfer companies, and hotel or corporate transport operators, selling prepaid rides in more than one Saudi city.
Typical timeline
Agreed after discovery, once licences, cities, fare rules, payment providers and integrations are confirmed, with a rollout order by city written into the scope.
What you own
The code, admin system, merchant accounts, rider and booking data, domain and hosting, all registered to your company and transferable at any time.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

Platform capabilities

Built for several cities, several branches and one finance team.

Running prepaid bookings nationally raises questions a single city never does. Should a Riyadh fare table apply in Al Khobar? Which branch issues the invoice for a Jeddah to Makkah transfer? How do corporate clients with staff in three cities receive one statement? Our taxi booking online booking system development in Saudi Arabia answers those questions with a structure of brands, branches and cities that your administrators control. Each city keeps its own fares, service areas, vehicle classes and availability, while payment, invoicing, data protection and reporting are shared. Arabic is the primary language in a right to left layout, with English and the languages your riders read added on top. Everything below is configured in the admin area by your own team after launch.

Explain your project
  • City and branch structure

    Each city or branch has its own service area, fare tables, vehicle classes, staff and schedule. Riders see only what the city they are booking in offers. Head office can add a new city by copying an existing setup and adjusting it, rather than commissioning a new site. Branch staff only see their own city's bookings and riders, which keeps access tidy.

    Opening a new city is an admin task, not a project.

  • Licence aware service settings

    The Transport General Authority licenses taxi, taxi broker and e-hailing activities separately. The platform lets you sell only the services each of your licences and branches covers, show licence details where required, and switch a service off in one city without touching the others.

    The site never sells a service your licence does not cover.

  • National payment methods

    mada debit cards, Apple Pay, STC Bank, Visa and Mastercard through a payment service provider licensed by SAMA, plus Tabby or Tamara for larger chauffeur bookings if your merchant terms allow transport. Corporate clients can settle invoices through SADAD or bank transfer where your bank supports it. Each branch can settle into the same merchant account or a separate one, depending on how your companies are structured.

    Riders and companies pay through methods they already trust.

  • Airport products for each city

    Separate airport flows for King Khalid International in Riyadh, King Abdulaziz International in Jeddah and King Fahd International in Dammam, each with terminal choices, flight tracking, waiting rules and meeting points set by the local branch. Riders arriving at one airport can also book their onward trip from another city in the same checkout.

    Airport bookings work the same way, with local details.

  • Intercity routes and deposits

    Fares for intercity trips such as Riyadh to Al Qassim, Jeddah to Makkah or Dammam to Al Ahsa, with deposits at booking and balance collection before departure. The route decides which branch fulfils and invoices the trip. Return legs can be sold with the outbound trip at a price you set.

    Long trips are paid for before a car leaves the city.

  • Corporate accounts across cities

    Companies with offices in several cities book under one account with bookers per site, cost centres, approval rules and a single monthly statement. Spending limits can be set per booker, and travel managers see reports covering every city. New companies apply online and are approved by your finance team before they can book on credit.

    National clients deal with one supplier and one invoice.

  • ZATCA e-invoicing and VAT

    Each paid trip produces a VAT invoice under the right legal entity, refunds produce credit notes, and invoice data flows to your accounting system or e-invoicing solution for Fatoora clearance or reporting, according to the phase that applies to your business.

    Tax records stay correct across every branch.

  • Cancellations, refunds and disputes

    Cancellation windows by service and city, self service changes from the confirmation link, and refunds through the original payment method. Chargebacks are recorded against the booking with the evidence your provider asks for: timestamps, driver assignment and trip completion. Refund approvals above a level you set go to a manager first.

    Disputes are answered from records, not recollection.

  • Rider messaging

    Confirmations, reminders and driver details by SMS, email or WhatsApp Business, in Arabic, English and other languages. Message timing and wording can differ by city and service, and sender names follow the registration rules for SMS in the Kingdom. Branches can add local details such as meeting points without editing the main templates.

    Riders always know who is coming and when.

  • Head office reporting

    Revenue, refunds, cancellations, corporate balances and checkout drop off by city, branch and service, matched to payment provider settlements and exportable to your ERP. Managers can compare branches on equal terms rather than through separate spreadsheets.

    Leadership sees the whole fleet's sales in one place.

Who this is for

Four kinds of operator that need a national platform.

Prepaid online booking suits trips planned ahead: airport transfers, intercity rides, chauffeur hire and corporate travel. Street hail trips run on the meter under their own rules and rarely need a checkout. Taxi booking booking website design for a national operator also has to balance one brand with local differences, so the first question in discovery is always which decisions belong to head office and which belong to each city. The answer shapes permissions, fare ownership and reporting for the rest of the build.

01

Fleets expanding from one city to several

You built a reputation in Riyadh or Jeddah and are opening branches elsewhere. We design the platform so the first city's setup becomes the template for the next, with fares, staff and service areas adjusted locally. Payment, invoicing and data rules are set once and inherited, which keeps compliance consistent as you grow, whether the next branch opens in Dammam, Abha or Tabuk.

Each new branch needs its own licence arrangements confirmed by you.

02

Limousine and chauffeur groups serving corporate clients

Ministries, banks, energy companies and event organisers book cars in more than one city and expect one account. Corporate booking, approvals, monthly statements and SADAD or transfer payment become the core of the platform, with card checkout kept for individual riders and visitors. Reports per client show trips and spend by city, which your account managers can bring to contract renewals.

03

Hotel and hospitality groups with transport fleets

Hotel groups operating in Riyadh, Jeddah, Makkah, Madinah and the Eastern Province often run or contract cars for guests. A branded booking site per property, with shared payments and reporting at group level, lets guests prepay before arrival while each property's invoices come from the right entity.

Which company invoices which trip is agreed with your accountants.

04

Operators adding prepaid booking to a dispatch system

If you already run dispatch software for drivers, the booking platform becomes the place where riders and companies buy trips. Paid bookings pass into dispatch through its API, and status updates come back for rider messages. Your drivers keep the tools they know, and you gain a proper checkout without changing operations.

How a multi-city booking platform is planned and rolled out.

  1. 01Discovery in Riyadh or by videoHead office and branch leads agree cities, licences, fare ownership, payment methods, corporate terms and refund policy. Riyadh clients can meet us in person; other cities join by video call.
  2. 02Compliance and payments setupMerchant application with a SAMA licensed provider, registering the online store with the Ministry of Commerce, PDPL records of processing, and e-invoicing integration planned with your accountants.
  3. 03Platform designArabic first, right to left booking flows, branch and city structure, corporate portal and admin roles, tested with riders, controllers and finance staff.
  4. 04Build and integrationsFare engine, availability, payments, invoices, messaging and reporting, connected to dispatch, ERP and e-invoicing systems through their APIs.
  5. 05Pilot city launchGo live in one city first, run real payments, refunds and corporate invoices, and fix what the pilot shows before adding more branches.
  6. 06City by city rolloutEach further city is configured from the pilot template, trained, tested and launched in the order agreed, with reports compared across branches.

Technology

What we build this with.

We build on a modern web stack such as Next.js or Laravel, with APIs connecting your payment provider, dispatch software, ERP, e-invoicing solution and messaging services. Data residency and hosting are agreed with you under the PDPL, and NCA controls guide security. Hosting scales for peaks such as Riyadh Season evenings or the end of Ramadan, when booking traffic rises sharply in several cities at once.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions national operators ask before launch.

Each city gets its own fares and fleet, with shared payments and reporting.

The platform is structured by brand, branch and city. Each city has its own service area, fare tables, vehicle classes, staff and availability, and riders only see what their city offers. Payment processing, invoicing, data protection and reports are shared, so head office keeps control of money and compliance. A new city starts as a copy of an existing one and is adjusted before launch.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews