Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40)

I maintain that a web-based payment app is an essential requirement for this API.  The alternative is native thin payment apps that communicate with their web service outside of our context.  I mean - that is what is going to happen anyway with any native payment app IMHO, but there is no reason I can think of to require that sort of an architecture.  A payment app (read web app) should be able to register a URI that gets invoked using messaging we define for the various interactions we require. 

---
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/40#issuecomment-197944308