Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42)

@ianbjacobs,

Yeah, but this document seems to do things like explain Payment Apps -- which I would expect to be in a separate document as they relate to more than just the browser API. 

I can imagine a Web Payments Architecture doc similar to what @adrianhopebailie wrote that talks about the various concepts, such as Payment Apps, and the various APIs that are available in the ecosystem. For example, the document would indicate what Payment Apps are and that if you want to  register a web-based Payment App for use with the Payment Request API, use the Registration API to do that. The document could also say, if you want to write a Payment App and send a Payment Request Message to an HTTP endpoint for processing, use the HTTP API. If you want to accept payment on your website, call the Payment Request API. And so forth.

The scope and how all of the various pieces relate to one another is larger than a single API. It seems like much of the material that is in the Payment Request API Architecture document should be in such a document. Right now there is significant overlap/duplication which seems like it would require extra work to keep in sync in the future.

---
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/42#issuecomment-197540319