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


In terms of a concrete proposal, are you asking that the Browser API allows for;

1. The display of the obligation in the Browser UI
2. The production of a cryptographically signed invoice and that includes the obligation by the API
3. The automated delivery of this invoice to the payer as part of the process – do you think the payment application should be responsible for this or perhaps the payment mediator, or is it acceptable to just pass this back from the API to the merchant and make the merchant responsible for providing it? Would that not make it more likely for lost invoices?

Does all of this apply for transactions that are just an “Authorisation”? When is the obligation and invoice needed as part of such a process and what happens if the authorisation time’s out?

Reply to this email directly or view it on GitHub:

Received on Thursday, 25 February 2016 20:03:45 UTC