Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63)

Adding notes from 19 October app task force discussion:
https://www.w3.org/2016/10/19-apps-minutes.html#filtering

* Need to clarify whether the expectation is that the mediator will still match on the payment method identifier and the payment app will only handle the filter.
* AdamR pointed out that up to now, payment apps have only known about a payment request once selected by the user. But if they are polled for filter matching, this could (depending on how it's proposed), leak information to the app about the existence of a payment request BEFORE the app has been selected.
* Jason points out that some payment apps might implement filtering on the server side, and performance would be a concern.
* AdamR began the thought process of whether a function that returns a boolean about filter matching could be a pure function provided at registration, and that could be run without letting the payment app know.


-- 
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/63#issuecomment-254831097