Launch in Saudi Arabia

A ride-hailing service
for the Kingdom
configured around your operation.

Configure SAR pricing, Arabic and English, city zones, service types, and an admin-composed registration flow. Supported payment providers are connected after the operator obtains the necessary approvals.

Riyadh skyline at golden hour with a Waslni-style sedan in the foreground
48
Supported interface languages, including Arabic and English
SAR
Configurable local currency and fare rules
4 steps
Configuration, validation, pilot, and release
Configurable
Registration fields and role-based approvals
Last updated · May 20268 min readSaudi Arabia · MENA

Saudi Arabia combines large cities, varied service areas, and Arabic-first customer expectations. A serious launch still depends on the operator’s approvals, driver supply, support capacity, pricing, and tested payment setup.

The hard part is not demand. It is local fit. A Saudi operator needs Arabic-first customer journeys, SAR pricing, service areas, suitable driver-registration fields, support procedures, and payment methods approved for its own legal entity. The operator and its advisers decide which documents, licences, and checks are required.

Waslni provides the configurable software foundation. The same role-aware mobile app serves riders and drivers, authorised staff can handle quick tasks inside it, and the full web dashboard manages the wider operation. App Experience can present rides, delivery and shops, or both. Payment connections are confirmed only after the operator selects a supported provider and obtains merchant approval.

Configured for Saudi

What is preset
for the Kingdom

The platform is the same one running Palestine and Egypt. The differences are configuration, not code.

01

Configurable payment options

The platform can connect to a supported provider after the operator’s merchant account is approved. The operator chooses which approved methods to offer; cash and the in-app wallet remain optional.

02

Arabic-first product experience

Right-to-left layouts cover the unified mobile app, in-app admin tools, and the web dashboard. Operators can also manage an English experience when their audience requires it.

03

Configurable driver registration

Admins define the sections, documents, and fields required for each service type and review every submission. The operator’s Saudi legal advisers determine the official requirements and approvals.

04

Multi-city out of the box

Riyadh, Jeddah, Dammam, Mecca, Medina — define each as a city geofence with its own pricing rules, peak windows, and dispatch settings. The same tenant runs them all.

What ships

Three connected surfaces.
One operation.

Mobile app

One download for riders and drivers

The same branded iOS and Android app opens the right rider or driver mode after sign-in. Configure it for city rides and parcel delivery, a restaurant and grocery marketplace, or both.

Mobile admin

Quick control inside the app

Permission-aware admin tools let authorised team members handle urgent approvals, live operations, and support checks without switching to another app.

Web admin

Full control from the browser

Manage dispatch, users, service types, pricing, payment options, documents, roles, reports, shops, and content from the main web dashboard.

Launch sequence

From configuration to
a controlled pilot

Each step depends on the operator’s approvals, data readiness, testing, and store review.

01 /
Step 1

Brand and Saudi settings

Apply the brand, set SAR, choose interface languages, define service areas, and select the initial App Experience.

02 /
Step 2

Services and registration

Configure service types, fares, operating rules, and the registration fields approved by the operator’s local advisers.

03 /
Step 3

Payments and validation

Connect a supported provider after merchant approval and test every enabled card, cash, wallet, refund, and settlement flow.

04 /
Step 4

Controlled pilot

Submit the branded app for store review, onboard a pilot group, and validate dispatch, support, and finance before wider release.

Saudi-specific questions

Plain answers
for the Kingdom

01 /

Can I configure Waslni for Saudi Arabia?

Yes. Configure SAR pricing, Arabic and English, cities, service types, registration fields, and supported payment integrations. The operator remains responsible for business registration, transport approvals, and approved merchant accounts.

02 /

Do I need a Saudi-registered company?

Business registration, transport approval, app-store requirements, and merchant-account eligibility depend on the operator and its activities. Confirm them with Saudi legal and payment advisers before launch; Waslni does not issue licences or approvals.

03 /

Which payment provider can I use?

Choose a provider that supports your Saudi legal entity, required payment methods, and settlement model. Waslni confirms technical support only after reviewing the provider, merchant account, and launch scope.

04 /

Is Arabic a primary interface language?

Yes. Arabic uses right-to-left layouts across the role-aware app, in-app administration, and the web dashboard. Review the actual screens and tenant copy during the demo.

05 /

How do you handle Saudi driver registration?

A user can switch from rider mode into the driver-registration flow in the same mobile app. Admins compose the required sections and fields per service type and approve submissions from the web dashboard. Your local team decides which documents and checks are legally required.

Ready when you are

Review the Saudi setup,
before defining launch scope

Explore SAR pricing, Arabic RTL, the unified app, in-app administration, the full web dashboard, and App Experience settings.

Launch a ride-hailing service in Saudi Arabia — Waslni