The UAE is the most regulated, most mature ride-hailing market in the GCC — which is exactly why operators picking the right platform compete with the global brands as equals. Waslni gives you a platform configured for the AED stack and the RTA audit.
The UAE is the most demanding ride-hailing market in the GCC. Customers compare your app against Uber's UAE product, not against a forgiving local benchmark. Regulators expect every driver document on file. Payment failure on a 30 AED ride is the kind of thing that gets shared on Twitter by tomorrow morning.
That sounds intimidating until you realise it is also the reason operators with the right platform can win quickly. UAE customers reward a well-built product immediately and forgive nothing about a bad one. Pick the right platform and you skip a year of "we're working on it"; pick the wrong one and the App Store reviews start writing themselves on day three.
Waslni's platform is configured for the UAE: AED currency by default, bilingual UI with the English-default behaviour that matches local consumer expectation, payment integrations with the acquiring partners UAE merchants actually sign with, and a driver compliance workflow that holds up to RTA-style scrutiny. Multi-emirate dispatch is a configuration decision, not a code branch. Four weeks gets you from kickoff to apps in the UAE App Store under your brand.
Network International, Telr, Checkout.com, Tap Payments — any acquiring partner with a JSON / hosted-page API plugs into the Waslni payment abstraction. Apple Pay and Google Pay on top of cards. Cash supported but rarely needed.
Driver document checklist for the UAE market: Emirates ID, UAE driving license, vehicle Mulkiya, valid Salik tag, vehicle inspection certificate, professional permit where applicable. Expiry alerts and automatic offline-mode on lapse.
Dubai, Abu Dhabi, Sharjah, Ajman, Ras Al Khaimah — each as its own city geofence with separate pricing and peak windows. Same tenant, distinct configurations.
UAE consumers are bilingual; the rider app defaults to English with one-tap switch to Arabic and full RTL. The admin panel works the same way. Pick the default that fits your audience.
Native iOS + Android. AED fare quotes. Saved cards (Network International, Telr, Checkout). Apple Pay + Google Pay. Scheduled rides up to two weeks out. Bilingual.
Smart assignment, navigation, transparent AED earnings, weekly payouts to UAE bank accounts via the acquiring partner or direct WPS where applicable, document upload, demand heatmap.
Multi-emirate dispatch. Role-based permissions. AED finance reports with VAT-ready breakdowns. Content CMS for the policy pages your regulator wants visible.
Tenant with AED default, English-default + Arabic option, your launch emirates as geofences. Brand kit applied.
Service types (sedan, SUV, premium, ladies-only) configured. AED per-km, per-min, base fare. Peak windows for Dubai evening, Friday brunch flows, Abu Dhabi weekday rush.
Network International, Telr, or Checkout.com merchant account activated. Driver document workflow for Emirates ID, UAE license, Mulkiya, etc. 50-driver pilot onboarded.
iOS + Android apps in UAE-locale App Store + Google Play. Soft launch in one emirate; expand once the first 7 days are clean.
Yes. The platform is configured for the UAE market: AED currency, bilingual EN + AR with English-default option, multi-emirate dispatch, payment integrations with Network International, Telr, Checkout.com or Tap Payments, driver document workflow aligned with RTA-style audits. Four-week launch assuming business registration and acquirer accounts are ready.
To operate a ride-hailing service, yes — usually through the relevant emirate's transport authority (RTA in Dubai, ITC in Abu Dhabi, etc.) and the appropriate trade licence. Waslni is your software partner; your local legal team handles the licensing. The platform supports the data exports and audit trail those regulators ask for.
The rider app uses phone-OTP by default, the universally available method. UAE-PASS as an identity provider for high-trust flows (corporate accounts, regulated services) is an integration we run through the standard third-party-auth path used elsewhere in the platform.
Yes. Service types are admin-configurable: define a "Ladies" service with a constraint that the assigned driver is flagged as female-eligible, define "Premium" with its own vehicle-class restriction and higher fare formula. Both run on the same platform from day one.
Salik toll passthrough on fares is a per-trip surcharge handled in the operator console: the system detects the toll-zone crossing and adds the appropriate charge to the rider invoice, settling to the driver wallet. The integration is standard for UAE deployments.
14 days free. AED currency. Bilingual UI with English default. Real apps install on your phone.