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

> @jnormore as per the spec, the complete() method must "Pass the value of success to the Payment App that accepted the payment request."

No, not the payment app, the user agent. See https://w3c.github.io/browser-payment-api/specs/paymentrequest.html#complete. Full text:

> The complete method must be called after the user has accepted the payment request and the [[acceptPromise]] has been resolved. The complete method takes a boolean argument that indicates the payment was successfully processed if true and that processing failed if false. Calling the complete method tells the user agent that the user interaction is over (and should cause any remaining user interface to be closed).

So complete() is just an explicit way for the merchant to tell the user agent to explicitly close the UI.

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

Received on Thursday, 31 March 2016 21:06:35 UTC