01 /
Can the app be configured specifically for Egypt?
Yes. The operator can set EGP, Arabic RTL content, cities and service areas, vehicle categories, pricing, registration forms, payment options, and the App Experience for its Egyptian deployment.
Launch in Egypt
A ride-hailing service
for Cairo and beyond
under your brand.
Waslni gives an Egyptian operator one branded mobile app for riders and drivers, quick permission-aware administration inside the app, and a full web panel. Configure App Experience for rides, shops and delivery, or both.
1
Unified mobile app for rider and driver roles
3
Connected surfaces: mobile app, in-app admin, and web admin
EGP
Currency and pricing rules configured for Egypt
48
Supported languages, including Arabic RTL
Last updated · July 20268 min readEgypt · MENA
Launching in Egypt is an operating project, not just an app release. You need a clear service area, suitable vehicle categories, pricing that reflects local costs, a driver onboarding policy, support processes, and payment methods your customers can actually use.
Waslni keeps the product side simpler. The rider and driver use one mobile app, with each account seeing the tools that match its role. Authorized staff can handle quick operational tasks inside the same app, while the full web panel covers configuration, approvals, shops, pricing, permissions, and reporting.
For an Egyptian deployment, the operator can set EGP pricing, Arabic RTL content, cities and service polygons, service types, peak periods, registration fields, and supported payment integrations. The operator selects its merchant providers and remains responsible for local licences and regulatory requirements.
Configured for Egypt
What is preset
for the Egyptian market
These settings let the operator adapt the platform to its real business model without hard-coding Egypt-specific rules into the app.
01
Payments configured around your operation
Waslni supports integration paths for Fawry, Kashier, Paymob, and Lahza. Your team chooses which methods to offer, connects its approved merchant accounts, and may keep cash or the in-app wallet optional.
02
Arabic-first product experience
Right-to-left layouts cover the unified mobile app, in-app admin tools, and the web dashboard. Operators can maintain Arabic and English customer-facing copy from one operation.
03
Multi-city Egypt out of the box
Cairo, Alexandria, Giza, Mansoura, Tanta — define each as a city geofence with its own pricing rules. The same tenant runs them all.
04
Configurable driver registration
Admins compose the required sections, documents, and fields for each service type, then review submissions from the web dashboard. Your local legal team decides the requirements that apply in Egypt.
What ships
Three connected surfaces.
One operation.
Mobile app
One download for riders and drivers
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.
Mobile admin
Quick control inside the app
Permission-aware admin tools let authorised team members handle urgent approvals, live operations, and support checks without switching to another app.
Web admin
Full control from the browser
Manage dispatch, users, service types, pricing, payment options, documents, roles, reports, shops, and content from the main web dashboard.
Launch sequence
From configuration
to a controlled pilot
01 /
Step 1
Brand and Egyptian settings
Apply the brand, set EGP, choose content languages, define launch cities and polygons, and select the initial App Experience.
02 /
Step 2
Service types, pricing, and onboarding
Configure vehicle categories, fixed or calculated fares, peak rules, commissions, and the registration fields required by the operator.
03 /
Step 3
Payments and operating rules
Connect a supported provider after merchant approval, decide whether cash and wallet are enabled, and test each payment, refund, and settlement flow.
04 /
Step 4
Controlled pilot in Egypt
Submit the app to stores, onboard a limited initial group, and validate dispatch, customer support, cancellations, and exception handling before expanding.
Egypt-specific questions
Plain answers
before you launch
02 /
How does cash work?
When cash is enabled, the app records the trip or order value and the driver’s collected amount so the operator can reconcile balances and commissions. The exact settlement policy is set by the operator.
03 /
Which payment gateway should I use in Egypt?
Waslni includes integration paths for Fawry, Kashier, Paymob, and Lahza. Availability, merchant approval, fees, supported payment methods, and settlement terms vary, so choose and test the provider that fits your legal entity and operating model.
04 /
Can I run Cairo and Alexandria in the same project?
Yes. You can define multiple cities, service areas, and pricing rules in one deployment. If the brands, teams, and accounts are fully separate, discuss provisioning an independent deployment for each business.
05 /
What about licensing and local requirements?
Waslni provides configurable registration fields, permissions, trip records, and operational exports. The operator and its Egyptian legal advisers remain responsible for confirming licences, required documents, payment approvals, and any regulator-specific process before launch.
Keep reading
Geo guide
Launch in Saudi Arabia
Plan SAR pricing, Arabic operations, service areas, onboarding, and locally approved integrations.
Read
Geo guide
Launch in the UAE
AED pricing, bilingual operation, configurable services and integrations.
Read
Sister
Get an app like Careem
The Careem-style angle on the same platform.
Read
Start in Egypt
An Egyptian demo,
built around your operation
Explore the unified rider-and-driver app, permission-aware mobile administration, the full web dashboard, EGP settings, and the App Experience modes for your project.