Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133)

> @@ -284,16 +284,77 @@
>            payment app.
>          </div>
>          <div class="note">
> -          <p>The <code>supportedMethods</code> sequence contains the <a>payment method identifiers</a>
> -          for the <a>payment methods</a> that the merchant web site accepts.</p>
> +
> +          <p>The <code>details</code> contains the core payment request data that will be passed on to the user selected
> +            <a>payment app</a>.</p>
> +
> +          <p>The <code>amount</code> sequence contains the amount (possibly in different currencies) that the website

Is this "amount" in the top-level details object, or is it in every paymentMethod object? I'm a -1 for the former (top-level) and a +1 for the latter (in every payment method object). The -1 is because it feels like doing so would duplicate data (because we'd also have that same data in each payment method object?)... sorry, can't see the complete spec to see where the change is (and don't have the time to checkout this branch and view it locally). Hopefully this comment makes sense to you @adrianhopebailie.

---
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/pull/133/files/38f22264a20bbe3dcaaa3d47036d9c08c07237fc#r59144649