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

The problem with the fallback flow is we need to wait for user to click on something before calling the `show()` method. This makes two users have two interactions. A first one on "pay with payment request",  then another one "sorry, we can't use payment request, do you want to try an alternative legacy method?". This looks pretty deceptive to me.

That being said, I totally agree with you, it sucks if a website can probe the payments methods supported by a user-agent.

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