National Land Transport Act, 2009 (Act No. 5 of 2009)RegulationsSecond National Land Transport Regulations, 2025Chapter 2: Regulations on Electronic-Hailing Services16. Minimum specifications for an e-hailing platform |
| (1) | An e-hailing platform must have at least the following functionalities for the passenger: |
| (a) | A user must be able to sign up with the e-hailing platform app. |
| (b) | Provision for the creation of a trip request with end destination. |
| (c) | Provision for section of a service including categories where the e-hailing platform management company provides for varying service offerings. |
| (d) | The user must be able to check the price for the ride beforehand. |
| (e) | The app must enable the user to view live billing as the ride is taking place. |
| (f) | The user must be able to interact with the driver after the driver has been allocated to the user. |
| (g) | Provision for push notifications to keep the user up to date with the trip request status, driver arrival time, driver and car details including live tracking of the driver's location from ride acceptance to completion. |
| (h) | The user must be able to contact the driver through the app. |
| (i) | The platform must enable a user to book the ride for another traveller from own account. |
| (j) | Payment must be able to be done automatically after the ride is complete, where the rider is making electronic or card payment. |
| (k) | The user must be able to select a payment method including adding a credit card or debit card beforehand, where it is the user choice of payment. |
| (l) | The user must be able to review the driver when the trip is complete. |
| (m) | Panic buttons must be provided in case of emergency which are connected to relevant private security service providers or vehicle tracking providers appointed by the operator, and are tested regularly, at least once a month to ensure that they are still functional. |
| (n) | Panic buttons contemplated in paragraph (m) must be capable of being accessed and used by passengers as well as by the driver of the vehicle. |
| (2) | The platform must have at least the following functionalities for the driver: |
| (a) | The platform must provide for the driver profile and status which must include the following details: |
| (i) | a photograph of the driver not older than 12 months; |
| (ii) | details of the driver's valid driving licence; |
| (iii) | details of the driver's professional driving permit, including expiry dates, and |
| (iv) | the motor vehicle details including at least make, model, date of first registration in terms of the National Road Traffic Act, registration number and colour. |
| (b) | The driver must be able to receive trip orders to accept or decline, including passenger information regarding the location and destination. |
| (c) | The platform must provide the driver with navigation and route optimisation that offers the best trip route option. |
| (d) | There must be driver delivery reports that provide the driver with daily, weekly, and monthly information regarding trips and earnings, where applicable. |
| (e) | The app may also be capable of charging the user for waiting time starting from a defined parameter as additional cost on top of the base fare. |
| (f) | The app must be able to provide the driver with a heat map that enables the driver to be aware of high demand areas. |