When inputting a credit card with an expiration date of 2020 or higher, the 2.0 POS will not take it. Is there a setting that can be changed or a patch to the system?
*This post is locked for comments
Can you tell us what version of RMS you are running. There was a patch for tsys internal credit card processing with 2.0.200
I have experienced this same problem.
We run the credit card transaction through a standard terminal sitting next to the POS and use the credit card tender type...
We swipe the card in the POS, tab to the expiration date, input the 4 digit number, and input the authorization code once it clears the separate credit card terminal...
Does Anyone have a solution for this?
I have looked into this problem and MS has this solution which is no help: https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?WTNTZSMNWUKNTMMYVTQUUXNNZOUKYPPPTUVLMNUZMLLTZXZR
are you made any customization on tender form
if you did try to disable tender trigger.
It is 2.0.200. One user tested and found that instead of putting 5/20 in, we could put in 5/2020. This seemed to stick.
I tried to input 5/2020 and different input to see if I could get one to work and did not...
I did check and we are currently running RMS 2.0.0126.
Does anyone know what I need to update to get this to work properly?
If I update to CU5?
Thanks for the help Ramy Rashad and userBB!
working at any version try 127 or higher
Thanks Ramy Rashad!
I will try and report back for future reference.
Ramy is correct, this is not an issue known to occur within RMS. It is typically associated with customers using third party for processing that are not supported (for example heartland) or customers who do not use electronic draft capture from within RMS, but fault RMS when it doesn't work. Customers who plan to continue processing credit cards using RMS after October 2015 may want to think long and hard about being minimally on RMS 2.0.2000, because that version meets the upcoming PCI requirement changes made by the banking industry not Microsoft. Retailers who fail to be compliant may anticipate being fined, charged higher processing fees or may have their ability to process credit cards at all revoked... until they are compliant. I don't believe it's optional and I do not recommend anyone wait until October to find out!
I updated to RMS 2.0.2000 and it is still NOT working...
I receive the error: Validation Error 322: An invalid credit card expiration date was detected.
I went into RMS Administrator and the Current Database Version is 2.06
Does anyone have any idea of the source of the problem?
I have tried inputting the expiration date as:
122032
1232
12/32
Any help / ideas are appreciated!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
