Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8)

How a payment app announces its capabilities is distinct from how a browser learns about it. I think there are a set of capabilities like that that have nothing to do with paymentRequest API and therefore should be dealt with separately. 

The way that one registers a payment app with some other software entity that wants to use the HTTP API will likely be different. But the way the payment app announces its capabilities would likely be the same, hence the desire to factor that out.

Ian

---
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/8#issuecomment-212987085