- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Mon, 14 Mar 2016 04:58:37 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Monday, 14 March 2016 11:59:05 UTC
The full discussion from the old thread is useful context for anyone picking this up. The issue centers around a balance of payer privacy (can't tell the payee up front all the supported payment methods and currencies) with flexibility (the ability to request payment in a variety of currencies and to offer different prices and currencies depending on the payment method). The pragmatic approach may be to start simple and only support a single currency and price and to let the API evolve as we get more input from stakeholders on HOW they want this to work. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/54#issuecomment-196278129
Received on Monday, 14 March 2016 11:59:05 UTC