Re: [w3c/browser-payment-api] How can short payment method identifiers be successful (#123)

Hmm.  The payment method identifier "visa" would obviously need to map to a specific set of requirements.   You are correct that there are a plethora of payment methods that might map into the generic identifier "visa".  The WG would need to identify the specific requirements for the one that is named "visa".  

In reality, there are going to be a bazillion payment methods, identified by URIs.  As a merchant, my payment processor is going to tell me which identifiers I should use based upon what *they* accept.  If we were smart, we would allow a payment method "profile" - a syntax that would magically dereference into a collection of accepted payment methods.  Then let the market sort out a bunch of profiles that are interesting.

---
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/123#issuecomment-206636440