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

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, unfortunately, this message is not very clear.  So what's happening?

A - Yes, we agree this message is not very clear. Unfortunately, we are relying on the lower layer implementation by merchant payment gateway software -- in this case, Payware PC -- to return the proper message so we can inform our users about what's happening.

If you look at the SIMEVENT.LOG in \Elliott7 root directory (if you are running V7), or \Elliott7\bin folder (if you are running V8), you can locate the following related entries:

<RESPONSE><TERMINATION_STATUS>NOT_PROCESSED</TERMINATION_STATUS><RESULT>ERROR</RESULT><RESULT_CODE>55</RESULT_CODE><TROUTD>0</TROUTD><RESPONSE_TEXT>A call to SSPI failed, see inner exception.</RESPONSE_TEXT><ERRORS /><TRANS_AMOUNT>359.06</TRANS_AMOUNT></RESPONSE>

This is a log file created by Payware for us to debug.  As you can see, there's no additional detail information we can trace.  To be fair, this is actually the message from Microsoft .Net.  Payware PC simply returns the .Net message, which they send on to Elliott.

After further investigation to your Payware PC server and discussion with Payware PC tech support, we found problem is caused by Windows update on 5/12/15 with KB3061518 and possible KB3068708 on your Payware PC server. You need to remove these two updates.  The root of the problem is the Windows update phase out support of 512 bytes encryption key which Payware PC rely on.

When we ask Payware PC what is their plan to migrate to higher level encryption key support with Payware PC, they simply said that they will no longer support Payware PC after Oct 15, 2015.  At this moment, we advise all of our Elliott users that use credit card processing migrate from Payware PC to Payware Connect. 




    • Related Articles

    • Emailing PDF with SSPI Failed After Online Charging Using Credit Card

      Q - I processed an order and charged a credit card in Elliott. Then I printed the invoice and emailed the PDF file to my customer. I received the following error message: ERROR: A call to SSPI failed, see inner exception. The client and server cannot ...

    • Credit Card Transaction Time Out

      Q - When I process a credit card transaction in Elliott, I receive a message window with the title "Finished Transaction Status" and the detail message like followings: E:System.Net.WebException: The underlying connection was closed: A connection ...

    • 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 ...

    • 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 ...

    • Credit Card Payments in Elliott but Not in Payment Gateway

      Q - Yesterday, we processed two credit card payments through A/R Credit Transaction Handle. They were declined. Today, when we reconciled the A/R Credit Card Log from yesterday with the Payment Gateway (Solupay), they didn't match. The difference is ...