The design of this (if it's necessary) depends heavily on the kind of access it needs to other things. @adamroach can you pick up where @tommythorsen left off? Can you write some code that shows what a developer may need to write in a `canMakePayment` callback? Something that shows a decision being made that the browser couldn't make itself. I imagine there are a few ways to solve this, and some are defined by specs already, but we shouldn't be diving into the solution until we fully understand the problem. -- 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-275372103
Received on Thursday, 26 January 2017 11:59:24 UTC