Can I configure Waslni for Jordan?
Yes. Configure JOD pricing, Arabic and English, cities, service types, registration fields, and supported payment integrations. Local licences and merchant approval remain the operator’s responsibility.
Configure JOD pricing, Arabic-first journeys, approved operating areas, service types, and registration fields. Select App Experience and connect a supported payment provider after merchant approval.
Jordan combines dense capital-city travel with different operating conditions in Zarqa, Irbid, Aqaba, and other cities. Coverage, driver supply, pricing, and support should be validated city by city rather than assumed from one national plan.
A Jordan launch needs pricing that reflects local operating costs, clear city coverage, a driver-registration policy, reliable support, and payment methods available to the operator’s approved merchant account. Those choices should be validated before a wider release.
Waslni can be configured with JOD pricing, supported languages, multiple cities, service types, and an admin-composed registration flow. 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.
Waslni can connect to supported card or wallet providers available to the operator after merchant approval. The operator chooses which methods to offer, including cash or the optional in-app wallet.
Admins compose registration sections, fields, and supporting documents by service type. The operator and its Jordanian legal advisers determine the official requirements.
Define approved areas in Amman, Zarqa, Irbid, or elsewhere with separate pricing and rules. Airport-specific workflows require separate approval and testing.
Choose from the supported interface languages, including Arabic with RTL 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 JOD, 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. Configure JOD pricing, Arabic and English, cities, service types, registration fields, and supported payment integrations. Local licences and merchant approval remain the operator’s responsibility.
Choose a provider that supports your Jordanian entity, required methods, and settlement model. Waslni confirms technical support after merchant approval and testing.
Operating areas and fares are configurable, but demand, driver supply, licensing, support coverage, and unit economics must be validated for each city.
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.
Waslni provides configurable registration fields, roles, trip records, and operational exports. The operator and its Jordanian legal advisers remain responsible for confirming licences, documents, and regulator-specific procedures.
Explore JOD pricing, languages, the unified app, in-app administration, the full web dashboard, and App Experience.