Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27)

@ianbjacobs wrote:
> I do not see that the above use cases relate to the scope of the current WG charter.

Some do, some don't. We need to make sure we don't /only/ look at the use cases in Phase I. The Web Payments IG has reviewed and agreed to place those use cases into our use cases document because they're an important part of the Web Payments ecosystem we're building.

> What use cases for the browser API require the data to be reused by arbitrary processors outside of the browser API itself?

Let me take the opposite approach that I took above and give a single example (there are more than just this one):

Take the Payment Request, for example. The assumption is that the browser API is going to send this message to a payment service processor web page of some kind. Let's assume the PSP is using HTTP.  So, how does the PSP get the payment request message from the client-side code to the server-side code? I would hope that it serializes it as something JSON-like and sends it to the server-side code for processing. We could either require each PSP to create their own payment request serialization format, or they could re-use the JSON message that we have for the payment request.

The same holds for the payment acknowledgement. Where is that generated? It's probably generated on a server somewhere and then transmitted to the web payments browser API.

So, even in the most basic case, these messages travel outside of the Browser API.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/27#issuecomment-178758216