Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)

After discussing this with @zkoch, I'm starting to lean toward the `.canMakePayment()` approach for the payment handler to perform the filtering. The user should have ability to avoid this call either via user agent setting or by entering private browsing mode. This alleviates the concern about leaking sensitive information to the payment handler before selection.

Note that the user must install the payment handler first before the handler is able to receive the `.canMakePayment()` call. This indicates elevated trust on the part of user, which also alleviates the privacy concern somewhat.

-- 
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/payment-handler/issues/157#issuecomment-303576073