Launch in Qatar

A ride-hailing service
for Doha and beyond
configured around your operation.

Configure QAR pricing, Arabic and English, operating zones, service types, and the registration fields your local team requires. Payment providers are connected only after the operator obtains an approved merchant account.

48
Supported interface languages, including Arabic and English
QAR
Configurable local currency and fare rules
App Experience
Rides, delivery and shops, or both
4 steps
Configuration, validation, pilot, and release
48
Supported interface languages, including Arabic and English
QAR
Configurable local currency and fare rules
App Experience
Rides, delivery and shops, or both
4 steps
Configuration, validation, pilot, and release
Last updated · May 20267 min readQatar · GCC

Qatar combines concentrated urban travel with airport, hotel, business, and event demand. A launch still requires a clear approved service model, enough drivers, suitable support coverage, and tested operating rules.

Doha combines a diverse rider base with concentrated travel demand around business districts, hotels, airports, and major events. A focused operator still needs an approved service model, clear pickup rules, tested support procedures, and payment methods that its own merchant account can accept.

Waslni can be configured with QAR pricing, supported interface languages, operating zones, service types, and an admin-composed registration flow. Riders and drivers use one role-aware app, authorised staff get quick administration inside it, and the full web dashboard controls the operation. App Experience can show rides, delivery and shops, or both. Payment providers and any airport-specific workflow require separate approval, scope, and testing.

Configured for Qatar

What is preset
for the Qatari market

01

Configurable payment options

Waslni can be connected to supported card or wallet providers available to the operator. The merchant account must be approved separately, and the operator decides whether to offer card, cash, or the optional in-app wallet.

02

Configurable driver registration

Admins define registration sections, fields, and supporting documents by service type. The operator and its Qatari advisers decide which licences, checks, and records are required.

03

Configurable operating zones

Define Doha, Lusail, Al Wakrah, or another approved area as a geofence with its own pricing and operating rules. Airport access rules must be confirmed with the relevant authority.

04

Language defaults for your audience

Choose from the supported interface languages, including English and Arabic with RTL, across the unified app, in-app administration, and the web dashboard.

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

01 /
Step 1

Brand and Qatar settings

Apply the brand, set QAR, choose languages, define approved operating zones, and select the initial App Experience.

02 /
Step 2

Services and registration

Configure service types, fares, operating rules, and 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 payment, refund, and settlement flow.

04 /
Step 4

Controlled pilot

Submit the app for store review, start in an approved limited area, and validate dispatch, support, and finance before expansion.

Qatar-specific

Plain answers
for Doha operators

01 /

Can I configure Waslni for Qatar?

Yes. Configure QAR pricing, Arabic and English, operating zones, service types, registration fields, and supported payment integrations. The operator must still secure local licences and approved merchant accounts.

02 /

Do I need a Qatari commercial registration?

The operator must confirm company, transport, app-store, and merchant-account requirements with qualified Qatari advisers. Waslni supplies configurable software and does not issue licences or approvals.

03 /

Which payment provider can I use?

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

04 /

Is the Hamad International Airport pickup workflow supported?

A basic airport service area and fare can be configured. Do not assume a holding queue, FIFO assignment, flight-data link, or automatic access-fee logic; each requires airport approval, a defined scope, and testing.

05 /

Can the platform handle high-demand events?

Operators can configure service areas, capacity, peak windows, and support procedures. Event access rules, temporary pickup zones, pricing restrictions, and integrations must be confirmed for the event and local authority.

Start in Qatar

Review the Qatar setup,
before defining launch scope

Explore QAR pricing, language defaults, the unified app, in-app administration, the full web dashboard, and App Experience settings.

Launch a ride-hailing service in Qatar — Waslni