> > Is the canHandle() mechanism an absolute and fundamental requirement that we can't do without? > > I believe it is. The Service Worker or object that the Service Worker gets representing the PaymentRequest must be able to handle all the method calls: .canMakePayment(), .abort(), .updateWith(), etc. Well, we could remove .canMakePayment() too... > I don't think we should do the recommended payment app thing - the merchant can recommend whatever they like (or fall back to basic card). I'm not sure I follow your argumentation, but falling back to basic card is certainly also an option. I think that for the sake of kickstarting the payment app ecosystem, though, recommended payment apps has the potential to work very well. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-payment-apps-api/issues/96#issuecomment-275066607
Received on Wednesday, 25 January 2017 10:02:01 UTC