Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11)

@sideshowbarker,

Thanks for getting some input. 

> “That poll is super misleading… The alternatives here are URLs vs simple strings”

Sorry it is read that way. We have three options and I thought it reasonable to list
them all. But I can see the case for organizing the question in two parts: URL or not?
If URL, then registry or not?

> “Everyone needs to understand that a new token will only become supported by shipping a new version of a browser, I don’t see how else this would work. So having com.visa.foo is cute, but kind of pointless too”

I'm not sure I understand that point. I believe that our design does not require a browser upgrade in order for a merchant and user to be able to use a new payment method.

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/11#issuecomment-213499564