We discussed this at our payment apps call today: https://www.w3.org/2016/07/27-apps-minutes.html Jason took an action to write up a proposal. Here is a partial summary: * We want to reduce user friction in the system. * Payment app registration may happen differently in different scenarios in order to reduce friction. Some examples * When the merchant recommends a payment app and the user selects it, registration can happen in that moment without additional user action. * When the browser recommends a payment app and the user selects it, registration can happen in that moment without additional user action. (There is an expectation that the display of browser-recommended apps will differ from the display of merchant-recommended apps). * When the user installs native payment app, registration can happen as part of the app installation process. * Users visiting a Web site (e.g., merchant or bank) may wish to explicitly register payment apps. There may be additional useful distinctions between what happens for open v. proprietary payment methods, but for now it seems to me that we captured the main issues by looking at merchant-recommended, browser-recommended, and user-self-initiated. My sense is that we should still specify what data needs to be exchanged whenever the registration happens to take place via the browser. Ian --- 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-235642972
Received on Wednesday, 27 July 2016 16:34:07 UTC