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

I'd expect that depends upon the nature of the payment app.  I'd expect a web based payment app cannot do this for the same reason it cannot really do it now.  There is however only really one way to arrive on the payees fulfillment page, and the payee can employ communication not mediated by the browser.  An browser extension can do post fulfillment interaction in more ways. And a native app can circumvent the browser entirely. 

---
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-203896999