Distribution, Manufacturing, and Internet Modules

[ebjelovs]

What version(s) of PC Charge are PA-DSS compliant?

There has been a bit of confusion regarding this topic lately, in part fed by recent communications from Wells Fargo and Bank of America credit card services to PC Charge customers. Sage and VeriFone (the providers of PC Charge) have been working together to help clear the confusion, and this post is part of that clarification effort.

Version 5.8.3 of PC Charge IS MOST DEFINITELY certified as compliant by the PCI Council, and I have a copy of a letter sent to VeriFone from the PCI Council that verifies this. In fact, because 5.8.3 is compliant is why that version was selected by the MAS team to be autoshipped to our Sage ERP MAS 90 and 200 customers with their version 4.4 shipments.  It is also available for download from the Sage ERP MAS 90 and 200 Sage Online.

At this point I do not know if Wells Fargo will be sending a corrected communication to PC Charge customers, although VeriFone has requested that they do so. Meanwhile, versions 5.9.1 and 5.9.2 are currently undergoing quality assurance compatibility testing with the MAS team, and, as always, once they have been verified as compatible, the Compatibility Matrix will be updated to reflect that change in status. However, there is no need to rush to upgrade to any newer version at this time because version 5.8.3 is PA-DSS Compliant.

There have been some questions about the difference between PABP 1.4 certification and PA-DSS 1.2 certification as stated on the PCI Council's website. As I understand it, PABP is the certification standard used prior to PA-DSS. As such, it has an Expiry Date in December of 2010, making it acceptable for new deployments until that time. So, versions 5.8.1 and 5.8.2 of PC Charge are also still acceptable for use until the expiry date.

[DandyDon]

Is Mas 90 4.2 compliant with PC Charge 5.8.3?

 We are on 5.7.1. If we upgrade via Verifone online, will we have any issues?

[ebjelovs]

DandyDon,

No.  Running a compliant version of PCCharge does not automatically make the version of MAS 90 or 200 that you are running also compliant. This is, unfortunately, a common compliance misconception. The version of PCCharge you are running is not the only component of compliance that you need to be concerned with; Sage ERP MAS 90 and 200 is also required to be PA-DSS compliant in order to continue processing according to compliance standards.  Version 4.2 is NOT compliant with PA-DSS standards, and unfortunately, there is nothing that can be done to make it compliant. 

 If you are currently running version 4.2 and want to continue to process credit card transactions, you will need to upgrade to either version 4.30.0.18 or 4.40.0.1 in order to be running on a PA-DSS compliant version of your Sage ERP product.  You can find much more information about PA-DSS compliance as it relates to Sage ERP MAS 90 and 200 at this link:  http://www.sagemasinfo.com/M90PCI/  

[DRSS]

Hello Erika,

Does 4.30.18 work with PC Charge 5.8.3 -  the support matrix says 5.71-5.8.2 ?

[DandyDon]

As luck would have it, we happen to be a week or two (or three!) from 4.4 upgrade. Our reseller is coming in tomorrow to do a service pack on 4.2 and upgrade PC Charge and we should be able to process credit cards until 4.4 is live. We somehow missed the notification earlier in the month about PA-DSS.

[ebjelovs]

DRSS,

Yes, I have confirmed with our quality assurance team that PCCharge version 5.8.3 has been successfully tested with all of the PA-DSS compliant versions of Sage ERP MAS 90 and 200 and Extended Enterprise Suite.  We will update the info in the supported matrix document to reflect that when we re-publish the document.  Thanks for the timely question!

[DRSS]

Thanks Erika!

[Broadfoot]

We have a client that is upgrading from MAS 90 4.1 to 4.4 and has recently upgraded PCCharge from 5.7.1h to 5.8.3.  They are doing this on a new 2008 server.  I understand that PCCharge 5.8.3 is not compatible with Windows Server 2008.  Verifone shows 5.9.1 as being the first version that is.  Is 5.9.1 or 2 available from Sage?  What is the recommended solution in this situation?

Thanks,

John Broadfoot

[Broadfoot]

For anyone else that has this issue, Sage was able to provide version 5.9.2.