Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)

> @marcoscaceres the whole purpose of modifiers was to preserve user privacy. It's possible that the feature, as specc'd has gotten very stale, and needs some love but I don't think we want to throw it out entirely.

Ok, but the problem remains that we can't distinguish between card types (only networks). So it makes the feature unreliable.  

While it protects privacy, it's kinda useless because we can't guarantee that the total shown to the user is the total they will be charged. That seems like a deal breaker to me. 

The core of the problem is that BIN databases are quite unreliable (~10% error rate). Our user research is telling us users can't reliably differentiate between their debit and credit cards, so this puts us in a bad position (where both users and BIN data still result in unacceptable error rates).

So, the only sensible solution seems to be to pass a card's BIN number back to the merchant, and for them to figure out what kind of card it is. 

Open to other suggestions here, but, for basic card, this is a show stopper.    

-- 
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-request/issues/753#issuecomment-413092104