Configure currency display, Arabic-first journeys, approved operating areas, service types, registration fields, and App Experience. Connect a supported payment provider after merchant approval.
A Palestinian launch needs an Arabic-first customer journey, clear city coverage, suitable registration fields, support procedures, and payment methods available to the operator’s approved merchant account.
Currency display, cash handling, driver documents, inter-city services, and operating areas are business decisions rather than universal presets. The operator and its local advisers define the legal and operational requirements before the pilot.
Waslni provides one role-aware mobile app for riders and drivers, quick administration inside that app for authorised staff, and a full web dashboard. App Experience determines whether customers see rides, delivery and shops, or both.
Configuration is reviewed against the operator’s approvals, data, and tested launch scope.
Connect a supported provider after merchant approval. The operator chooses which approved methods to offer; cash and the in-app wallet remain optional.
Admins define registration sections, fields, and supporting documents by service type. The operator’s Palestinian legal advisers determine the official requirements.
Define approved areas in Ramallah, Nablus, Hebron, Bethlehem, or elsewhere with separate pricing and rules. Inter-city operation requires its own legal and commercial review.
Choose from 48 supported interface languages, including Arabic with RTL, 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, configure currency display and 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 cash, wallet, payment, and settlement flow.
Submit the app for store review and validate dispatch, support, and finance in a limited approved area before expansion.
Yes. Configure currency display, Arabic-first content, operating areas, services, registration fields, and approved payment connections. The operator remains responsible for local licences and merchant approval.
Choose a supported provider and methods available to the operator’s approved merchant account. Confirm fees, settlement, refunds, and technical support before launch.
Currency and receipt requirements must be defined for the operator’s accounting and legal context. Confirm any secondary display, conversion source, rounding rule, and disclosure before enabling it.
Yes. Areas, fares, services, and registration fields are configurable. Connectivity, access, licensing, support coverage, and operational feasibility must be assessed separately for each area.
When cash is enabled, the app records the fare and driver collection. The operator defines reconciliation, wallet funding, and settlement procedures according to its contracts and accounting requirements.
Explore currency settings, Arabic RTL, the unified app, in-app administration, the full web dashboard, and App Experience.