Re: [w3c/payment-request] Changes resulting from 28 February PING privacy review (#843)

> I suggest adding an additional exception type, or return value to the canMakePayment promise indicating "user is still interested in Web Payments, but no background / passive checking, to maximize use of Web Payments API. Thoughts?

The use case remains that "can make payment?" is intended to be used to present, for example, an Google Pay specific button directly in the web page. Asking the user is not practical, because the site is effectively "port scanning" what supported payment methods are.  

I think the only feasible solution here is for the user to have control over this (like Safari does). Basically, an opt-in this check: 

> "[ ] Tell sites I support "basic-card" (when not in Private Browsing mode)." 

-- 
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-request/pull/843#issuecomment-469540188