Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242)

A couple of observations... the spec is now silent on:

1. Payment Instrument ordering and defaults. It talks about Payment Handlers, but not Payment Instruments (which are the things that show up on the UI).
2. Usage patterns being used as an input to ordering.
3. Reducing clicks based on default instrument selection.
4. Merchant preferences being used as an input to ordering.
5. Minimum display expectations (icon and name).

Not defining these expectations about defaults and ordering could result in a developer implementing the spec preferring their organization's payment instruments over others by default as a good idea. It's this sort of "default" behavior that led to the landmark $732M EU fine where the organization knew about their corporate requirements, but whose developers failed to follow through on those requirements - http://www.nytimes.com/2013/03/07/technology/eu-fines-microsoft-over-browser.html 

Suggested text:
>  When ordering Payment Handlers and Payment Instruments, the user agent is expected to honor user preferences over other preferences. User agents are expected to permit manual configuration options, such as as setting a preferred Payment Handler or Payment Instrument display order for a site, or for all sites. 
>
> It is expected that User agents may take usage patterns, user experience optimizations such as reducing clicks, and merchant preferences into account. It is expected that preferences will be taken into account in the following order: manually set user preferences, user preferences based on usage patterns or optimizations, merchant preferences, and default user agent preferences considered last. 
>
> User experience details are left to implementers. 

Feel free to reword/reformat as the Editor's see fit.

-- 
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/pull/242#issuecomment-350477408