Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30)

> Matt referred me to this long list of subtypes:
> https://www.bindb.com/bin-list.html

I think this page makes the problem look much worse than it really is. There are many different issuing banks out there in addition to dual branded cards (e.g. United Airlines' Chase Visa Card). But this is the whole value add of the card network - by and large, if you're in the network, things work.

I'd still like to better understand real world use cases and how prevalent those use cases are before adding the complexity of a "not supported" type into the API.

---
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/30#issuecomment-203107094