Re: [paymentrequest] Let merchant pass in arbitrary data to payment request? (#11)

For now we don't think there needs to be a payment method independent way of passing this data to the user agent. For example, the basic card payment method that returns PANs and expiry, etc. will not need a transaction ID. How this data is handled will vary by payment method and what formats are supported will likely vary (JSON structured data vs. string, for example).

We propose that we handle this by providing any additional data that a payment method knows how to process as part of the payment specific data object that is passed into the `PaymentRequest` constructor. Once we have some implementation experience we can determine if we need to return to this topic and provide a more general way of supplying the data as part of the `PaymentDetails` object.

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/11#issuecomment-163373971