Configure AED pricing, Arabic and English, emirate-specific operating areas, service types, and driver-registration fields. Supported payment providers are connected after the operator obtains the required approvals.
UAE customers expect a reliable bilingual service, while each emirate may have different operating and approval requirements. The operator should validate documents, service areas, pricing, support, and payments before release.
That makes preparation more important than a launch-date promise. Operators need clear service areas, tested pricing, suitable registration fields, support procedures, and locally approved payment methods before opening the service to customers.
Waslni can be configured with AED pricing, Arabic and English, multiple operating areas, service types, and an admin-composed registration flow. Supported payment providers are connected only after merchant approval; licensing remains with the operator and its local advisers.
Connect Checkout.com after the UAE merchant account is approved and tested. Cash and the optional in-app wallet can be configured separately.
Admins define registration sections, fields, and supporting documents by service type, then review submissions from the web dashboard. The operator’s UAE legal team determines the official requirements for each emirate.
Define approved areas in Dubai, Abu Dhabi, Sharjah, Ajman, Ras Al Khaimah, or elsewhere with distinct fare and dispatch rules. Confirm eligibility before enabling each area.
Choose the tenant-visible languages your audience needs, including English and Arabic with RTL, across the role-aware app and administration surfaces.
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.
Permission-aware admin tools let authorised team members handle urgent approvals, live operations, and support checks without switching to another app.
Manage dispatch, users, service types, pricing, payment options, documents, roles, reports, shops, and content from the main web dashboard.
Apply the brand, set AED, choose languages, define operating areas, and select the initial App Experience.
Configure service types, fares, operating rules, and registration fields approved by the operator’s local advisers.
Connect a supported provider after merchant approval and test every enabled payment, refund, and settlement flow.
Submit the app for store review, start with a limited operating area, and validate dispatch, support, and finance before expansion.
Yes. Configure AED pricing, Arabic and English, operating areas, service types, registration fields, and supported payment integrations. The operator remains responsible for trade and transport licences and approved merchant accounts.
The operator must confirm trade, transport, data, insurance, and app-store requirements for each emirate with qualified local advisers. Waslni supplies configurable software and does not certify regulatory compliance.
The mobile app uses phone OTP by default. UAE-PASS is not presented as an automatically active feature: if an operator requires it, scope, approvals, and technical integration must be confirmed as a separate implementation.
The operator can configure service types, fares, eligibility fields, and visible content. Any assignment rule, local restriction, or approval must be confirmed and tested for the launch scope.
Do not assume automatic toll detection. A toll workflow needs a confirmed data source, fare rule, reconciliation method, and tests; otherwise the operator can manage an approved surcharge through its configured pricing rules.
SAR pricing, Arabic operations, configurable services, and approved integrations.
EGP pricing, Arabic operations, configurable services, and approved integrations.
Careem was UAE-founded; here is the platform side of that pattern.
Explore AED pricing, language defaults, the unified app, in-app administration, the full web dashboard, and App Experience settings.