Re: [w3c/webpayments] Overview document figure 5 (#171)

As I recall, there may be some reason for a "complete" message because of Apple Pay... but I'll let someone more knowledgeable about that respond if that's the case.

My thoughts are:

Shouldn't the mediator just pass the payment response right through to merchant site and close? If the payment fails, the flow can't be easily recovered, right? Doesn't the merchant site have to start a new flow? If they don't have to start a new flow, doesn't the merchant site need to communicate something that passes through the mediator to the user to tell them what to do next?

It seems to me that the user experience be better if you don't have to see an error message in the mediator, close that, and then also see an error message at the merchant site directing you as to what to do next. It also seems better for control to simply go back to the merchant site so they can customize how to direct the user's next step. That way we can remove any need for designing something to allow the merchant site to communicate error information back to the mediator that the user can act on -- and specifying how the mediator is to present choices to the user based on that information. This also means there would be fewer decisions merchant sites need to make to figure out whether they should keep the mediator UI open based on the type of error that occurred.

On the other hand, the user experience in the case of a rejected card, for example, would be pretty frustrating. I would go through the checkout process, select my shipping address, etc., open a payment app, select a card to pay with -- and then the payment would fail and I'd have to start over. Ideally, I'd only have to choose another payment app and card again.

So, given that a design choice to integrate checkout choices like shipping address into the mediator has been made (as opposed to keeping them on the merchant site), it makes sense to have this added complexity.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/171#issuecomment-238941272