New answers tagged

0

As said by anthonyryan1, it is required for American Express. So either you ask for/require this information only for American Express (which would mean you would either have to ask the user for the card type or start by letting them input the card number and then asking for the rest, or you disable the field if you see it's not required once a Non-Amex card ...


0

While you're correct that Visa and MasterCard do not validate this information, that's not true of all credit card providers. American Express actually does validate the "Name" field if you collect it as a merchant and by not collecting it you're more likely to have legitimate payments declined with this card.


5

Stick to conventions and consistency This is really simple: if user is charged on day 5 of the month, he should be charged on day 5 next month. Most users plan in anticipation and they know that every fifth day of the month they will be charged for a service. Otherwise, see what would happen January 5 February 4 March 5 April 4 May 4 June 3 July 3 ...


0

According to Dr. Math there are 30.42 days in an average month so you'd be "safe" rounding down to 30. :-) That aside, 30 days seems like a fair and intuitive number to use for most people. From a practical standpoint it's usually easier for a programmer to deal with too. Of course, whoever inserts the data into a datastore would be wise to use a reliable ...


4

You don't need to over think this. Unless there are regulatory constraints it can be whatever you want it to be and your users will take it as corporate policy. (By the way is there existing corporate policy relating to the definition of a month in other areas? If so leverage those decisions.) If you want to be thorough, and have the time and resources, you ...



Top 50 recent answers are included