We discussed whether or not the API should support a "chatty" interface early on in the WG's work. The decision was that we would stick to a simple request/response interface for now to keep it simple and because there is no guarantee that a browser can even offer such an interface to an external payment app (especially in a resource constricted environment). Payment apps and websites can use the existing interface to establish another out of band channel if that is required. E.g. The payment method can define a mechanism like a callback URL that the app will use to establish a channel with the merchant's system. -- 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/494#issuecomment-291031243
Received on Monday, 3 April 2017 01:37:47 UTC