Iraq is a custom country enablement, not a preset Waslni market. Confirm IQD settings, Arabic and required Kurdish content, payment feasibility, operating areas, and local approvals before committing to a pilot.
Iraq includes distinct operating conditions in Baghdad, Basra, Erbil, and other cities. The operator should validate demand, driver supply, connectivity, support, licensing, and payment availability for each area.
An Iraq launch needs clear payment and operating rules for each region. The operator chooses cash, wallet, or another supported method according to its approved merchant accounts, contracts, and accounting process, then tests the complete flow before release.
Waslni can be configured with IQD pricing, supported languages, operating areas, service types, and dynamic registration. 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.
Cash and the in-app wallet can be evaluated, but no Iraq-specific online gateway is promised. Provider coverage, merchant eligibility, settlement, refunds, and support must be confirmed before implementation.
Admins define the sections, fields, and supporting documents required for each service type. The operator’s local legal advisers determine the official requirements in its operating region.
Define approved areas in Baghdad, Basra, Erbil, or elsewhere with separate pricing and operating rules. Legal and commercial requirements must be confirmed for every region.
Eight interface languages are bundled, including Arabic with RTL. Confirm which Kurdish locale and translated content the operation needs; do not assume it is included.
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 IQD, 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 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.
Potentially, through a custom country enablement. IQD defaults, required locales, payment feasibility, operating areas, local licences, and testing must be confirmed before the project is treated as launch-ready.
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.
Separate operating areas, languages, registration fields, and business rules can be configured. The operator must confirm licensing, merchant accounts, data handling, and legal structure for each region.
Operating areas and fares are configurable, but demand, driver supply, licensing, support coverage, and unit economics must be validated for each city.
The platform records trips, commissions, and wallet movements. The operator defines its own settlement destination and schedule based on provider support, driver contracts, and local accounting requirements.
Explore IQD pricing, languages, the unified app, in-app administration, the full web dashboard, and App Experience.