Question #001

Question #001
Credit Card Expiration Date

Have any of you been getting credit cards with expiration dates beyond 2019?

flowerSoft would flag those cards as expired and ask you if you want to update the card.  If you answer “yes”, flowerSoft will allow you to continue.

I have a customer who has gotten 2 such cards, one expiring on 2020 and the other one on 2021!

I’ve never heard of credit cards expiring 9 years from today.  That’s crazy if true.

This all goes back to the Y2K problem of 1999.  On dates with 2-digit years (such as the credit card expiration date) I had to come up with a century mark (a 2-digit number) which demarcated the 20th and 21st centuries.  The number I chose was 20.  So an expiration date of 12/19 would be OK because flowerSoft considers any 2-digit year before 20 be in the 21st century.  So, an expiration date of 12/19 would be considered to be in the year 2019, while and expiration date of 12/20 would be considered to be in 1920.  Hence, flowerSoft proclaims that the card is expired.

The only place flowerSoft uses a 2-digit year is in the expiration date field.  All other date fields have 4-digit years and there is no problem with those dates.

So, if credit cards are now going to have expiration dates beyond 2019, I’ll change the 20 to 25 or 30.  That is an easy fix.  The only thing it would affect is a birthdate.  Some one born in 1931 would be considered to be 1-year-old by flowerSoft.  Not a big problem since the only place flowerSoft asks for a birth date is in the employee file and I don’t think many of you have employees born in the 1920’s or 30’s.

So, I’d like to have your input as to what year should I use for the century mark, 25 or 30.  Please let me know by voting in the poll below.


4 thoughts on “Question #001

  1. As it is now 2012, if one were to purge all credit cards that have expired, or at least ones older that 2000, then no century mark is needed as all cards with 04/12 or less would be expired.


    1. That is not the problem. If a card is truly expired, flowerSoft will flag it as such.
      The problem is that is a new credit card has an expiration date of 12/20 for example, flowerSoft will think it is an expired credit card.
      Now, 2020 is 8 years from now. I was expecting this problem to appear around 2016 or so, not now.
      Yet, the change is an easy one to make. I just wanted opinions on whether to use 25 or 30.
      I’m leaning towards 30, maybe even higher, because flowerSoft does not use 2-digit years anywhere except in the credit card expiration field.


  2. I see no problem with either 25 or 30. Just that you would probably have to deal with it again 5 years sooner with 25. Right? We have not had any issues with this. I don’t favor purging expired cards, because so many cards just get new expiration dates and keep the same number.


  3. Yes, the purging would not solve the problem.
    I think I’m going to change the 20 to50 and do some testing.
    Like I said, flowerSoft does not use 2-digit years anywhere but in the credit card expiration date.
    Setting it to 50 would stop that problem from happening again at least for another 30 years.


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s