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.

I don't believe that is true. You don't currently ask if the user if they want to use the (only) legacy method before offering it to them. With PaymentRequest it should be as seamless. In step 3 above, you redirect without prompting the user anything. So they click the checkout button, and then see the legacy method. They may not know or care that in-between you checked with PaymentRequest. Alternatively, the user agent may have prompted them to install or populate a new payment method and when they declined they were redirected to the legacy flow. In either case it feels natural to the user.



1) 

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