Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403)

Perhaps it would be better to initialize the `PaymentRequest` instance when the customer lands on the "summary page" in step 2. Then, when the customer is ready to click on another "Checkout button" in step 3, you can call `request.show()` instead of redirecting to the traditional checkout form. (If `PaymentRequest` is not supported, you can fall back to the traditional checkout forms.) Would that work? 

-- 
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/403#issuecomment-297547358

Received on Wednesday, 26 April 2017 21:33:08 UTC