TSYS and Aloha update needed

[AlohaRoss]

Did you know that on July 31st many people who use Aloha EDC and you use a processor using the TSYS platform your credit cards may not work. Here is the story

There is a mandatory, industry-wide certificate update that should have been remotely done by your POS service provider by now. this needs to be done by July 31st. This is typically a simple and quick update but it's looking like you will need to contact your POS technician to make it happen. It's possible they already did it, since they have known it was coming.
Contact your POS [rovider to make sure you are on the SHA-2 certificate. If by chance your POS version is too old and cannot be updated at this time they can use a private certificate provided by TSYS
If EDC says visanet and you are not using Heartland, this effects you.

If you are are using any version of EDC below 7.X you will need this update. If you are under a support contract this should be a free update. The update cannot be run until you have settled your batchs. Best to do prior to open. Most Aloha version from 6.X and above can be updated very easy. For those of you still with ver 5.3, it will take a bit longer but you can also be updated. Lastly, if you are still using XP, its time to move to Windows 7. It is getting harder and harder to find Win7 32 bit machines online. For those with LPT hasps, adding the LPT card will be most likely need to be added. If your Hasp is the big white dongle on the back of your machine, this means you.

If you are not under a support contract of course this is going to cost you.


AlohaRoss

http://www.needaholahelp.com

3rd Party support

 

[MenulinkMan]

NCR has provided the following info:

"As of July 22nd, 2016, the processors have provided <NCR> with the following dates as to when they will no longer support SHA-1:

Vantive - Sept 18, 2016
Heartland - Oct 1, 2016
First Data - Nov 15, 2016
Elavon - Jan 1, 2017
TSYS - Jan 16, 2016
World Pay - Jan 17th, 2017
Chase/Paymentech - May 31, 2017

 

[AlohaRoss]

menulink,

so the emails 2 of the processors I work with are wrong. they have been warning all there clients this week that they have to have this upgrade by end of month. Dealer in there area has been updating all the sites to 12.3 over the past 45 days. Why the 2 so different sets of information

AlohaRoss

http://www.needaholahelp.com

3rd Party support

 

[MenulinkMan]

Not sure. Here is a copy of the data that was sent out..

Link to the data I received

 

[MenulinkMan]

Gah. I can't edit my last post.

2 of my resellers have stated that we needn't worry about being up to date by the 31st of this month, plus a former colleague of mine received the same info a week or so ago. I've got 100 or so of my sites on 6.* version of EDC, so if NCR's email is wrong, i'm going to have a bad next week....

Could be that SHA1 will work, but no longer supported by the processor for tech issues. So this way they are forcing people to upgrade to a higher security standard before the official cut off date. I mean, SHA 2 officially starts Monday(or Sunday..don't remember), but its not a hard cut off of SHA 1.

 

[PosGuyUS]

With the software we use, not EDC, my understanding is that if you are on Windows XP SP3, Windows 7, 8 or 10 you should be fine. That is because the certificates needed are in Windows, not our CC software. I would think it might be the same with EDC.

Each of the processors has been pushing these dates back over and over. Paymentech was supposed to change something in their security 2 years ago and caused a panic, I don't know if they ever did it.