Re: [w3c/payment-request] Make "total" and "details" optional (#912)

There's some confusion on a few threads about this that we would be relaxing the restriction across the board. @maxlgu I think you should update the proposal to be clearer that the individual payment processors can still mandate the total, but that this allows new payment processors to not require a total.

Here's the text of [my reply](https://lists.w3.org/Archives/Public/public-payments-wg/2020May/0011.html) on the above thread:

> We are not proposing making "total" generally optional (for all payment methods). Rather, it would become at the discretion of the user agent or payment handler when it is required (i.e., it would no longer be "required" in the WebIDL type, but the handler is allowed to throw an exception if it's not given).
>
> For traditional payment methods, this would still be required (otherwise there is no way to communicate to the payment provider how much money is actually being spent). But for some new payment modes such as the proposed [Digital Product Management API](https://discourse.wicg.io/t/proposal-web-payments-digital-product-management-api/4350), the server is the source of truth on what the price of the item is, and requiring the payment amount to be given by the client is redundant.

-- 
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/payment-request/issues/912#issuecomment-626416957