Sage 100

I have a client on 4.50 (need to double check the PU) and they have one transaction where they're getting: The credit card transaction request failed. The payment server returned a result of EXPIRED CARD The card has an expiration of 1/2015. Has anyone else encountered this recently?

Are they sure the Exp is right? Had a client say the same thing to me but we found out that the employee had changed the date - they never got the correct date from the customer. ( card was really expired)

Is this PC Charge? Isn't there a date (MM.YY) in setup after which the cards are not considered valid yet? Was caught on this once a few years back. Had to bump the expiration cutoff forward.

Clarification: Setup is on the PC Charge side. If this is Sage Payments back end then, well, never mind...

It's SPS. I asked the question about the expiration date and they say it's correct.

+1 @WayneSchulz

They"" as in the MAS user? Or ""they"" as in they have actually contacted the customer and confirmed it? Just because the expiration date is in MAS, it doesn't mean it is correct.

Maybe worth a shot re-keying the exp. date in MAS in case of a data-write issue.

The MAS user (competent, fairly technical person who usually doesn't BS me) says he verified it with their customer.

They could also look on the virtual terminal to see what it shows for the expiration date??

I did have another client change the exp date so many times that it didn't work in MAS but it worked on VT. So I would see like @ThereseLogeais said and/or try it on VT to see if it will go through.

I just sent them a not about trying to rekey the expiration date and about trying it on Virtual Terminal. I'll let everyone know what I find out. Thanks!