Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Caroline Brichford]

?We are using NAV 2009R2 and just switched over to ChargeLogic for our credit card processing.  We were just informed that the processors and the payment providers are all switching over to a new security TLS V1.2 that is not supported by our NAV 2009R2 version since it uses a .NET 3.5.   Our classic client does not use the .NET so the change to upgrade the security is not an issue with it.  Our web services integration with our web portal is also impacted by the change.  Chargelogic just announced this change in January to us and have given us till the end of February to come up with and implement a solution.

Upgrading NAV is planned for 2019, so that is not an option at this time. 

Is anyone else running into this issue?  What have you come up with as reasonable solutions?  I have been presented 3 solutions, two that are very temporary and have a 80% chance to actually work and be PCI compliant and the third is more permanent but we don’t have enough time to implement before the February 28th deadline.  

——————————
Caroline Brichford
Furukawa Rock Drill USA
Kent OH
——————————

[Val Gameiro]

?I’m not familiar with ChargeLogic so tis may not be useful, but is there a manual way of processing those transactions? Maybe their offer a web interface and you can hand key things in until you have time to implement a more permanent solution?

Another thought is, can you implement SSL instead of TLS?
Walkthrough: Configuring Web Services to Use SSL

Microsoft		remove preview
Walkthrough: Configuring Web Services to Use SSL Microsoft Dynamics NAV supports SSL authentication. The server authenticates itself to the client, but the client does not authenticate itself to the server. When the Web service client connects to the Microsoft Dynamics NAV Business Web Services server, the server replies by sending its digital certificate to the client. View this on Microsoft >

Sorry, wish I could be of more help!

——————————
Val Gameiro
Senior NAV Analyst
BPL Plasma Inc.
Austin, Texas
NAVUG Austin Chapter Leader
——————————
——————————————-

[Ted Johnston]

May not be germane, as it is not ChargeLogic, but it does involve TLS.

We use a custom designed CC interface to Payeezy (First Data). This was developed way back when Lanham dropped support for their credit card processing and we needed to find a solution quickly.

Our programming group developed a DLL that NAV can call which interacts with the credit card company.

Fast forward to last summer when we needed to update the DLL to support a new CC transaction for a special project. All they had to do was recompile the DLL that was called to the new .NET framework. No change to NAV was needed.

So, if ChargeLogic has a DLL that they call NAV, they should be able to just recompile that one DLL to support .NET and off you go. 

A cautionary tale (more background).
Last summer, we found out that Payeezy had already set and moved two “deadlines” for the transition. We were never notified by any of our CC chain. Shame on me for not regularly checking up on Payeezy to check. 

On Wednesday morning they finally stopped accepting non TLS1.2 transactions. I’m glad we were ready……..

——————————
Ted Johnston
IT Director
Streicher’s
Minneapolis MN
——————————
——————————————-

[Crystal Tollison]

?Hi Caroline,
Your post is timely. Just yesterday Chargelogic held a Partners webinar where they announce that Microsoft has release a patch for programs using .NET 3.5.

Ironically, Microsoft realized that they had issues with this .Net version and other programs much bigger than a few versions of NAV, CRM being the biggest in our world.  That seemed to have gotten their attention.

They have released a patch that can assist in most cases if you are using the RTC version of 2009.  This forum would not be the proper place to pass on the details.  Many ‘if’, ‘and’, or ‘but’s in the mix to responsibly try to transfer the knowledge here.

All Chargelogic Partners were contacted about this so I suggest you contact your VAR for additional information.  Good news is there is now hope!

——————————
Crystal Tollison
Consultant
ArcherPoint Inc.
Lawrenceville GA
——————————
——————————————-

[Karen Tran]

Hi Caroline,

TLS 1.2 is not a ChargeLogic update, but is a new version of transport layer security that is being mandated as the required method of secure communication by all payment processors. Although the PCI Standards Security Council has mandated June 30, 2018, as the deadline for being current on TLS 1.1 or 1.2, many payment processors are requiring that customers use TLS 1.2, and many have set their deadlines in advance of June. Your payment processor has issued a deadline of February 28, so that is the date with which you must comply in order to continue processing payments with your processor.

As was mentioned by @Crystal Tollison, we recently learned of a patch for customers using Dynamics NAV 2009 RTC that may make the change to TLS 1.2 easier than what was originally presented to you. Please reach out to your partner to explore the current available options.

ChargeLogic began communicating with our partners as early as April 2017 about changes regarding TLS 1.2. We did not have the payment processors deadlines at that time. We have been updating our partners with information as the payment processors notify us about their deadlines.

Let me know if you have additional questions.

——————————
Karen Tran
Director
ChargeLogic
Baltimore, MD 21209
443-279-1026
——————————
——————————————-