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 requesting to be paid.</p>
> +
> +          <p>The <code>supportedMethods</code> sequence contains the <a>payment methods</a> that the merchant web
> +            site accepts. Each <a>payment method</a> is linked to one or more <a>payment method identifiers</a>.</p>
> +
> +          <p>The <code>identifers</code> sequence contains the <a>payment method identifiers</a> that identify the
> +          <a>payment methods</a> the web site supports and for which the associated <code>data</code> is part of the

We need a mechanism to pass payment method specific data in the payment request. The format of this data is not specified here so this is just a hook. I don't think it should be defined as WebIDL at all (See https://github.com/w3c/browser-payment-api/issues/132). What do you suggest?

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