Payment Apps Task Force

<conorh_wp> Hello, having some tech difficulty but joining call momentarily.

ok

<Tommy> can I join? If so, where do I call?

sure!

https://mit.webex.com/mit/j.php?MTID=mab3c7a1fb772cbcbf39b054b2ebd9183

<Jason_YANG> hi

hi JasonY

<Jason_YANG> I am the colleague of Max and Kepeng ,from Alibaba

welcome

Design Considerations

https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#design-considerations

IJ: Did anyone have a chance to look at this?
... I would like to get feedback on this and then bring to WG

<conorh_wp> +q

Conor: I will volunteer to read it
... but regrets for next week.

JasonN: I will read it as well

(Comments welcome from others as well)

Issue 8 - Is the concept of payment app registration necessary?

Jason: Is it necessary to have a registration model? From a customer model perspective it increases choice and introduces complexity.
... and from a merchant perspective, it also adds complexity.
... from a payment provider perspective, responsibility is on the them to get user registered in a new environment
... it does seem registration is necessary from open payment methods
... for cards, I think browsers will implement their own and retailers as well

===

It seems inevitable that the browser needs to know payment app metadata.

They might know about that metadata a priori ("browser recommended payment apps") or from merchant recommendations.

They might learn about the metadata through user action, but as part of another process (e.g., native app installation).

They might learn about the metadata through explicit user action ("register me!")

====

Do those statements sound correct?

Jason: I can write a proposal if there's interest within the group to explore this option.
... I understand the wish to have a registration flow for customers

IJ: Can you say a little bit about what you have in mind?

Jason: the way to do this without registration is to leave registration as a relationship between customer and merchant.
... we allow the merchant to state what payment methods they support
... the "recommended flow" would eliminate the need of users to register

IJ: What about a bank app? How does it get to be into the mediator flow?

[Open and proprietary registration may be different]

In the proprietary case, the merchant knows which app will be launched.

scribe: is that enough information for the mediator to launch the app without prior user registration required.
... it suffices for the user to say "I want to use one of the merchant's recommended payment apps, say paypal"

====

"Current" assumption - users register payment apps with the browser

a) There are cases where the merchant has a relationship with an app provider, and where selection by the user of the app is sufficient.

a.i) Could that include registration for future uses as well?

PROPOSAL: Make "recommended apps" as good as registered apps

<Tommy> +1, but if we want to move from two lists ("installed apps" and "recommended apps") to one list ("merchant supplied list"), we may want to give the mediator the liberty to do some ordering of the list. The mediator may want to display payment apps that the user has used before, at the top of the list.

Conclusion: we need to discuss in the broader WG

b) There are cases where the browser has a relationship with an app provider; same thing

BUT display of these should be different from those recommended by the merchant

<jnormore> +1 "The mediator may want to display payment apps that the user has used before, at the top of the list.", the UA can still offer preferences and customization to the customer on those apps it's seen the customer use in the past

IJ: Question - so do we still need an API for "user recommended" apps to be known to the browser?

Jason: Browser can still do work of helping user manage order, etc. when merchants recommend apps

(e.g., based on previous choices, etc.)

[Discussion about whether merchants should be able to state "I only accept X"]

[And distinction between open and proprietary]

IJ: I still think we need a registration mechanism for "non-recommended" case

Next meeting

3 Aug

<jnormore> :)

<scribe> ACTION: Jason to write a proposal about minimizing the effort to register payment apps, calling out merchant recommendations, browser recommendations, and user initiated registration [recorded in http://www.w3.org/2016/07/27-apps-minutes.html#action01]