How to Fix Sagepay Error Code 5999

Sagepay Error Code 5999 can be a frustrating issue for both merchants and customers attempting to process payments. This error is typically linked to transaction failures within the Sagepay system. Understanding its causes and implementing solutions can help in successfully resolving this issue, ensuring smoother payment processes in the future.

Causes of Sagepay Error Code 5999

Several factors can contribute to the occurrence of Error Code 5999 in Sagepay. It’s crucial to pinpoint the exact cause in your specific situation to apply the most effective solution.

Reason #1: Invalid Transaction Details

Incorrect or incomplete transaction details such as payment amount, account numbers, or expiration dates can trigger this error.

Reason #2: Communication Issues

Connectivity problems between your website/platform and the Sagepay server may cause transaction failures, presenting this error code.

Reason #3: Merchant Account Issues

Restrictions or issues with the merchant account used for transactions on Sagepay can lead to Error 5999, especially if the account is not properly set up or has been suspended.

Reason #4: Fraud Protection Triggers

Sagepay’s internal fraud prevention measures might flag a transaction as suspicious, resulting in Error 5999 while trying to process the payment.

Solutions for Sagepay Error Code 5999

To resolve Error Code 5999, follow the steps provided for each solution closely.

Solution #1: Verify Transaction Details

1. Check the transaction details inputted during the payment process. Ensure that all information is accurate and complete.
2. If you find any inaccuracies, correct them and attempt the transaction again.
3. Ensure that the card details, such as expiration date and CVV, are entered correctly.

Solution #2: Test Internet and Server Connectivity

1. Verify your internet connection to ensure it’s stable and fast enough to communicate with Sagepay’s servers.
2. Ping the Sagepay server from your server to test connectivity. Use a command-line tool and type ping sagepayserveraddress.com (replace sagepayserveraddress.com with the actual Sagepay server address).
3. If you experience connectivity issues, contact your internet service provider or IT support to resolve them before attempting the transaction again.

Solution #3: Review Your Merchant Account Status

1. Log into your Sagepay merchant account and check for any notifications or alerts.
2. If your account is suspended or has restrictions, contact Sagepay support directly to understand the reasons and remedy them.
3. Ensure that your merchant account is correctly set up for the types of transactions you are attempting.

Solution #4: Evaluate Fraud Protection Settings

1. Access the fraud prevention settings in your Sagepay account.
2. Review the rules and triggers that are currently set up. Adjust any settings that might be too restrictive for your typical transaction profile.
3. Test a transaction with the adjusted settings to see if the error persists. Make further adjustments as necessary.

Solution #5: Configure Sage Pay Server according to Required Specifications.

Step 1: Follow the Guide First, you need to follow the instructions in the Sage Pay Server Integration guide. I’ll give you the steps from the same below.

Step 2: Add Your IP Address Next, you need to tell Sage Pay your computer’s address, which is called an IP address. Here’s how to do it:

• Log in to your Sage Pay account here.
• Look for a section called “Valid IPs”.
• Click the “Add” button.
• A box will pop up asking for your IP address. If you don’t know it, you can find it by typing “What’s my IP” into Google.
• It will also ask for a “Subnet mask”. Just type in 255.255.255.000.
• Finally, it will ask for a “Description”. This can be any name you want.
• Click the “Add” button to finish.

Step 3: Check Your Firewall Make sure your computer’s firewall isn’t blocking certain “doors” that Sage Pay needs to use. These “doors” are called ports, and the ones Sage Pay needs are 80 and 443.

Step 4: Use the Right HTTPS Protocol When you send information to Sage Pay, you need to use a secure method called HTTPS. Make sure you’re using at least version 1.0 of a protocol called TLS. Sage Pay supports these versions of TLS:

• TLS1-AES-256-CBC-SHA
• TLS1-AES-128-CBC-SHA
• TLS1-DHE-DSS-RC4-SHA
• TLS1-DHE-DSS-AES-256-CBC-SHA
• TLS1-DHE-DSS-AES-128-CBC-SHA
• TLS1-DHE-RSA-AES-256-CBC-SHA
• TLS1-DHE-RSA-AES-128-CBC-SHA

Step 5: Include the Right HTTP Header When you send information to Sage Pay, you need to include a piece of information called a HTTP header. The one you need to include is: Content-Type: application/x-www-form-urlencoded Even if you include other headers, you must include this one exactly as shown.

If you follow these steps, you should be able to avoid the HTTP 500 Internal Error 5003. If you still have trouble, don’t hesitate to ask for help!

FAQs

How Do I Know if the Error is on Sagepay’s End?

Check the Sagepay status page for any reported outages or issues. If other users are experiencing similar problems, it might indicate a problem with Sagepay’s system.

Can Error Code 5999 Occur Because of the Customer’s Bank?

Yes, if a customer’s bank rejects the transaction attempt, Sagepay might present Error Code 5999. Instruct the customer to check with their bank for more details.

Are There Specific Times When Error 5999 is More Likely to Occur?

Error Code 5999 can occur at any time but is more likely during periods of high transaction volume or when Sagepay is conducting system maintenance. Always check the Sagepay status page for potential issues.

Addressing Sagepay Error Code 5999 requires a methodical approach to troubleshoot each potential cause. By following the solutions outlined above, you can identify and rectify the source of the error, restoring smooth payment processing for your transactions.