Re: [paymentrequest] Constructor should not include "total" in list of items (#68)

Apologies - I of course meant "the only thing that really matters to the payment flow".  The user needs to know all sorts of stuff.  I am not proposing that we get rid of the items list.  I am proposing that the total be a separate item - in particular because it is by definition NOT an item.

On Fri, Feb 26, 2016 at 9:34 AM, Nick S <notifications@github.com <mailto:notifications@github.com>> wrote:
The total is neither an item nor a fee. It is the total. It is the only thing that really
matters.

In the spirit of stimulating further discussion, I shall disagree with that point. Sometimes from the user's perspective the total is the last thing that matters. This is because some types of payment instrument - such as an EMV card - require an absolute amount to be charged (the 'total'). However, this absolute amount may have little to no bearing on the expected cost of the product (an Uber or Lyft pre-auth, for example).

From the payment provider's perspective, the total may well be the only thing that really matters. That is not true from the user's perspective.

—
Reply to this email directly or view it on GitHub <https://github.com/WICG/paymentrequest/issues/68#issuecomment-189384371>.




--
Shane McCarron
Projects Manager, Spec-Ops