I think we have to accept that the concept of a "Web App" is something that already exists, and that if we want to make use of the slogan "A Payment App is a Web App that does payments", we have to align our definition of "Web App" with what most people consider a Web App to be. This whole concept is quite fuzzy, and different people will have different opinions of where the boundaries of a Web App are, but I don't think most people think that "a Web App is the same as an origin". The related concept of a "Progressive Web App" as defined by the Web App Manifest specification allows for an arbitrary number of Web Apps within one origin, and I feel that it would be wise of us to align with this. Of course, what you are suggesting, @adrianhopebailie, will also work perfectly well, and it's actually really similar to my proposal (the algorithm will be almost identical), except that the origin is used as a "default wallet", rather than the current web page. If we go in that direction, though, we should stop talking about "payment apps" (and rename the specification). Maybe "payment handlers"? -- 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/webpayments-payment-apps-api/issues/105#issuecomment-283041576
Received on Tuesday, 28 February 2017 13:42:29 UTC