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

Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)

From: Jason Normore <notifications@github.com>
Date: Tue, 31 May 2016 07:43:03 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/webpayments/pull/132/c222710371@github.com>
:+1: to the changes.

As an aside, this brings up the thought to me of whether or not both 'supported' and 'enabled' are really necessary because if I were a payment app I would say 'enabled' for everything that I support because I want to provide the best experience and to ensure I capture as many new customers as possible by having a seamless onboarding flow within the payment experience. I'll admit though that I'm probably not thinking of some payment apps that require a separate onboarding process that's impossible inside the payment flow, but from a customer perspective that wouldn't be a great experience anyway. A PR is not the appropriate place to discuss this, I'll open an issue after thinking it through a little more.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Received on Tuesday, 31 May 2016 14:44:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 May 2016 14:44:23 UTC