Hi @romandev, I think you described the privacy concern appropriately: there is concern about (all) payment apps learning about the user's interactions with the merchant BEFORE the user has selected a payment app. One idea, as you describe, is to get user permission. However, I think that there is some concern that it may be difficult for many users to understand the real implication of the permission. I forgot to link to yesterday's discussion of this: https://www.w3.org/2017/08/29-apps-minutes.html The two proposals other than canMakePaymentEvent() we are currently investigating are: * Static registration of PMI + filters. * Dropping this mechanism entirely, as there is a hypothesis that payment apps may be more motivated to be displayed than to be filtered out. Ian -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/pull/170#issuecomment-326016625
Received on Wednesday, 30 August 2017 14:55:44 UTC