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

from @adrianhopebailie 
> The only component that requires "hints" is the user agent because it's not expected to understand anything about payment method data.

> Based on some of the observations in #19 I would like to propose that unless there is a need for the user agent to display the confirmation button (as opposed to the payment app) this is a non-issue.

> I propose that we close this issue and open a separate discussion to address the request from @mattsaxon and @vkuntz for a standard way to exchange the agreed payment obligation between payer and payee.

Nobody has objected to opening up a separate new issue for that, so I wonder if you will be going ahead with opening it, or whether you’d prefer for @mattsaxon and @vkuntz to open it. IMHO it seems like @mattsaxon ought to be the one to open it, since it’s his request.

from @mattsaxon 
> I'd like to leave open until the API has the hint that is needed for it to display the appropriate message.

Are you willing to open a separate new issue for “standard way to exchange the agreed payment obligation between payer and payee”, and if so, once it’s open, would you then agree that this issue should be closed as @adrianhopebailie has proposed? Or is there something else this covers that would not be covered by the “standard way to exchange the agreed payment obligation between payer and payee” proposal?

At least as far as what @adrianhopebailie has asserted, in the comments cited above, he’s said that there seems to be no need for a hint to the UA. Do you disagree?

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