It's still not clear to me if "native" payment handlers will have more capabilities to determine if `.canMakePayment()` can respond with "true" than the filtering here allows. That is, if a native (e.g., Android Pay, Apple Pay, Microsoft Wallet, or a native app installed from an app store) payment handler can do its `.canMakePayment()` support by: * performing a network request. * talking to a peripheral over USB, BlueTooth, NFC, or whatever. * access a database that checks something related to the user. Then we are doing the web a disservice by not providing an analogous set of capabilities. However, if the answer to `.canMakePayment()` is that native payment solutions only do the string matching, then filtering is fine. -- 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-276531400
Received on Tuesday, 31 January 2017 23:51:40 UTC