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

> allow the merchant to tell the payment app that the payment has been processed

You are making an implicit assumption that it will be possible for the user agent to pass a message back to the payment app after the payment app has responded to the initial payment request. I don't think we can make this assumption unless we get some clarity on how payment apps (and the interface between them and the user agent) will be implemented.

Up to now the assumption has been that the request passed to the payment app and response is a one off to avoid complex UI and state management. 

I proposed a possible solution to this but the consensus seemed to be that this was not necessary as a standard at this time due to a lack of use cases to justify it [1] however I think that this and a few other open issues suggest it's worth looking at again [2].

 1. https://github.com/w3c/webpayments/issues/76     
 1. https://github.com/w3c/browser-payment-api/issues/109

---
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-203886794