Better handling for failed or aborted checkouts

[multinet-pmerk]

When a checkout is aborted or 3D secure is failed the users ends up back on the booking form with all fields already filled out.

If the user wants to go to the checkout again he must click Book again and if this is done within 15 minutes of the first booking it won't work and users gets a message that he is already booked on the course.

This is really confusing for the user, either they give up or they think that they have booked the course.

We need to come up with a way to check if the booking already created is "Paid": false, and has "PaymentMethodId": 2, we either remove it and create a new booking or we simply use it and go to the checkout again (if the user has Card payment selected for the 2nd booking).

[itssimple]

This plugin doesn't know anything about any bookings made through any payment plugins, as the payment plugins handle all that interaction.

The duplicate booking control is made in the API, so we don't check it ourselves, it's made automatically when we try to book.

And to be able to handle aborted bookings/failed bookings, we'd need to extend the amount of events that the plugin can handle, and add settings in the backend, to either allow removal of bookings that are marked as aborted/failed.

And when those events are available in the main plugin (this one), we would have to update all payment plugins, to support this new event.

So it's not a quickfix, but it can be done.