Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138)

@adrianhopebailie wrote:
> We could have a stand alone messages spec which defines the base schema of the messages and the rules for encoding these in different forms but this could also be encapsulated in the two API specs.

@ianbjacobs wrote:
> The paymentRequest API and HTTP API specifications could end up sharing a parameter definition spec; I hope they do but I'd like to see each one mature before we factor that out.

I haven't heard a good reason to not have a common format for the payment request and payment response messages. Both the Browser API and the HTTP API are expected to communicate with Payment Apps by sending them a payment request and getting back a payment response. Why are we saying that the message that a browser sends might be different from the one that a non-browser sends? Seems like an interoperability failure waiting to happen.

---
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/138#issuecomment-210133641