> Yes, and given the whole point of this work from beginning has been to reduce the complexity of the user experience, anything that requires additional work from users should be added only if it’s clear that it’s absolutely essential. And it’s not clear that payment-app registration is essential. I agree that is the goal. But our use cases make it clear (to me) that third party Payment Apps must be supported. And if that is the case, there must be a way to let the system know they are available. That has nothing to do with the user or user complexity. It isn't as if the user is typing PaymentApp.register(string, callback). The user clicked install on the Wells Fargo payment app while they were looking at their checking account balance. That interaction needs to work seamlessly. --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-payment-apps-api/issues/8#issuecomment-235973171
Received on Thursday, 28 July 2016 17:54:52 UTC