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

>From my current understanding, the purpose of the ``complete()`` action is to allow the merchant to tell the payment app that the payment has been processed / checkout is complete and let it close any UI associated with it.

A couple things:

1. In the case of a successful payment, the UI would almost always need to be closed so this works. In the case of a failed payment, the payment app will most likely want to let the customer know what the reason for that failure was and retry from the last step (validation error is a good example), so providing just a failure response isn't going to work, there needs to be some extra information provided, specific to the payment method that the payment app would know how to handle.

2. I'm not sure what use a payment app would have with knowing whether it was an auth, capture, auth/capture, settled, etc, that would be a merchant concern from my experience. I would think a payment app only wants to know what to do next at this step, not what type of transaction a merchant processed, this may come from the status of the transaction but in the end it's up to the merchant to determine what it wants the payment app to do (close UI, show error, retry, etc). I think we should consider making these codes more of instructions for the payment app, from the merchant, rather than codes that are specific to the payment method.

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