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

Matt Saxon suggested to Ian that in the real world, payment method filtering is handled by payment apps, citing Apple Pay, Samsung Pay, Android Pay as examples.

One idea is to add to the payment app specification the following:
* Payment methods may define filtering capabilities.
* Merchants would include filter information in the 'data' object (of payment request API) for accepted payment methods
* Payments apps would be responsible for implementing matching using the filter information. Payment apps could choose not to implement filtering for a given payment method.
* There would be a standard function implemented by payment apps that would respond true or false to queries from the mediator about (filter) matching for each payment method.

Thus, payment method-specific filters would be implemented by payment apps, not the mediator.

Note: For in-browser basic card support, this can also be modeled as the browser-as-payment-app implementing matching rather than the browser-as-mediator.


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