The need initiating this Best Practise was found in the "Movingo" collaboration.
In order for a transport authority to enable refresh of its travellers’ tickets sold in a 3rd part sales channel, a ticket refresh procedure is needed in different cases.
The procedure, implemented in the 3rd parts' sales channel, should be started on a schedule and include all current valid tickets.
Without the procedure, in combination with cacheing of tickets in the sales channel and/or in the ticket bearer, it is not possible to update the format/validity of the tickets during the tickets’ validity period.
If the conditions/validity and/or of technical/functional reasons Transport authorities wants to add informnation to already purchased subtickets this procedure needs to be added.
Subticket regular refresh is done for subtickets that have been successfully purchased and where the parent ticket is still valid.
Monitoring is set up to alert administrators if more than 10 refresh attempts fail during a single nightly process from one participant.
A subticket resale process is started if one subticket purchase fails during the sale of a main ticket (main-MTB).
The logic for subticket resale is as follows:
In case of a successful sale on the retry attempt, the subticket MTB are added to the Movingo ticket parent ticket MTB container and is available for the customer applications.
When a new participant finishes its BoB-implementation and is ready including its subtickets within a ticket collaboration (ex. Movingo - region period tickets) a resale/recreation of the main MTB and creation of the new participants sub-MTB is made.
API endpoints used:
The process for adding a new participant is as follows: