Chrome validates basic card data before sending it to the merchant website. We perform Luhn check on the credit card number, for example. We also check that the expiration date is not the past. If validation fails, Chrome UI prompts the user to correct the errors. (In some cases, Chrome can also validate the CVC against the issuing bank. This capability may be hard to implement for some user agents.) Therefore, I don't know whether we should make validation into a hard requirement. I would prefer it, certainly, but I will not block on it. Let's operate based on the lowest common denominator for now and try to gradually raise the bar for ourselves. -- 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/webpayments-methods-card/issues/26#issuecomment-290093053
Received on Wednesday, 29 March 2017 13:41:31 UTC