[w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)

How would we extend the invoke of a payment app with other things than HTTP (like native messaging)? In the spec or outside (i.e. keep it a UA specific native API)? Should we give an example of such an invocation?

---
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/webpayments/issues/156