01
1. Vehicle Discovery
The app requests rentable vehicles from the backend and displays eligible vehicles with their location data.
eeDIGI ENTERPRISE MOBILITY
How the System Works
A shared rental uses several systems at once. Here is what happens from the moment a customer finds a motorcycle until the ride is closed and paid.
RENTAL FLOW
The customer sees a few simple steps while the backend checks the account, vehicle and payment state.
A step that takes seconds in the customer app may involve vehicle eligibility, account status, IoT communication and payment rules behind the scenes.
02
2. Rental Start
Customer and vehicle eligibility are checked. Once requirements are met, a rental record is created and any supported vehicle command is sent.
03
3. Ride & IoT
During an active rental, location and status data from the vehicle can be associated with the ride for operational visibility.
04
4. Rental Completion
Parking and service-zone rules are checked, usage is calculated, payment is completed and the vehicle is returned to an available state.
PLATFORM INTERFACE
WHAT HAPPENS IN THE BACKGROUND?
When something fails, the platform needs a clear record of which step completed and which one did not.
✓Customer verificationAccount, required documents and payment method can be checked before rental according to project rules.
✓Vehicle selectionAvailability is validated server-side to prevent the same vehicle from being assigned to multiple customers.
✓Rental startStart time, vehicle and customer are linked in a single rental record.
✓Location and statusIoT data is matched to the vehicle identity and made available to the operational system.
✓Operations visibilitySupport staff can inspect the active rental and vehicle state from the same record when intervention is required.
✓Rental completionDuration, price, parking rules and payment result are finalized before the rental is closed.
Screens are representative UI presentations. Final feature scope depends on project, vehicle and hardware compatibility.
INTEGRATION POINTS
The mobile app coordinates with several services rather than operating on its own.
During a rental, the mobile app, backend API, payment provider and IoT service each have separate responsibilities. Failure scenarios are designed with that separation in mind.
For example, a payment may succeed while the customer's connection drops, or an IoT device may respond late. Server-side transaction records allow the system to recover to the correct state.
Operational rules vary by project, so the final workflow is confirmed after the vehicle type and field procedures are understood.
DESIGN THE WORKFLOW WITH US
Discuss Your Project →Turn your planned or existing rental process into a clear technical workflow.
Define the customer, payment, vehicle and operations steps before development begins.