Configure MAD pricing, supported languages, operating areas, services, and registration fields. Choose App Experience and connect a supported payment provider after merchant approval.
Morocco combines distinct city patterns, seasonal travel, and audiences that may use Arabic, French, or English. The operator should validate language defaults, pricing, coverage, and support for each launch area.
Language and payment choice both matter. The operator should choose the interface languages its audience needs, decide whether cash or a wallet fits the operating model, and connect only payment methods available to its approved merchant account.
Waslni supports 48 interface languages, including Arabic, French, and English. One role-aware app serves riders and drivers, authorised staff get quick administration inside it, and the full web dashboard controls the operation. App Experience selects rides, delivery and shops, or both.
The operator can connect a supported card or wallet provider after merchant approval and choose the methods offered at launch. Cash and the optional in-app wallet can be configured separately.
Admins define registration sections, fields, and supporting documents by service type. The operator’s Moroccan legal advisers determine the official requirements.
Define approved areas in Casablanca, Rabat, Marrakech, or elsewhere with separate pricing and operating rules. Airport-specific workflows require separate approval and testing.
Choose the languages your audience needs, including Arabic with RTL, French, and English, across the unified app and both 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 MAD, choose languages, define approved areas, and select App Experience.
Configure service types, fares, operating rules, and locally approved registration fields.
Connect a supported provider after merchant approval and test every enabled payment and settlement flow.
Submit the app for store review and validate dispatch, support, and finance in a limited area before expansion.
Yes. You can configure MAD pricing, language preferences, cities, service types, registration fields, and supported payment integrations. Your local team still needs the relevant licences and approved merchant accounts before going live.
The same mobile app serves riders and drivers and supports the languages enabled for the tenant. The web dashboard and customer-facing copy can also be localised for Arabic, French, or English as the operator requires.
When cash is enabled, the app records the fare and driver collection. The operator defines reconciliation and settlement procedures according to its contracts and accounting requirements.
Operating areas and fares are configurable, but demand, driver supply, licensing, support coverage, and unit economics must be validated for each city.
Languages, service areas, fares, and seasonal rules are configurable. Airport queues, automatic currency conversion, and tourism integrations require separate scope, approval, and testing.
Explore MAD pricing, languages, the unified app, in-app administration, the full web dashboard, and App Experience.