Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18)

Here's a proposal:

dictionary PaymentDetails {
    sequence<PaymentItem>    items;
    sequence<ShippingOption> shippingOptions;
    optional<PaymentItem> total;
};

And define total in the spec as something like this:

 "This field is used to communicate the total amount of the transaction. Processors are not required 
 to validate that subtotals add up to the total amount."

Then delete this:

 "The last PaymentItem in the sequence represents the total amount of the payment request. It is the responsibility of the calling code to ensure that the total amount is the sum of the preceding items. The user agent MAY not validate that this is true. "

(In any case "MAY not" needs to be fixed.)

Ian


---
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/18#issuecomment-213148126