> It is not clear to me how an API instantiated on a merchant page will deal with redirects to a payment provider site and still be able to provide a return result. To be clear, this is also possible via URL-based callbacks, you can relay messages using that mechanism, but it forces Web developers to initiate a payment at one location and complete it at another location (which is done today, but it's not as nice as just waiting for a promise to be fulfilled). Note that this second approach is sort of what the HTTP API uses (because that sort of programming paradigm is more common place in non-browser HTTP clients): http://web-payments.github.io/web-payments-http-api/#processing-a-payment-request --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/16#issuecomment-161503004Received on Thursday, 3 December 2015 03:12:00 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC