Re: [browser-payment-api] Add section on Extensibility (#44)

Ahh!  As it turns out I have been working on this.  It is pretty straightforward.  We will supply a skeletal payment app that communicates with the test management system's server.  Custom code on the server will evaluate the messages that are passed to the payment app from the user agent to ensure the messages adhere to the structure that was input.  So we can evaluate the basic parameters, and also ensure that the data passed through is untouched. 

A separate communication channel from the test case to the server (web sockets and service worker) will send /down/ the success criteria, and will receive /up/ a message from the server indicating the success or failure of the evaluation.  

---
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/44#issuecomment-197866077