If there was another discussion about this somewhere and I missed it, I apologize. I think it is true that in a closed ecosystem some browsers may have a way to know what payment methods they are managing themselves when they are also acting as a payment app. That's a solved problem. Or if it isn't, I am confident that the browser developers can solve it themselves. I don't think that we have addressed the concern of third party payment apps. In particular on non-mobile platforms. There is no native way to register a payment app on Linux, for example. In a Linux environment, the payment app will be attached to the user agent somehow. Windows on the desktop should have a similar need. I am not against the typical case being seamless. I think that is essential. But as a standards body we can't create a system where it isn't possible for everyone to participate. At least, I don't think we can. --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-payment-apps-api/issues/8#issuecomment-236001907
Received on Thursday, 28 July 2016 19:38:23 UTC