@adamroach > Keeping that in mind, describe a scenario that the proposed "Recommended Payment" functionality enables that isn't currently possible. Start with the user clicking on "buy," and describe the steps that take place up to the point that money leaves that user's possession and enters the hands of someone they did not desire to pay. As I've been pointing out in my comments (https://github.com/w3c/webpayments-payment-apps-api/issues/48#issuecomment-273201675), I'm not party to the internal discussion of this group, so I'm trying to piece things together from what I can find on specs & on GitHub. I keep asking how this data is going to be used, and what the flow is for a recommended payment app. If this group has already shown that browser UI can be used to show recommended payment apps in a safe & beneficial way, please point me to it. Pointing me to the existing evidence seems more productive than me guessing and being told I'm right/wrong 😄. -- 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/webpayments-payment-apps-api/issues/48#issuecomment-274429380
Received on Monday, 23 January 2017 08:45:37 UTC