Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112)

Isn't it true that, if origin information is not associated, then the app is installed in the ambient system, and not just the browser extension.  In that scenario, the app should deal with updates through the system, ala apt-get, PlayStore, etc.  If the app is installed in the browser itself, then the browser already supplies hooks for this.  If some browsers handle this badly, like by forcing the app to leak that it's installed, then maybe one should address that directly.

We actually have another sort of scenario :  If you visit an exchange/bank/mint, then it may interact with the Taler plugin to enable withdrawal operations.  It'd be lovely to avoiding leaking this 1 bit of identifying information, but achieving that without the W3C's help is infinitely easier than not leaking the same bit of information to a merchant checkout page.  We're not worried currently. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/112#issuecomment-194497424