Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)

Thanks for a great explanation, Adrian. That makes a lot of sense.

The reason I created this issue is that I'm currently in the process of making a tentative implementation of web payments for the Opera browser. One of my top priorities is to make the payment flow as simple and understandable as possible for the user. With that in mind, consider the following potential flow:

- BACKGROUND: Bob the user has installed the app "PayByCard" which supports payment by all brands of credit card. He has configured two different visa cards -- his work card and his private card.
- STEP 1: Bob clicks "Pay" on a web site which supports payment by visa card.
- STEP 2: The browser (the payment mediator) compares the web site's supported payment methods with the installed payment apps and concludes that PayByCard is able to fulfill the payment request. Bob is shown a dialog where he can choose the PayByCard app (and potentially a whole list of other apps that fulfill the criteria).
- STEP 3: Bob selects PayByCard and is taken to the app where he is given the choice between his two configured visa cards.
- STEP 4: Bob selects his private card, and the payment is ready to be processed.

As a UI developer, I would really like to be able to smash STEP 2 and STEP 3 together so that I could present Bob's two credit cards in the very first screen Bob sees, without him having to go through the extra step of selecting the payment app first. Is there a way the current specification allows for me to do this? Can this be done by having multiple "pay" actions with the same type?

---
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/webpayments/issues/124#issuecomment-211865953