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

@rsolomakhin,

Thank you for the feedback and welcome to the task force.

> I am of the opinion that installing a payment app is sufficient to register it. On the web, this can be 
> accomplished via registering a Service Worker and there's no need for additional 
> navigator.payments.register(info) API.

I think many would agree that any native app installation could include payment app registration and thus no additional user action would be necessary. However, for the Web-based payment app case, please say more about how the user consents to register the payment app. I think consent is important because you don't want payment apps mysteriously showing up in your "matching apps" list merely because you happened to visit a Web site. So it is likely that some user action is required to tell the browser about the payment app data. I'd love to hear more of your thoughts on how you see this happening.

I think there is strong agreement that we want to make it as simple as possible for users. Other than the native app installation use case, the other case we have been talking about is when the merchant recommend an app and the user chooses it, this could be the action that registers the app. It has also been pointed out that registration is not obligatory in this case; it's just useful if you want persistence of the data for future transactions.

> Let's stick with one-to-one mapping here for now. So BobPay should be able to display only 
> one item on browser UI: "BobPay".

Ok, that's helpful input on that question.

> The spec talks about network failures. I think Service Workers are the answer here. 
> They provide offline capability and caching, if necessary.

Do you think we need to provide any information (e.g., a transaction identifier) that
could be used to query the state of a transaction? 

Related: We have spoken about creating a "payment app good practices" document that could
include this sort of information (e.g., how to use service workers to deal with network failures). See also our early draft of https://w3c.github.io/webpayments/proposals/method-practice/

Thanks again!

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