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. 

Credit Card Processing

  1. How to Process a Force Credit Card Transaction?
  2. Credit Card Processing Frequently Asked Questions
  3. Payware PC Server Actively Refuses Credit Card Transaction
  4. Does Elliott Encrypt Credit Card Number in The Database?
  5. How to Reverse Credit Card Sales?
  6. Credit Card Transaction Time Out
  7. Procedure to Process Credit Card by Reference ID
  8. How to Charge a Credit Card If Pre-Authorized for the Wrong Customer
  9. Payware Connect Communication Error
  10. What Happens if Credit Card PreAuth Is Not Followed by Completion?
  11. Credit Card Processing Error: Chk Viawarp For Dupl
  12. What Does Error Code 2029999 Mean in Payware Connect SIMEvent.Log File?
  13. I Receive "A call to SSPI failed, see inner exception" Message During Credit Card Processing
  14. Credit Card Payments in Elliott but Not in Payment Gateway
  15. Feature - Support for Verifone Point Devices with Card Chip Technology
  16. Error with Payware Connect - The remote certificate is invalid according to the validation procedure
  17. How to Find Orders That Have Been Pre-Authorized for Credit Card Charge
  18. Feature - Online Credit Card Interface Level 2 Support
  19. How to Handle and Prevent Credit Card Duplicate Charges
  20. Invalid Tran Counter [99...99] with POINT Interface When Charging a Credit Card
  21. How to Set Up MX915 POS Device for Static Network IP Address
  22. Receive "Input parameter INVOICE assigned invalid value" with POS Credit Card Charge
  23. How to Reprint a Credit Card Receipt
  24. Does Elliott Support Credit Card Pre-Authorization Transactions?
  25. What Is the Credit Card Authorization Member Field for?
  26. Selling Non-Approved Items Can Cause Credit Card Processing TERM ID ERROR

Feedback and Knowledge Base