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

I understand this requirement as a motivator to have a separate message and API specifications for the payment request.

So, while the payment request is not (in legal terms) an invoice, it is a piece of data that could be embedded in an email, sent via an API call or passed via any number of mechanisms to a debtor who can then attempt to make the payment.

I can imagine a QR code that is a URL pointing to the payment request (in the form of a JSON document) being printed on a receipt for example...

This will only work if the format is standardized and we explicitly choose to accommodate this use case and consider how the data schema needs to be designed to do so. _(Example: If the payment request is embedded in an email it must provide a URL to which the debtor submits a response)_

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