The ride lifecycle
From request to payout: who does what at each step and where it is visible.
A ride goes through the same steps regardless of the channel. Each step has a role, a screen and a record — that is why the numbers in the apps, console and settlement agree.
| Step | Who | Where | What happens |
|---|---|---|---|
| 1. Request | Passenger / operator | Passenger app | Pickup, destination and service type |
| 2. Price | Server | Prices and zones | Maximum price by the company price list |
| 3. Assignment | Dispatcher / system | Dispatch board | Ride goes to a driver by radius or manually |
| 4. Accept | Driver | Driver app | Timed offer and acceptance |
| 5. Arrival | Driver | Driver app | Navigation, contact and arrival |
| 6. Ride | Driver and passenger | Both apps | Route, time and ride sharing |
| 7. Completion | Driver | Driver app | Amount and payment method |
| 8. Receipt | System | Fiscalisation | Fiscal receipt, PDF and email |
| 9. Rating | Passenger | Passenger app | Driver rating without affecting the price |
| 10. Settlement | Accounting | Settlement | Revenue, commission and balance |
| 11. Payout | Accounting | Money | Driver payout and a record |
One record for everyonePassenger, driver, dispatcher and accounting look at the same ride — there is no separate adding up and no “second spreadsheet”.