Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17)

> I'd expect that depends upon the nature of the payment app. 

Not sure what you're referring to with this statement.

> I'd expect a web based payment app cannot do this for the same reason it cannot really do it now.

I disagree. This cannot be done today because there is not payment app representing the user in this exchange. The whole technology stack is provided by the merchant and the user simply provides credentials into a UI they must trust (provided by the merchant, directly or via their PSP).

The only exception is "wallet" services like PayPal or MasterPass but the fact that the interaction between these and the merchant are not standardized means the merchant must offer a plethroa of payment options and different flows to support each payment method they consider worthwhile.

Today this results in a terrible user experience. This API should move this "match-making" and payment pre-negotiation out of the UI so that the UX is far cleaner and it's possible to introduce payment methods with complex interactions (like encrypted credentials) that are hidden from the user.

---
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/browser-payment-api/issues/17#issuecomment-203917063