-
- Origin and Instrument Display for Selection
-
-
- After applying the matching algorithm defined in Payment Request API,
- the user agent displays a list of instruments from matching payment
- apps for the user to make a selection. This specification includes a
- limited number of display requirements; most user experience details
- are left to implementers.
-
-
-
- Ordering of Payment Handlers
-
-
- - The user agent MUST favor user-side
- order preferences (based on user configuration or behavior) over
- payee-side order preferences.
-
- - The user agent MUST display matching
- payment handlers in an order that corresponds to the order of
- supported payment methods provided by the payee, except where
- overridden by user-side order preferences.
-
- - The user agent SHOULD allow the user
- to configure the display of matching payment handlers to control the
- ordering and define preselected defaults.
-
-
-
- The second bullet above may be amended to remove explicit mention of
- ordering defined by the payee.
-
-
- The following are examples of payment handler ordering:
-
-
- - For a given Web site, display payment handlers in an order that
- reflects usage patterns for the site (e.g., a frequently used payment
- handler at the top, or the most recently used payment handler at the
- top).
-
- - Enable the user to set a preferred order for a given site or for
- all sites.
-
- - If the origin of the site being visited by the user matches the
- origin of a payment handler, show the payment handler at the top of
- the list.
-
-
-
- The Working Group has discussed two types of merchant preferences
- related to payment apps: (1) highlighting merchant-preferred payment
- apps already registered by the user and (2) recommending payment apps
- not yet registered by the user. The current draft of the
- specification does not address either point, and the Working Group is
- seeking feedback on the importance of these use cases. Note that for
- the second capability, merchants can recommend payment apps through
- other mechanisms such as links from their web sites.
-
-
-
-
- Display of Instruments
-
-
- The user agent MUST enable the user to
- select any displayed instrument.
-
-
- - At a minimum, we expect user agents to display an icon and label
- for each matching origin to help the user make a selection.
-
- - In some contexts (e.g., a desktop browser), it may be possible to
- improve the user experience by offering additional detail to the
- user. For example, if the user's "bank.com" origin knows about two
- credit cards (thus, two potential responses to the same payment
- method "basic-card"), the user agent could display each credit card's
- brand and the last four digits of the card to remind the user which
- cards the origin knows about.
-
-
-
- The Working Group is discussing how default payment instrument
- display could further streamline the user experience.
-
-
-
-
- Selection of Instruments
-
-
- Users agents may wish to enable the user to select individual
- displayed Instruments. The payment handler would receive information
- about the selected Instrument and could take action, potentially
- eliminating an extra click (first open the payment app then select
- the Instrument).
-
-
-