- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Thu, 14 Apr 2016 16:26:53 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 14 April 2016 23:27:21 UTC
> Yes, that's a big problem. :) Sorry I should have said, _actually_ visa versa. I can see a configuration of the documents where the JSON encoding of a payment request and response and the mechanism for submitting these to a web based payment app are defined in the HTTP API. The browser API would be dependent on the HTTP API and would describe how a paymentRequest is converted to the JSON format defined in the HTTP spec and then submitted to a web based payment app (as described in the HTTP API). --- 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/138#issuecomment-210201639
Received on Thursday, 14 April 2016 23:27:21 UTC