Thanks for your answer Rouslan. The usual and classic flow on any e-commerce stores is as follow: 1. Customer add products to cart 2. Customer clicks on the "Checkout button", which redirects to some "summary page" 3. Customer is ready and click on another "Checkout button" which redirects this time to the traditional checkout forms If one wanted to perform some `canMakePayment` logic while on step 3, he would have to spin-up 2 instances of paymentRequest. Your example is great and I get the idea, but this would assume the customer will get the paymentRequest slate on the first checkout button click (step 2 above), and won't have time to see the summary of his cart. Of course we can add this summary directly into the paymentRequest slate (lineItems), but I'm wondering if this is the best for the customer in term of UI (more than 5 items and the Payment slate becomes hard to read) -- 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-297546248
Received on Wednesday, 26 April 2017 21:28:02 UTC