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

Am I correct that what is being proposed is relevant to the data schema of the payment request only?
i.e. The proposal is to have SOME mechanism to link a payment request to an invoice but not to define any invoice delivery mechanism.

Assuming this is a standard data element that we define in the payment request, do we go so far as to define what that data must look like, and if we say its a URL what that URL should point to?

I am inclined to say that standardizing anything more than a named data element in the request that could be of any type (URL, unique id), is going beyond our scope, although I'd like to hear other opinions on this.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/60#issuecomment-177942997