W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 2016

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

From: Rouslan Solomakhin <notifications@github.com>
Date: Tue, 09 Feb 2016 16:13:59 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/60/182142802@github.com>
For my sake as a non-native English speaker, let's define a couple of terms. It sounds like @vkuntz is talking about something like a _receipt_.

> "A written or printed statement acknowledging that something has been paid for."

This is something that the merchant provides to the user after the transaction has been complete. I can imagine this happening through the complete() method:

var receipt = {"items": [...], "amount": "35.00", "currencyCode": "USD"};
payment.complete(true, receipt);

In contrast, an _invoice_ is much closer to the definition of a payment request.

> "A list of goods sent or services provided, with a statement of the sum due for these; a bill."

The browser has this information and may even store it. For example, this is similar to "Downloads" page in Chrome.

@vkuntz, which one did you have in mind?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 10 February 2016 00:14:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC