This is right. > Then basic card converts the resulting parsed JS object to a dictionary. This can fail. At this point there would need to be a communication channel for showing an error back to the user. I think we get this for free. If the payment app is unable to handle a payment request, then it will be filtered out of possible payment methods. If no payment app is available to handle the payment request, then `.show()` is rejected with `NotSupportedError` exception. Do you think that works? If that works, should we write it down (either normatively or as a note)? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/307#issuecomment-267149109
Received on Wednesday, 14 December 2016 20:36:58 UTC