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)

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.

Thus I want to re-state my proposal that we:
>Allow the payment app to display an appropriate verb based on whatever logic they choose. The payment app is the payer's agent and so is not likely to be malicious or defraud the payer.

All of the logic about what type of payment processing is being requested should be understood by the payment app (which has claimed explicit support for the requested payment methods) so the payment app should be capable, based on the payment details and payment method data, of indicating to the user what they are accepting.

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.

@rsolomakhin has suggested that the label on the "total" (last) line item is the appropriate string but I don't think we should conflate the two. One is a clean user readable string explaining the total of the transaction the other is a legal obligation passed from the payee and acknowledged by payer.


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