@jakearchibald, > If my understanding is correct, there's a very definite 1:1 relationship between a payment app and a service worker registration. A developer may want to group multiple payment options under a single "Payment App", but implement different options via different service worker registrations. A Payment App may have more than one payment option that it registers. Imagine a scenario where the Payment App uses two service worker registrations, A and B. Service worker registration A could register payment option 1 and, therefore, its active service worker will receive the `paymentrequest` event for it, should the user select it. Service worker registration B could register payment option 2 and, therefore, its active service worker would receive the `paymentrequest` event for it. As long as some payment option is registered for a particular Payment App and the service worker registration persists, then the Payment App is "installed". -- 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-280736297
Received on Friday, 17 February 2017 18:59:34 UTC