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: Adrian Hope-Bailie <notifications@github.com>
Date: Thu, 26 May 2016 09:03:34 -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/221916125@github.com>
> I think we are going to have problems enforcing this.

I don't think we have to enforce this but we should point it out in the spec so apps can differentiate IF they need to. In the proposed spec I worded this as:

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

So as long as the payment app believes it can handle the request it can set the method as enabled (that includes if the app is able to enroll the necessary instrument on the fly).

What we are trying to avoid is apps that advertise payment methods that have a high chance of failing because then the website has to resubmit the request and start the process again.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Received on Thursday, 26 May 2016 16:04:08 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 26 May 2016 16:04:09 UTC