Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229)

Yes.  We do not want a situation where a "payment app" can be little more than a tracker that "pays" merchants with "discount coupons", but the net effect on the user is simply that they are being tracked through yet another source.  It's good if show always changes the top level context, but actually not quite sufficient.  

In fact, I'd think security dictates that the browser's payment mediator should always make an appearance, even if the merchant only supports one payment app.  Now some browsers might find ways to skip the payment mediator, but if the browser has a security settings, slider, etc. then our recommendations should be that anyone with any security contentiousness should always see the payment mediator during a payment. 

-- 
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/browser-payment-api/issues/229#issuecomment-248277508