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

+1

From: Manu Sporny <notifications@github.com<mailto:notifications@github.com>>
Date: Saturday, Dec 09, 2017, 10:13 AM
To: w3c/payment-handler <payment-handler@noreply.github.com<mailto:payment-handler@noreply.github.com>>
Cc: Kenneth Mealey <Kenneth.Mealey@aexp.com<mailto:Kenneth.Mealey@aexp.com>>, Mention <mention@noreply.github.com<mailto:mention@noreply.github.com>>
Subject: 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 were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/w3c/payment-handler/pull/242#issuecomment-350477408>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZrykDw0vSSeZPC7lCWeFbp987YrVQazks5s-qODgaJpZM4Q582s>.


American Express made the following annotations
******************************************************************************
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."

American Express a ajouté le commentaire suivant le Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent renfermer des 
renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci.

******************************************************************************


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