:+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: https://github.com/w3c/webpayments/pull/132#issuecomment-222710371
Received on Tuesday, 31 May 2016 14:44:23 UTC