Shift Start
10 min
overview the shift start workflow establishes an authenticated, linked session between the taxi meter and the payment terminal for a specific driver and vehicle until both devices are linked, subsidy scheme processing is not available and the devices operate independently sequence diagram sequencediagram actor driver participant tm as taxi meter participant cc as cabfare connect participant pt as payment terminal driver >>tm logs in on taxi meter tm >>cc post /meter/driver/login (driverid, vehicleplate, taximeterid) cc >>tm 200 ok (mptpdriverdata, subsidystatus) tm >>driver displays subsidy scheme eligibility status driver >>pt logs in on payment terminal pt >>cc post /terminal/driver/login (driverid, terminalid) cc >>pt 200 ok (mptpdriverdata, subsidystatus) driver >>pt selects option to link terminals pt >>cc post /terminal/link/request (driverid, vehicleplate, terminalid) cc >>tm post /link/request (driverid, vehicleplate, subsidystatus) alt taxi meter accepts link request tm >>cc 200 ok (link success) tm >>driver displays subsidy scheme eligibility, enters linked mode cc >>pt post /link/response (link success, subsidystatus) pt >>driver displays subsidy scheme eligibility, enters linked mode else taxi meter rejects link request tm >>cc error (link failure) cc >>pt post /link/response (link failure) pt >>driver displays error, continues in unlinked mode end step by step step 1 — driver logs in on taxi meter the driver logs in on the taxi meter as normal the taxi meter notifies cabfare connect of the login event taxi meter calls post /meter/driver/login required fields taximeterid , driverid , vehicleplate cabfare connect responds with the driver's current subsidy scheme eligibility status ( mptpdriverdata ) the taxi meter displays the driver's subsidy scheme eligibility status on screen if the driver is not eligible, subsidy scheme trip functions are disabled for the shift but standard trips continue normally step 2 — driver logs in on payment terminal the driver logs in on the payment terminal the payment terminal notifies cabfare connect of the login event payment terminal calls post /terminal/driver/login required fields terminalid , driverid optional fields vehicleplate — only provide if the vehicle plate is confirmed and known to the payment terminal, for example with hardware fixed to a specific vehicle cabfare connect responds with the same driver subsidy scheme eligibility status both devices must be logged in before a link request can succeed step 3 — driver initiates device link the driver selects the option to link the terminals on the payment terminal this step may be configured to occur automatically depending on the payment terminal implementation payment terminal calls post /terminal/link/request required fields terminalid , driverid step 4 — cabfare connect forwards link request to taxi meter cabfare connect forwards the link request to the taxi meter cabfare connect calls post /link/request on the taxi meter includes driverid , vehicleplate , driver subsidy scheme eligibility status step 5 — taxi meter responds to link request if the taxi meter accepts the link request taxi meter returns a success response to cabfare connect taxi meter displays the driver's subsidy scheme eligibility status and enters linked mode cabfare connect sends a link success response to the payment terminal via post /link/response payment terminal enters linked mode and displays the driver's subsidy scheme eligibility status if the taxi meter rejects the link request (for example if the driver is not yet logged in on the taxi meter) taxi meter returns an error response to cabfare connect cabfare connect sends a link failure response to the payment terminal via post /link/response payment terminal displays an error and continues in unlinked mode step 6 — linked session established once both devices have confirmed linked mode, the session is active the following payment types are now available for the duration of the shift subsidy scheme trips — where a passenger subsidy card is validated and the subsidy is processed by cabfare connect, with the remaining balance collected by card, cash, or other method standard card payment trips — where the full fare is collected by the payment terminal with no subsidy scheme processing cash and other payment trips — where the payment terminal is not involved in the payment if the devices do not successfully link, both devices continue to operate independently in unlinked mode standard trips and cash payments remain available but subsidy scheme processing is not available key points the driver must be logged in on the taxi meter before the link request is initiated on the payment terminal vehicleplate is optional at payment terminal login and link request — refer to the review note in step 3 subsidy scheme eligibility is checked by cabfare connect at login and communicated to both devices if linking fails, both devices continue in unlinked mode — the shift is not blocked