Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Allow for handling different cancellation options #545

Open
matt-wirtz opened this issue May 8, 2024 · 0 comments
Open
Milestone

Comments

@matt-wirtz
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Services with time slot reservation options or fixed price services usually have cancellation options where additional fees are applied. E.g. when booking a shared car for some time next week that booking can be canceled until the booking time has been reached. But when cancelling some charges are applied. Or if a booked DRT service is cancelled usually additional fees are applied. Some TOs offer different cancellation options like either a voucher or a refund.

Currently an extensive provision of cancellation options is not supported by TOMP.

Urgency

Major (the TOMP API works as advertised but this is really neccessary to implement), because the use case of cancelling a trip/booking is quite common for services with time slot reservation options or fixed price services.

Describe the solution you'd like

There should be two use cases:

  • TO provides possible cancellation options and the MP cancels the trip/booking by specifying one option.
  • The MP cancels the trip/booking directly without requesting cancellation options. If multiple options do exists the TO decides which one is chosen.

Possible Implementation

When the cancel operation is triggered the MP can opt to set "requestCancellationOffers": true. In this case the TO provides an array of cancellationOptions. That object holds e.g. the price, info text and an cancellationOptionId. Based on this the MP can trigger the cancellation by providing "requestCancellationOffers": false and "cancellationOfferId": 2.
If the MP triggers a cancellation with "requestCancellationOffers": false and doesn't provide a cancellationOfferId the TO decides which option to use.

@edwinvandenbelt edwinvandenbelt moved this to To do in WT1 Kanban Jun 5, 2024
@edwinvandenbelt edwinvandenbelt added this to the 2.0 milestone Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To do
Status: In review
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants