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: Sat, 28 May 2016 03:15:50 -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/222301130@github.com>
> 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

:+1:  - I haven't yet incorporated the edits you and I discussed. I don't think this should be normative text. It is supposed to be guidance for payment app developers to ensure they understand the distinction and don't register themselves with browsers in a way that will lead to many abandoned transactions.

I only referenced the current text here to point out to @tommythorsen that the intent is for payment apps to decide which methods they support are enabled and that they can do this based on their own logic as long as they only list a payment method as enabled if they believe they will be able to handle a payment request for that payment method and any enrollment that may be required can be done on the fly.

---
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-222301130
Received on Saturday, 28 May 2016 10:16:22 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 28 May 2016 10:16:23 UTC