Feature Request: Retain or replicate cart for failed payments

[mitchell-amasia]

Issue Template

Deployment
My deployment is on:

• [x ] Azure

Expected behaviour
When a customer unsuccessfully completes a checkout process, like a failed or cancelled payment, the cart still exists so that the customer can attempt to complete the checkout successfully again.

Cancel the order if payment was unsuccessful and use the replicate endpoint of Commercetools to create a new cart with the same items in it.
https://docs.commercetools.com/api/projects/carts#replicate-an-existing-cart-or-order-to-a-new-cart

Actual behaviour
An order is created when a user proceeds to the Mollie hosted checkout. This results in the cart's cartState field being set to ordered.
When the payment fails or is cancelled, the customer returns to the e-commerce platform, but the cart is "gone" from the customers perspective. They would have to add items again to a new cart to continue.

[denisand]

Extension and notification modules only update transactions and payments on commercetools side. It seems that something else is creating order from cart and causing this. Ideally, "create order" (or not) action would follow once returned from Mollie hosted checkout, based on the response.

Does this happen when used with a frontend?

[mitchell-amasia]

It's not very clear where this is happening. We're using the vsf-mollie integration, in which a "createOrder" is called.
It creates an order in Mollie but it also appears to create an order in Commercetools, based on the cart. And this happens right before the user is redirected to Mollie's hosted checkout.

[denisand]

@mitchell-amasia is this still the issue? If not - can we close it?