- From: ianbjacobs <notifications@github.com>
- Date: Tue, 09 Feb 2016 20:14:02 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
Received on Wednesday, 10 February 2016 04:14:36 UTC
@adrianhopebailie, I think we should establish: * Is there a minimal merchant use case that we must address to get adoption of the API? * If so, what's the minimal information required to achieve it? For example, if merchants say to us something like "We can't use the API unless there's a way to associate an offer with a receipt" then we should listen carefully to that. While it is not in our scope to create standards for digital receipts, the merchant may need information to link two "events"; I think this is what you are saying and it sounds reasonable, but we need to ground it in merchant needs IMO. Ian --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/60#issuecomment-182187934
Received on Wednesday, 10 February 2016 04:14:36 UTC