Some additional notes: * Once invoked, the payment app can choose to fail, and the merchant will get back a fail message for the PR API invocation, without information about why. So this sort of "decline" is possible, it's just after the matching phase. * AdamR pointed out that if the canHandle() function cannot access the network, you can "bake in" some code (e.g., a list of bad sites) so that network access is not required by canHandle(). Then you can update canHandle() periodically as needed when the payment app is in use. I'll put this topic on the agenda this week or next. Ian -- 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/92#issuecomment-273898549
Received on Thursday, 19 January 2017 21:06:50 UTC