Payware Connect Communication Error

Q - We are using Payware Connect for credit card processing.  We have seen the below credit card processing error message a few times today. We do not recall seeing this particular error message before. See sample screen below.  What caused it?

A - This is a typical Payware Connect Communication Error.  It can happen when Payware Connect servers are not available for some reason (e.g. high network traffic or server overload.)  The typical error messages you will get are as follows:

• Communication error: java.net.ConnectException: Connection refused: connect
• ERROR: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  

Another type of error message you can get is as follows:

• E:System.Net.WebException: The underlying connection was closed: An unexpected error: occured on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
  

These types of errors are random and typically can last a few minutes and then go away.  If the errors last for an extended period of time, please call your credit card merchant services provider or Payware Connect tech support to verify.

• Related Articles

• Error with Payware Connect - The remote certificate is invalid according to the validation procedure

  Release Date: 12/15/2017 Q - We started getting the following error on certain workstations yesterday when trying to pre-authorize a credit card with Payware Connect. Originally it was on the remote server, where some users worked and some didn't. We ...

• How to Handle and Prevent Credit Card Duplicate Charges

  Release Date: 08/31/2018 How Did Credit Card Duplicate Charges Happen? Most of the time, duplicate credit card charges are caused by network (Internet) error. Elliott online credit card processing utilizes Payware Connect as the payment gateway. If ...

• Payware PC Server Actively Refuses Credit Card Transaction

  Q: When I process a credit card transaction in Elliott, I receive a message indicating the server is actively refusing the network traffic connection. As a result, the credit card processing fails. But if I go to the Payware PC credit card server, I ...

• I Receive "A call to SSPI failed, see inner exception" Message During Credit Card Processing

  Q - I received the following error message when I tried to process a credit card transaction in Elliott: A call to SSPI failed, see inner exception. See the following sample screen: All of our users are continuing to receive this error. But, ...

• Credit Card Processing Error: Chk Viawarp For Dupl

  Q - In A/R -> Processing -> Credit Card Trx Handle, at field "21. Approval No," I press F4 to interface with the credit card payment gateway server, then I receive the message "Credit: AP Error: Chk Viawarp For Dupl." See examples below: When I go to ...