Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8)

I think how one registers a Payment App with a browser should either be in a Web Payments Browser API that covers everything you can do with Web Payments using a browser (request payment, register a payment app), or those two things should be divided into two specs: Browser Payment Request API and Browser Payment App Registration API. Keep in mind that there are other ways to request payment and to potentially register Payment Apps that do not involve browsers.

I do not think we should not create a "Payment Request API" spec that covers *all possible request APIs* and a "Payment App Registration API" spec that covers *all possible registration APIs*. Rather, each type of API (eg: HTTP, Browser, ?) should define its own set of documents and they can be broken up in whatever way makes the most sense for that type of API.

---
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/8#issuecomment-212984851