Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17)

Having discussed this a little, here are a couple of thoughts:

* It may be difficult to pass this value through to a payment app - we should think about this as something that gets passed into the user agent to be used for UX
* We could keep this as an optional Boolean with true meaning success, false meaning failure, and undefined (i.e. not present) meaning indeterminate. In other words, don't show a success or failure animation in the UI if you get undefined.

---
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/issues/17#issuecomment-206502275