Airport ride-hailing is its own discipline: FIFO holding queues, terminal-specific pickup zones, per-airport fare rules, flight-aware scheduling, and audit logs the airport authority will actually read. Waslni ships all of it.
Airport ride-hailing looks like a sub-vertical of regular ride-hailing. Operators who have run it know it is its own discipline. The rules are different, the dispatch is different, the regulators are different, and the trip economics are different. A platform that ships an "airport mode" toggle as an afterthought rarely makes it past the first airport-authority audit.
The actual airport requirements are mundane and unforgiving. FIFO holding queue with strict ordering. Pickup zones per terminal and per arrival level. Distinct fare rules including airport access fees and tolls. Audit logs of every pickup with timestamp, terminal, driver, and rider — exportable in the format the airport authority asks for. Corporate-account workflows for the hotels and airlines that book at scale. Flight-status awareness for scheduled pickups when the inbound flight is delayed.
Waslni's platform supports all of this as first-class concerns, not bolt-ons. Multi-airport tenants, terminal- specific geofences, per-airport fare formulas, B2B invoicing for hotel partners, and audit-log exports in the format airport authorities accept. Four weeks gets you from kickoff to apps in the stores under your brand, with the airport tooling configured for your specific facility.
Driver enters the airport holding-area geofence, app puts them in the queue automatically. When a rider books from the terminal, the next driver in queue gets the trip. No favouritism, no manual reassignment unless an operator intervenes.
Each airport terminal (and each arrival level inside it) is a separate pickup geofence. The rider app shows the right pickup point based on the airport you are arriving at; the driver app navigates there.
Airport access fees, special tolls, and base-fare uplift handled per airport. Each airport can have a distinct fare formula configured from the admin panel.
For corporate accounts and scheduled rides, the system can integrate with a flight-status API to adjust pickup timing automatically when flights are delayed.
Hotels and corporate clients book through a dedicated web-booking flow or via the operator console. Monthly invoicing with cost-centre tagging on receipts.
Most airports require ride-hailing operators to maintain audit logs of every pickup, including timestamp, terminal, driver, and rider. Waslni's trip audit log exports satisfy this out of the box.
Drivers entering the airport holding-area geofence are automatically added to the queue. When a rider books a trip from the airport, the next driver in queue is assigned. Drivers see their queue position in the driver app. Operators can manually adjust the queue from the dispatch console when needed.
Yes. Each airport (and each terminal within it) is a separate geofence with its own pickup zone, holding-area, and fare rules. One tenant can run multi-airport operations across multiple cities.
It can. For corporate accounts and scheduled pickups, integrating a flight-status feed lets the system automatically delay or accelerate driver dispatch based on flight ETA. The integration is per-tenant configurable.
Per-airport access fees are configured as a fare-component in the airport service type. They appear on the rider receipt as a separate line item and pass through to the airport authority through your normal settlement.
Same platform fee structure as the rest of Waslni. Airport-specific features (FIFO queue, terminal geofencing, flight-status integration) are included in the standard tenant; corporate-account features are part of the standard admin panel.
14 days free. FIFO queue, terminal pickup zones, per-airport fares. No card required.