Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34)

> > There is a register() function

> Is this needed if payments apps are ServiceWorkers? There is already a way to register SWs

The way to register SWs is through the `navigator.serviceWorker.register()` function. This is the `register()` function that I have in mind here. It's the same for Service Workers and payment apps. According to the broad consensus on issue #33, payment apps are Service Workers.

> > It is not always necessary to call it (e.g., one-time usage of a merchant recommended app)

> I don't follow how this would work.

Normally your website would call the `register()` method in JavaScript to register a Service Worker. This triggers the browser registration logic. However, the browser can trigger this registration logic from a payment UI as well.

> The issue here is with push payments where the website gets no response from the app and so has no way of knowing if the payment was completed.

Since this is relevant to push payments only, we should discuss it in the push payment spec, right?

-- 
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/34#issuecomment-245456011