Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)

@adamroach - I agree with you but I think we should prove that this is easy to do using ServiceWorkers before we dismiss offering an alternative.

I'm busy trying to hack together a POC of this and will share when I am done.

> If the app uses javascript to pass the response back, is it really that unreasonable to require that they use javascript to get the payment request in the first place?

@tommythorsen  - I'd say yes actually. If the processing of the payment request is complex then it might be preferable to do this server-side and to return an HTML UI with just light client-side processing (maybe just a confirmation page).

---
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/webpayments/issues/130#issuecomment-220353046