Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173)

+1 for `response.shippingAddress`. I feel that `response.details` is for information that falls outside the scope of the spec, but the payment app still wants to pass to the merchant.

(To add to this, I feel that the field for opaque data in the PaymentRequest and the PaymentResponse should have the same name. In the PaymentRequest, this field is called `methodData[n].data`, while `details` refers to an instance of the PaymentDetails dictionary. In PaymentResponse, however, `details` refers to opaque data. I propose renaming `details` to `data` in PaymentResponse.)

---
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/173#issuecomment-215674291