Notifications
Announcements
No record found.
Unable to process Credit Cards with 2020 as the Credit Card Expiration date. Any help appreciated
*This post is locked for comments
I seem to recall this being associated with a limitation on the processor side not RMS are you possibly using a third party processor like Heartland for example and not using the RMS application electronic draft capture? I have tested this on my environment and can enter 2020 and higher without issue. I thought that may help you.
I know this is a limitation of some third party software like PC Charge. There is a setting in PC Charge for the highest allowable expiration date. Anything over that date it automatically declines.
It appears the FREEMAN response was accurate yet you've given yourself the suggested answer and are asking for the verification also Ed? It's irrelevant if it's PC charge or Heartland. What is relevant is that it isn't RMS. Which is what I believe FREEMAN not you suggested. Thanks [tag:justsayin].
Dynamics101:
I know you are new here. But a SUGGESTED Answer means just that. We don't know the answer unless the poster tells us what works. ALSO this is a RMS forum, not a AX or CRM or any other forum. So we assume the person is using RMS as there system unless they tell us otherwise. Which BCB1633 did not say which system, so we have to assume RMS.
Furthermore: PC Charge is a middleware software and Heartland is a Merchant Processor. 2 Different things, Do your homework before you critize someone that is FREELY giving advice to people.
Would you be so kind as to update the status of this question for us please? Was the issue determined to be linked to the PC Charge middle ware you were using or was it associated with the Heartland Processor as Mr. Freeman suggested sir as both answers are accurate and would be beneficial to anyone else who may encounter this issue. Thank you.
I have a customer who claims they are unable to process credit cards of various types with an expiration date of 2020. They are not using any middle ware and are swiping the cards.
However, if they modify the expiration date manually to 2019 - the card processes as expected. I have contacted the merchant processor and they claim they have no control over the expiration date limitation - not does RMS.
Since the cards were swiped from a mag stripe reader - this also rules out the Pin Pad.
I'm not finding any answers - anyone with other possible suggestions are welcome.
Has anyone found a solution to this? We had this problem recently with a card that was entered manually. (not swiped) We use Mercury with the RMS integrated processing. We were able to get it to go through by changing the expiration to 2019.
We manually enter the full date with a four digit year for 2020, for example 02/2020 and this works.
Interesting, I thought RMS would only take the expiration date as a 4 digit number. I just tried it with a 09/2016 expiration and it worked fine. Unfortunately I don't have a card with a 2020 expiration I can test but I trust that will work too. Thanks for the info.
If on the Maintenance plan, log into CustomerSource and upgrade to the latest version of RMS, 2.0.2022 fixes the problem. https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;3096600
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 Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
