@adrianhopebailie > What is not clear to me yet is what combination of Service Worker registration code and calls to `PaymentManager.addOption(...)` or similar would result in this set of options being presented to a user (assuming the browser wanted to present the full depth of options). Yes, this is what we need to figure out next. [My proposal](https://github.com/tommythorsen/webpayments-demo/blob/gh-pages/proposals/Apps%20and%20Workers.md) suggests that the second level of your hierarchy comes from the Web App Manifest, and that the third level is provided (by means of `PaymentManager.addOption(...)`) by one or more Service Workers that belong to the Web App. -- 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/98#issuecomment-280634428
Received on Friday, 17 February 2017 12:16:52 UTC