Re: [w3c/browser-payment-api] Detecting payment method support (#247)

> Right now on chrome 53, if we run this snippet of code, it will start showing up a payment window and then it disappears almost immediately. This make deceptive UX.

This sounds like a bug. The API should fail with no UI impact if the payment method is not supported.

The reason we don't currently have something akin to `validate()` is that we don't want merchants to use this API to farm information about their users.

Imagine you register a payment app from  visit `http://mikeshardware.com` and install their payment app which supports a proprietary payment method for paying with loyalty points. 

Now you visit `http://bobshardware.com` and they can test to see if you have that payment method supported?

Since we have agreed on using payment method manifests I'd suggest we have a set of allowed origins for validation as a way to resolve this but I'm sure there are some complex user consent issues we'll need to consider.

-- 
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/247#issuecomment-246306165