@burdges I think several of your suggestions are already implemented by https://w3c.github.io/browser-payment-api/#canmakepayment-method :
- step 3 allows returning a rejected promise with QuotaExceededError (your 4)
- step 6.1, modulo some above-mentioned ambiguity in the definition of "supports", allows always returning false or true (your 2 and 3)
I don't think your 1 is a good idea, as asking if you can make a payment should not show a payment; that defeats the purpose of the API.
--
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/browser-payment-api/pull/380#issuecomment-270660800