> the browser would invoke the payment app but not pass it any (payment request) information. The user could do whatever they want with the app (updates, add new payment instruments, etc.). An easy way to do this would simply be to make an HTTP GET request to the same URL that the payment requests are submitted to via HTTP POST. It's pretty trivial for the app issuer (as a remote HTTP server or local ServiceWorker) to differentiate between the two. --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/111#issuecomment-227834528
Received on Wednesday, 22 June 2016 18:28:02 UTC