Recent Features
| |||||||||||||
This is strange...This is strange...Posted Dec 10, 2011 6:51 UTC (Sat) by khim (subscriber, #9252)In reply to: Google Authenticator for multi-factor authentication - credit cards by giraffedata Parent article: Google Authenticator for multi-factor authentication
I used to successfully submit charges all the time with made up expiration dates. How can you do that? I've had card from a few banks, but they all reject transactions with incorrect expiration dates (at least electronic ones). This is PITA when card expires: if order is placed with old expiration date and is not shipped before it's annulled and new one is issued then you need to go to the web site and change the data. And not all sites provide nice interface to do that...
(Log in to post comments)
This is strange... Posted Dec 10, 2011 15:16 UTC (Sat) by corbet (editor, #1) [Link] Our experience as a credit card merchant suggests that banks differ widely in the practices they apply. For a lot of them, if you have a number, that's all they care about. We routinely get emails from people who realize they put in the wrong name or expiration date, but the charges go through just fine. Other banks insist on correct address information and will turn down charges because they don't like the position of the moon that night.
expiration date in credit card authentication Posted Dec 10, 2011 18:02 UTC (Sat) by giraffedata (subscriber, #1954) [Link] It doesn't surprise me that for some charges the expiration date has to be right. There's a lot of diversity in this area. But I know that traditionally, the expiration date wasn't part of authentication. When I did it, it was in 1999 using a traditional merchant credit card terminal. Banking computing standards often take a decade to make even a trivial change because regulators are very careful. I'm pretty sure that this terminal wasn't even capable of transmitting the expiration date I typed to its partner.
|
|||||||||||||