Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76)

> it means that the payment method ecosystem will struggle to scale since people will have to write lots of payment app specific code

I would consider this an argument in favor of standardization. If we standardize a mechanism to ask the payee for a new updated payment request via HTTP (which sounds like something we're talking about doing anyway in the HTTP API) then all that would be required in the browser API is a standard place to provide the callback URL.

I propose that we leave this out until we can demonstrate how it will be used (perhaps in conjunction with the HTTP API) and the value of standardizing it. It's a very minor change to the browser API spec if we do choose to add it.

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