Shift End

overview the shift end workflow closes the driver's shift and unlinks the taxi meter and payment terminal the taxi meter initiates the shift end by logging the driver out cabfare connect notifies the linked payment terminal to unlink and sends all required shift data to the subsidy provider if the driver logs out of the payment terminal first, cabfare connect notifies the taxi meter, which must then determine whether to also log the driver out or continue in unlinked mode sequence diagram sequencediagram actor driver participant tm as taxi meter participant cc as cabfare connect participant pt as payment terminal alt driver logs out of taxi meter first driver >>tm logs out of taxi meter alt taxi meter printer configured tm >>driver prints end of shift report end tm >>cc post /meter/driver/logout (taximeterid, driverid, shiftdata) cc >>tm 200 ok or 204 no content cc >>pt post /driver/logout (driverid) pt >>driver unlinks from taxi meter, logs driver out if configured cc >>cc sends shift data to subsidy provider else driver logs out of payment terminal first driver >>pt logs out of payment terminal pt >>cc post /terminal/driver/logout (terminalid, driverid) cc >>pt 200 ok or 204 no content cc >>tm post /driver/logout (driverid) tm >>driver notified of payment terminal logout note over tm taxi meter determines whether to log out or continue in unlinked mode end step by step step 1 — driver logs out of taxi meter this is the standard end of shift process the driver logs out of the taxi meter the specific action may vary by implementation — for example a dedicated end shift button or a logout option in the menu if the system is configured with a taxi meter printer the taxi meter prints an end of shift report before sending the logout notification to cabfare connect taxi meter calls post /meter/driver/logout required fields taximeterid , driverid , shift end data the shift end data must include all required information for subsidy provider reporting if any subsidy scheme trips were processed during the shift this data must always be included regardless of when or how the shift ends step 2 — cabfare connect processes shift end cabfare connect receives the logout notification and ends the shift session sends a logout notification to the linked payment terminal sends all required shift data to the subsidy provider cabfare connect calls post /driver/logout on the payment terminal the payment terminal receives the notification, unlinks from the taxi meter, and logs the driver out if configured to do so step 3 — alternative driver logs out of payment terminal first if the driver logs out of the payment terminal before the taxi meter the payment terminal notifies cabfare connect payment terminal calls post /terminal/driver/logout required fields terminalid , driverid cabfare connect sends a logout notification to the linked taxi meter cabfare connect calls post /driver/logout on the taxi meter it is then up to the taxi meter provider to determine whether this also logs the driver out of the taxi meter or whether the taxi meter continues operating in unlinked mode regardless of when the driver logs out of the taxi meter, the taxi meter must always send cabfare connect the required shift end data if any subsidy scheme trips were processed during the shift step 4 — shift data submitted to subsidy provider cabfare connect sends all required shift information to the subsidy provider once the taxi meter logout is complete this includes all trip data, subsidy payments, and lifting fees processed during the shift key points the taxi meter must always send shift end data to cabfare connect if any subsidy scheme trips were processed during the shift — this is required regardless of the logout sequence a taxi meter logout automatically triggers a logout notification to the linked payment terminal via cabfare connect if the driver logs out of the payment terminal first, the taxi meter determines whether to also log out or continue in unlinked mode all subsidy provider reporting is handled by cabfare connect — integration partners do not submit data directly to the subsidy provider the shift is not considered closed until post /meter/driver/logout has been successfully received by cabfare connect