- From: Rouslan Solomakhin <notifications@github.com>
- Date: Fri, 16 Feb 2018 07:07:51 -0800
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 February 2018 15:08:14 UTC
A payment handler is a service worker that stores payment instruments on user's computer. These instruments are used to determine which payment method the handler supports, for example. Without the instruments, a service worker is not a payment handler. On the other side of the coin, an instrument without a service worker is not a payment handler, because the browser would not have anywhere to fire a `CanMakePaymentEvent` or a `PaymentRequestEvent`. Service workers and instruments are two required parts for a payment handler, therefore. Removing the instruments or unregistering the service worker is equivalent to removing the payment handler. From looking at https://storage.spec.whatwg.org/#infrastructure, it appears that payment instruments are "site data," because they most closely resemble Indexed DB and Cache API and are closely tied to service worker registration, all of which are under the "site data" category. Does that answer the question? -- 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/payment-handler/issues/236#issuecomment-366260719
Received on Friday, 16 February 2018 15:08:14 UTC