Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59)

 I'd like to add a few data points to the ongoing discussion;

1. As @Krystosterone states [here](https://github.com/w3c/payment-request/issues/753#issuecomment-416292970), in the EU, differential pricing is now prohibited, for the UK this is as of January 2018, see this [article](https://www.moneysavingexpert.com/news/2018/01/cards-fees-to-be-banned-from-saturday/)

2. Whilst differential pricing for cards (and hence in basic-card spec) is no longer a requirement in the UK/EU, the ability to deliver differential pricing between payment methods I believe is still a valid use case.

3. Given the above restriction, I can vouch that certain merchants (specifically in the UK, my home country) have adopted a revised approach of simply not accepting certain types of card. Therefore I believe that filtering based on a deeper understanding than just network is still a requirement. (I attach a screen snip of one such payment process excluding retail credit cards)

![image](https://user-images.githubusercontent.com/17925307/46372274-97d27380-c682-11e8-9b81-4bd5d9478c5e.png)

Whilst I appreciate the implementation difficulties pertaining to accurate information regarding card types, I wanted to reaffirm the requirement, even if we choose to deprioritise and remove from this release. 

I suggest that if we do remove the capability from basic-card that we consider adding guidance to the Developer FAQ that Ian maintains.


-- 
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/payment-method-basic-card/issues/59#issuecomment-426405930