- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Thu, 01 Dec 2016 00:24:42 -0800
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 1 December 2016 08:25:42 UTC
I am with @zkoch on this. I'm not sure I see the use case here beyond card payments. I'd expect that for websites that are posting the PaymentResponse to a server they'll simply POST the JSON in the body of a new request. I think this issue is implying that POSTing `application/json` is less desirable than POSTing `application/x-www-form-urlencoded` data? -- 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/330#issuecomment-264108107
Received on Thursday, 1 December 2016 08:25:42 UTC