Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23)

At the 8 September teleconference [1] we discussed a use case raised by Max [2]. 

Here is my understanding of our current approach to balancing merchant preferences and user preferences:

 * Merchants express order preferences through payment method order (in payment request API) and through recommended apps (in the still draft payment apps spec).
 * Browsers would respect those order preferences by default, but MAY provide users with additional services to order apps according to user preferences. The WPWG will not standardize those preferences, but a variety of ideas have come up such as putting recommended payment apps in a privileged position; or when a user is visiting a site and has an app with the same origin displaying that app in a privileged position; or when the browser detects usage patterns for a payment app across sites, the browser might show that one in a favorable position; or the browser might allow the user to specify a preferred order; etc.

Thus, I believe the current approach is to let merchants express preferences and assume users will also be able to do so, and then allow the browser to take that data into account to do the right thing from the user's perspective (also honoring merchant preferences to the extent possible). 

I am reopening this issue to reconfirm (or change) this approach, and to see whether any other merchant preference mechanisms would help address the use case identified by Max.

Ian

[1] https://www.w3.org/2016/09/08-wpwg-minutes.html#item02
[2]  https://github.com/w3c/webpayments/blob/gh-pages/proposals/payment_app_user_experience.markdown

-- 
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/browser-payment-api/issues/23#issuecomment-245684311