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

@rsolomakhin wrote:

> There're several options available to us. From the top of my head, one method is to gate payment 
> app Service Worker registration on user activation. So the user must click an [Install BobPay] button > for register() call to succeed.

That was my expectation. To summarize, I see it this way:

* There is a register() function
* It is called in different ways (e.g., during native app installation, as a result of selecting a merchant-recommended app, or upon explicit "register me!" for a web-based payment app).
* It is not always necessary to call it (e.g., one-time usage of a merchant recommended app)
* We want the user to have to do as little as possible to register a payment app, and consent is important but happens in different ways (e.g., explicit installation of a native payment app constitutes consent to register it).

Does that align with your thinking? 

Ian



-- 
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-245434583