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

There is a top-level amount but as I say in the issue marker we could also define an optional per method amounts field which (if present) overrides the top-level amount. See https://github.com/w3c/browser-payment-api/issues/4#issuecomment-207913477

---
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#r59202299