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

To capture some notes about what we discussed on the payment apps call -- there were concerns (both performance-related and privacy-related) about the proposal as stated. One proposal was that part of app registration could include a lambda function -- required to be a *pure function* -- that took the filter as input and generated a boolean "I can handle this" as output. These would be evaluated in an isolated context a null origin (or what specs mean when they say the "origin is a globally unique identifier"), which would prevent external access (addressing the performance concerns) and prevent local storage (which would, in concert with preventing external access, address the privacy concerns).

-- 
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-254831042