Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286)

> Note that I disagree this is out of scope. The payment app spec should not be placing requirements on this spec that would create normative changes to the API. Throwing an event seems like a really easy way to ensure that anyone who cares can know that a transaction completed.

As I understand it, the event is caught by the payment app right? Therefor that event needs to be defined in the payment apps spec.

In that section of the *Payment Apps* spec it would refer to the appropriate point in the `complete()` algorithm definition of the *this* spec [1] when the browser MAY/SHOULD/MUST emit an event to the payment app.

[1] https://w3c.github.io/browser-payment-api/#complete

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/286#issuecomment-252023559