W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)

From: ianbjacobs <notifications@github.com>
Date: Fri, 27 May 2016 11:26:22 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/webpayments/issues/110/222219747@github.com>
@adrianhopebailie wrote:

"If a payment app defines a payment method as enabled then it MUST be able to process any payment request that lists that payment method as supported"

My first observation is that is a requirement on payment apps. In previous conversations you had said you were trying to think about conformance only for browsers (which I don't mind as a project). I just want to point out this would be an exception.

My second is that I don't think we should include that requirement. Here's why:

 * The requirements for conformance to a payment method should be part of the payment method spec, not the payment app spec.
 * I don't believe that we should tightly couple the definition of "enabled" as it relates
  to matching, with processing.
 * In general, I don't think we need requirements of the form "if you say you do it, you have
   to do it." Rather, we need statements that simply add up to conformance: "Do X. Do Y."

Meanwhile, we have listed a number of requirements related to the display of payment apps and the selection of payment apps:
 * https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#payment-app-display-by-the-browser
 * https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#payment-app-selection-by-the-user

In that list is this requirement:

 * The user must be able to select any displayed payment app.
 * Selection of a recommended (but unregistered) payment app should lead to payment app registration before invocation.

Note that "displayed payment app" is defined in the wiki to be: "a matching or recommended payment app presented by the browser for user selection."

...and there are definitions of "matching" and "recommended" payment apps etc.

We have not agreed yet to support "recommended payment apps" but the topic has
come up and so I've put some ideas about them in the wiki.

Ian






---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/110#issuecomment-222219747
Received on Friday, 27 May 2016 18:26:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 May 2016 18:26:50 UTC