Re: [webpayments] Should we expose status change events in the browser API? (#41)

> Are there use cases where listening to payment request processing events are useful to the payee's software?

I'm asserting that the current events, which are shippingaddresschange and shippingoptionchange, should be done through a different verifiable claims API. If these are removed, there are no events that are left in the requestPayment API, which would raise the question if there are /any/ events that are worth listening to.

Reply to this email directly or view it on GitHub:

Received on Wednesday, 16 December 2015 06:17:35 UTC