Hey Adrian, interesting question. A few thoughts: * Can you clarify use cases around this and how common those use cases are? I'm skeptical there is a real need for this. * This creates a rather strange implementation on the side of the merchant. It's the client that created the payment request, but now it's the server that is receiving certain change notifications? So now both the client and server have some sense of the paymentrequest state? I do not think I would want to implement such a system. * Technically, this is possible given the current paymentRequest API if both the merchant and the chosen payment app wanted to take advantage of it. But again, I'm not so sure this is a case we need to support. -Zach --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/76#issuecomment-178062089Received on Monday, 1 February 2016 16:45:09 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC