Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) from adamroach on 2017-01-31 (public-webpayments-specs@w3.org from January 2017)

From: adamroach <notifications@github.com>
Date: Mon, 30 Jan 2017 20:11:14 -0800
To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments-payment-apps-api/issues/99/276270607@github.com>

@marcoscaceres -- if you're willing to bind payment methods to origins so tightly, then we don't need an API at all here. What you've described is the way web payments work today. What you've described is what we're trying to fix.

-- 
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-payment-apps-api/issues/99#issuecomment-276270607

Received on Tuesday, 31 January 2017 04:12:15 UTC