Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60)


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.


Reply to this email directly or view it on GitHub:

Received on Wednesday, 10 February 2016 04:14:36 UTC