@rsolomakhin said: > Keep in mind this becomes an issue only when the merchant specifies something like "visa/debit" as the payment method. In the latest editor's draft of the specification, I see that these payment methods have been replaced with the single `basic-card` payment method. The `visa` and `debit` parts are moved into the method specific data section. Personally, I think this is a great improvement, and it makes my implementation much tidier than before. @rsolomakhin said: > By the way, I don't think card type should be removed. If this field is in the specification, I feel it's important that merchants can trust that it will work. If most basic card payment apps ignore this field, because it is tricky to implement, then we could get into the situation where merchants too will stay away from using this field, since it usually does not work. Then we end up with a piece of specification that nobody uses, which is not very cool. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-methods-card/issues/19#issuecomment-257552230
Received on Tuesday, 1 November 2016 12:16:20 UTC