@marcoscaceres wrote "The browser knows the registered methods of the app, so it could strip out the ones that don't match." We asked ourselves "who should do the filtering, the browser or the payment app?" There are pros and cons to each approach. If browsers do it, payment apps don't have to, which is a good thing. However, we expect to see a number of payment methods in use, each with its own filtering mechanism, and if we rely on the browser, then we are not likely to see those implemented. Therefore, we have favored asking payment apps to implement the filtering. Ian -- 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/96#issuecomment-274810554
Received on Tuesday, 24 January 2017 14:04:48 UTC