• Wednesday, June 10, 2020

9:00pm PST time. Update: We now have a handle on the credit card issue that some of our customers are reporting. This issue is only affecting U.S. based customers that are using the Transnational gateway and have the credit card vault option turned on. It appears that Transnational added a new parameter last night to the “return response” our software gets after a transaction is approved by their gateway.  Note that this only occurs if that transactions is using a saved credit cards, or if the option to save a new credit card is turned on.


We are currently working to develop an updated gateway.dll file that will support the changes made by Transnational. We expect to have that ready by the morning U.S. time for the following releases…

  • Version 16.0
  • Version 18.2
  • Version 19.0
  • Version 19.2

 If you are affected by this issue, and are using a version that is not listed, please contact us right away so we can create an updated file for you.

We understand the urgency of getting this issue resolved and our team is working around the clock to resolve this issue ASAP.

1:00pm PST time. It appears that our gateway provider experienced some issues this am. Some users are reporting that things are back to normal. If you are experiencing any issues, please create a ticket with a screenshot of your response log so that we can work with their engineers to determine the resolution. We sincerely apologize for this inconvenience.