From 0176dfb5ee84c087109149d024989d83eefd1cf3 Mon Sep 17 00:00:00 2001 From: Ian Jacobs Date: Thu, 1 Dec 2016 15:18:30 -0600 Subject: [PATCH] Updates to options based on 30 nov 2016 discussion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit See minutes: https://www.w3.org/2016/11/30-apps-minutes#item05 * Support for selection of options is now required. * Changed language from “display” to “enable selection” --- index.html | 37 ++++++++++++++++--------------------- 1 file changed, 16 insertions(+), 21 deletions(-) diff --git a/index.html b/index.html index d506df9..4de6aca 100644 --- a/index.html +++ b/index.html @@ -425,7 +425,7 @@

User Experience

  • The system should minimize user interaction for payment app registration, payment app selection, and payment credentials selection. Ideas include:
  • It is likely that this specification will include guidance rather than requirements about specific user experience optimizations.
    • @@ -769,7 +769,7 @@

    For each payment method indicated in the PaymentAppOption's enabledMethods field, associate the payment option and the payment app - with the payment method for future use. + with the payment method. @@ -861,10 +861,6 @@

    is to prepend the payment app name, e.g., "ExampleApp Visa ending in ***4756". However, when only one app is installed, the text "ExampleApp" is redundant.

    -

    It may be simpler for implementers to remove payment options - from this spec. A medium level of complexity is to specify - payment options, but give user agents choice of whether payment - options are supported.

    @@ -896,15 +892,15 @@

    The id member is an identifier, unique within the PaymentAppManifest, that will be passed to the - payment app to indicate which PaymentAppOption the user - selected. + payment app to indicate the PaymentAppOption selected + by the user.
    enabledMethods member
    The enabledMethods member lists the payment method identifiers of the - payment methods enabled by this option. + payment methods enabled by this option. When the merchant has provided a filter, it may be necessary to provide additional information about conditions under which the payment method is enabled.
    @@ -1022,28 +1018,27 @@

    Payment App Selection

    Selectable App Information Display

    After matching the user agent will have a list of payment apps that the user can select to handle the - payment request. How will these be ordered when they are displayed to the user, where do recommended apps + payment request. How will these are displayed and ordered, where do recommended apps fit in to the order and how do we treat apps that are both registered and recommended?

    - What information is needed by the user agent to display selectable apps? This needs to be captured - during registration. + What information is needed by the user agent to display selectable apps? This needs to be captured during registration.

    - The output of the payment method matching algorithm will be a list of matching payment apps from registered - payment apps and a list of recommended payment apps. The user agent will present this list of payment apps to the user - so they can select how they want to handle the payment request. + The output of the payment method matching algorithm will be a list of matching payment apps and options from registered + payment apps, and a list of recommended payment apps. The user agent will present this list of payment apps to the user for selection.

    -

    For the display of matching payment apps:

    +

    For matching payment apps:

    -

    For the display of recommended payment apps:

    +

    For recommended payment apps: