Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15)

I'd like the inputs to be split between 2 parameters because some are part of the payment request that goes to the app and others are explicitly intended to only be consumed by the browser (such as `requestShipping`).

Since the line item stuff in `PaymentDetails` is purely for display purposes by the browser, especially if we pull the total out into it's own item, I'd not include it in the payment request that goes to the payment app.

## PROPOSAL

* Move `items` and `shippingOptions` from `PaymentDetails` into `PaymentOptions`
* Drop the `supportedMethods` parameter.
* Define a `PaymentMethod` object which has:
    * A required member called `identifiers` which is a sequence of strings, each a payment method identifier. 
    * A `data` member which is a generic object and contains the payment method specific data for the payment method.      
* Add a `supportedMethods` member to `PaymentDetails` which is a sequence of `PaymentMethod` objects.

---
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/15#issuecomment-207087227