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] Add an explicit customer registration process independent from bookings #549

Open
matt-wirtz opened this issue Jun 25, 2024 · 0 comments
Labels
breaking This issue leads to a major version WT2
Milestone

Comments

@matt-wirtz
Copy link
Collaborator

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

Currently the process of customer registration is handled implicitly while creating bookings. This prevents use cases where non trip related purchases like a monthly subscription should be performed. It also prevents pre-booking user registration. Some registration processes take some time - even days - on the TO side to perform all checking. During this time the booking needs to remain in pending state until all checking has been successfully done. That makes it more complicated on MP side to handle and communicate to the user.
Additionally it makes GDPR processes like "where is my data stored" much more complicated.

Urgency

Major (the TOMP API works as advertised but this is really necessary to implement), because non trip related purchases are quite common. Many TOs offer subscriptions that allow e.g. for better time rates when using their service.

Additional context

Describe the solution you'd like

Add an explicit process of customer registration. That is then the basis for adding the capability for subscriptions and other non trip related purchases.

Describe alternatives you've considered

Possible Implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking This issue leads to a major version WT2
Projects
Status: In review
Development

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

2 participants