Re: [w3c/browser-payment-api] Fix #129 (#153)

@mattsaxon - I think what @hober is getting at is this statement:

> Any value passed to complete() only goes as far as the browser.

This is going to significantly degrade the experience for some payment instruments. I actually think some payment apps *need* to have the completion value passed back to it. An example is UnionPay, where transactions may require a PIN. This PIN (in encrypted form) is passed from the payment app via the user agent and payment processor to the issuing bank, where it's validated. If it's incorrect, the payment processor is instead of providing a "Success" or "Failure" going to return an "Incorrect PIN" status.

*Ideally*, the payment app is still visible at this point and can simply prompt the user to try again. But under the modified PR #161 that was taken, the payment app never gets the result of this. So the user has to go through the *entire* payment flow again, selecting the China UnionPay app, entering the PIN, etc. It's a bad user experience.

Now, I can see that some payment apps *won't* need to know or care about the completion value. But some do, and that should be accounted for.

---
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/153#issuecomment-216005807