Feature #30547
Updated by Amala Raju 5 months ago
*B2C Reissue Workflow* 1. The user logs in and navigates to the My Booking section. 2. They select the required transaction that needs to be reissued. 3. After selecting the booking, the system initiates the reissue flow based on the user’s updated travel requirement allowing the user to: * Add ancillaries * Choose the relevant flight segment 4. The user is redirected to the Payment Gateway to pay the applicable fare difference and charges. 5. Once the payment is successfully completed, the reissue is processed and the updated ticket is issued to the customer. *B2B Reissue Workflow* 1. After login, the B2B user can access the Aftersales section available on the main dashboard. 2. Upon clicking Aftersales, the user is directed to a page similar to TQR, where they can retrieve the booking using multiple filters such as: * Branch * Agency * user * Booking ID * PNR or Ticket Number * Passenger Last Name / First Name 3. Once the required transaction is selected, the user can: * Add ancillaries (if required), or * Choose the relevant flight segment for reissue. 4. The system processes the reissue amount and provides an option to generate a direct payment link for the customer. 5. This payment link is shared with the traveler to collect the due amount. * Note: Payment through the payment gateway is not available at this stage for the B2B user. * Since fares may fluctuate, the B2B agent cannot wait for the customer to complete the payment. * Therefore, once the payment link is generated and sent, the reissue request workflow is considered complete on the agent’s side. 6. In this scenario, the email passed to the airline for ticket issuance will use the agency or in-house email, as certain airlines directly send the updated ticket copy to the email provided. 7. In the admin panel, the transaction status will be updated to “Reissue – Payment Done” when the user pays the due amount. 8. When the customer completes the payment through the link, the admin will manually ticket the booking, and the updated ticket will be forwarded to the traveler. 9 . If the customer does not complete the payment within the expected time, the system can trigger a handler job to send reminder emails to both the traveler and the admin to notify them about the pending amount. *Design Reference :* https://caxita.co.in/tathkarah-new/after_sale_html/mybook_modifyBook_Inhouse_users.html *- inhouse user* https://caxita.co.in/tathkarah-new/after_sale_html/mybook_modifyBook_Agency_users.html *- Travel Agent* https://caxita.co.in/tathkarah-new/after_sale_html/mybook_modifyBook.html *- Guest user* https://caxita.co.in/tathkarah-new/after_sale_html/after_sale_summary_details.html https://caxita.co.in/tathkarah-new/after_sale_html/after_sale_result.html https://caxita.co.in/tathkarah-new/after_sale_html/after_sale_pax.html https://caxita.co.in/tathkarah-new/after_sale_html/after_sale_payment.html *- B2B* https://caxita.co.in/tathkarah-new/after_sale_html/after_sale_PG_payment.html *-Guest* *