Ride-hailing glossary

Every ride-hailing term
operators actually use,
defined plainly.

50+ terms, alphabetised, anchored, plain-language. Bookmark a definition with a stable URL fragment, link a driver to it, or read straight through to onboard a new operations hire.

Start a free demo Talk to sales

An open editorial dictionary spread illustrating the ride-hailing glossary

50+

Terms defined, all anchored for direct linking

A–W

Coverage from Acceptance rate through White-label

MENA-aware

Regional context called out where it differs

May 26

Last updated, revised quarterly

Last updated · May 202620 min readReference

Most ride-hailing terminology is a mix of Uber's internal vocabulary and whatever the local regulator decided to translate it to. The result is a category where operators in the same city use four different names for the same concept and assume everyone else knows what they mean.

This glossary tries to fix that. Each term is defined plainly, with the MENA-specific nuance called out where it matters. The URL fragment for every entry is stable, so you can bookmark a single definition, share it with a new operations hire, or quote it back to a regulator who is asking what your platform actually does. We revise the page quarterly as the category vocabulary evolves.

Jump to a letter

A B C D E F G H K L M O P R S T U V W

A–W

The full glossary
of ride-hailing terms

Every term has a stable #anchor so you can link directly to a single definition. The MENA-specific terms (mada, STC Pay, TGA) are folded into the same A–W stream.

A3 terms

Acceptance rate: The share of dispatched ride requests a driver accepts within the timeout window. Most operators target above 80%; lower rates signal poorly-matched assignments or driver dissatisfaction.
Aggregator: A platform that connects multiple fleets or operators under a single rider-facing app. Different from a white-label platform, where each operator runs its own brand.
Admin panel: The web console operators use to configure service types, fares, driver onboarding, role permissions, content pages and finance reports. In Waslni it is also the panel customer-service teams use to handle refunds and rider issues.

B2 terms

Base fare: The fixed component of a ride fare charged at trip start, before per-km and per-min components. Typically 2–8 currency units in MENA cities depending on service type.
Booking fee: An optional flat fee added to the rider's invoice to fund platform operations. Often called 'service fee' on receipts. Distinct from base fare.

C4 terms

Cancellation fee: The fee charged to a rider who cancels after a configurable grace period (commonly two minutes) or after the driver arrives. Settles to the driver to compensate for time invested.
Captain: Careem's local-cultural rebrand of 'driver'. Used widely in MENA marketing. Functionally identical to 'driver'.
Commission: The percentage of each completed-trip fare the platform retains, with the remainder paid to the driver. Typically 10–25% in MENA, configurable per service type and city in Waslni.
Completed trip: A trip the rider successfully reached the destination on, distinguishable from cancellations and no-shows. The most common usage-based pricing meter in white-label platforms.

D5 terms

Dispatch: The system that matches incoming ride requests to drivers. Modern platforms use proximity + rating + load score; legacy radio dispatch relied on a human at a base-station microphone.
Dispatcher: A human operator at the operator console who handles phone-in bookings, manual driver reassignment, and customer-service escalations. Replaces the radio-dispatch role.
Driver app: The mobile app drivers use to go online, accept rides, navigate, view earnings, upload documents, and withdraw payouts. Native iOS + Android in white-label platforms.
Driver wallet: An in-app ledger that tracks a driver's earnings, cash collected (negative balance), commission owed, and pending payouts. Reconciled with bank transfers on the payout calendar.
Dynamic pricing: Surge-style multiplier applied to fares during high-demand periods. Distinct from peak-hour pricing (fixed windows) — dynamic pricing reacts to live supply/demand.

E2 terms

ETA: Estimated Time of Arrival — both pickup ETA (when the driver reaches the rider) and drop-off ETA (when the rider reaches the destination). Rider apps display both.
e-Hailing: Regulatory term used in MENA and some Asian markets to describe ride-hailing. License regimes often distinguish 'e-hailing' from traditional taxi licensing.

F2 terms

Fare formula: The expression that calculates a trip fare. Typically: base_fare + (distance × per_km) + (time × per_min), with floor and ceiling caps. Configurable per service type and city.
Fleet: A collective of drivers (and sometimes vehicles) managed under a single operator brand. Distinct from a 'tenant' (the platform-level brand container) — one tenant may contain multiple fleet partners.

G1 term

Geofence: A geographical polygon defining a service area. Used for city-bounded dispatch, surge zones, airport pickup zones, and per-zone pricing rules.

H1 term

Heatmap: A driver-app overlay showing where ride demand is concentrating in real time. Helps drivers reposition before peak. Reduces empty kilometres.

K1 term

KYC: 'Know Your Customer' — the identity verification process for drivers (license, ID, vehicle documents) and sometimes riders (corporate accounts, regulated services). Required by most transport authorities.

L2 terms

Lahza: A Palestinian payment gateway used in Waslni production deployments for Palestine and Egypt. Card and wallet processing for both local and cross-border flows.
LTV (Lifetime Value): The total revenue a rider or driver generates across their full relationship with the platform. Central to acquisition-cost decisions — you should not pay more to acquire a rider than they are worth.

M3 terms

mada: The dominant card scheme in Saudi Arabia, mandatory for Saudi-issued debit cards. Ride-hailing apps targeting Saudi customers must support mada via HyperPay, PayTabs, or another local acquirer.
Multi-tenant: An architecture where a single platform instance serves multiple isolated brands ('tenants'). Each tenant has its own database, branding, and configuration, but the underlying code is shared. Waslni is multi-tenant from day one.
MQTT: A lightweight publish-subscribe messaging protocol used in ride-hailing for real-time driver location updates and order state changes. Waslni runs an MQTT broker (aedes) alongside the API.

O2 terms

Operator: The company running a ride-hailing service. In multi-tenant platforms, each operator is one tenant. The operator owns the brand, the driver and rider relationships, and the commercial terms.
OTA update: 'Over-the-air' update — pushing JavaScript code changes to already-installed mobile apps without requiring a new App Store / Play Store release. Waslni uses Expo Updates for this. Minutes from commit to user device.

P3 terms

Peak hour: A configurable time window during which fares are multiplied by a surge factor. Distinct from dynamic pricing (live supply/demand). Waslni supports multiple peak windows per day per service type.
Permission registry: A central definition of every fine-grained admin capability (e.g. "fares.edit", "drivers.suspend"). Roles are built by selecting permissions from the registry. Underpins Waslni's role-based access control.
Promo code: A short alphanumeric code a rider redeems for a fare discount or credit. Admin-configurable per city, service type, and per-rider-uses cap.

R3 terms

Referral: A program rewarding existing users for inviting new ones. Typically dual-sided: both inviter and invitee receive a credit. Waslni's referral engine is admin-configurable and is the cheapest acquisition channel most operators have.
Rider: The passenger booking and taking the ride. Synonyms: 'passenger', 'customer'. Distinct from the operator (running the business) and the driver (providing the service).
RTL: 'Right-to-left' — the writing direction of Arabic and Hebrew. A first-class concern in MENA ride-hailing UX. Verifying RTL across every screen, including admin panels and receipt PDFs, is what separates real Arabic support from a translation file.

S4 terms

Service type: A vehicle class with its own fare formula, seat count, and vehicle requirements (e.g. sedan, taxi, van, motorcycle, premium, ladies-only). Admin-configurable in Waslni.
SOS: An in-app emergency button visible to both riders and drivers. Calls the local emergency number and pushes a notification to the operator's response team. Required by some MENA regulators.
STC Pay: A digital wallet operated by Saudi Telecom Company, widely used in Saudi Arabia, especially among younger consumers. Ride-hailing apps targeting Saudi customers benefit from supporting STC Pay alongside cards.
Surge: A fare multiplier applied during high-demand periods to balance supply and demand. May be time-based (peak hour) or dynamic (live supply/demand). Surge transparency on the rider quote is a regulatory requirement in several markets.

T2 terms

Tenant: A platform-level brand container in multi-tenant architecture. Each tenant has its own database, configuration, branding, payment gateway credentials, and admin users. Waslni runs each operator as one tenant.
TGA: Transport General Authority — Saudi Arabia's transport regulator. Sets driver licensing rules, fare disclosure requirements, and operator-level reporting obligations for ride-hailing services in the Kingdom.

U2 terms

Uber clone: A category of one-time-licensed codebases marketed as ready-made Uber-style apps. Generally considered an anti-pattern: the clone is delivered as source code, the buyer becomes the maintainer, and ride-hailing maintenance is a full-time engineering function. White-label platforms like Waslni are the hosted alternative.
Utilisation: The share of online time a driver spends on a fare (rather than idle or repositioning). A primary driver-economics metric — high utilisation makes drivers happy, low utilisation makes them quit. Heatmaps and smart dispatch are tools for raising it.

V1 term

VAT: Value-added tax. Most MENA jurisdictions require VAT on ride-hailing fares, with operator obligations for collection and filing. Waslni's finance reports break out VAT per service type and city to simplify monthly returns.

W3 terms

Wait fee: A per-minute fee charged once a driver has arrived and is waiting for the rider beyond a configurable grace period. Compensates the driver for time spent stationary.
Web booking: A web-based booking interface for riders who do not have or prefer not to use the mobile app. Useful for hotel concierges, corporate accounts, and call-centre bookings. Bookings created on web flow through the same dispatch as in-app bookings.
White-label: A platform sold under the buyer's brand rather than the vendor's. In ride-hailing, true white-label means the rider and driver apps are published in the App Store and Google Play under the operator's developer accounts, with the operator's name, logo, and bundle ID. The vendor name is not visible to end users.

Keep reading

Pillar