Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56)

I don't think it makes a lot of sense to worry too much about the specific word on a button which may or may not exist in the payment app.

On the other hand, I think it does make sense to indicate to the payment app what kind of user journey its in the middle of, and where in that journey it might be.

For example, if building a basic card payment app, knowing whether or not there's a 'confirm' page after the card details are returned to the merchant allows me to choose how defensive my UI is, and whether I want to have a confirm step for *this payment request* within the app.

So it feels to me like its probably useful to enumerate the different journeys and allow a hint to be passed into the payment app which can then do the best thing for the user.

---
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/56#issuecomment-200752089