In this article, Sage users learn how to fix SagePay error 4020 (while activating Sage Pay On Sage 200) information received from an invalid IP address. If SagePay is integrated with your website with the help of Direct Method or the Server, you must valid IP Address for your web hosting company or your platform to start accepting the transaction through SagePay.
Types of SagePay Integration – My SagePay
- Shopper checkout
- Payment information
- Submit a payment
What is SagePay Error 4020
Sage Pay offers many advantages like Online payment, Phone payment, Face to Face payment, and Invoice payment with complete security to make your payment safe and secure. It still faces some issues due to various technical reasons. It is better if these issues are handled by technical experts only.
- The SagePay Error 4020 simply states that the transaction post which you are getting from the hosting company or website is not made through the valid IP Address that you enter in your Sage Pay Account.
- All transactions that are posted from your website/server MUST be sent via one of the IP addresses that you have provided to Sage Pay. If your IP address is not entered within.
- If a dynamic IP Range is used to make the transaction in MySagePay, it is for sure that the error will occur with your software.
Causes and Reason SagePay Information Received 4020
- No Access to SagePay: This error users face while registering their IP addresses. So users no any task performed till the time when users pick up with the valid IP address.
- System Crashing: System crashing is another way to impact the performance of the SagePay.
Related Issue– SAGEPAY Error 5080
Here is the Solution Procedure that will help you Fix Information Received SagePay Error 4020 in Sage 200
It is very easy to fix the SagePay Error Code 4020. At first, you have to stop the error from occurring again and the information will automatically not be posted through SagePay.
The second thing that you need to do is locate the IP Address. For that, follow the steps we are mentioning below:
Way I: System Restore
- First, Start your system >> login as an administrator
- Then Go to Start menu >> select all programs >> System Tools >> System Restore
- Next, select “Restore my system to an earlier time” >> select next
- Sure, Choose the latest system repair point >> then select the restore point list >> click to Next
- Open a confirmation window >> click next
- Last, the Restoration part is completed >> restart the system
Way II: Add Correct IP Address from SagePay Account Control Panel
- First, Click on the Start Menu >> then type CMD Command
- Next, DOS Window will load up >> type the Ping followed by URL that can take you to your own website
- Here you will get the IP Address of the website from where the transaction is processed using SagePay
- Now, you will get the IP Address, and enter the IP Address into your Admin Account of MySagePay.
Way III: Use Sage Pay Simulator to Process the Transaction
- Now, retrieve the IP Address using which the transaction had been processed earlier.
Way IV: Contact your Server Administrator
- If you have your own internal server, the information must be there on your server. Get the IP Address from the server.
Way V: If your Website is with some other Hosting Company
- If it is hosted by any third party, you can get the IP Address from them.
We are a team of professional technical experts who can handle the issues SagePay Error 4020 and other Sage exchange errors very promptly and provide all necessary solution measures effectively and efficiently. To get in touch with our Sage technical support service team, call us on our toll-free number +1800-986-6931.
We are also available through the live chat which is available on our website in the down-right corner. Send us a mail on our Email ID and our team will get back to you to provide you with the necessary solution to bring your “SagePay Error 4020” to functioning once again.
Other SagePay Error Codes with Error Messages or Reasons
Error codes | response | messages or reasons |
400 | Bad Request | The server did not understand the syntax of the request |
401 | Un-authorized | The user authentication is a must for the request |
402 | Request Failed | The request you have done is not successful. That means it is rejected or declined |
422 | Unprocessable Entity | The request was well-formed but contains invalid values or missing properties. |
500 | Server Error | An unexpected thing is done by the server so the request is not being processed |
502 | Bad Gateway | There is an invalid response received by the server from another server when you send the request |
503 | SERVICE UNAVAILABLE | The server is overloaded or down that is why the request is not completed |
1009 | 422 | It has invalid values |
1011 | 422 | Merchant session key or card identifier invalid |
1012 | 404 | Transaction not found |
1013 | 403 | Transaction type not supported |
1015 | 422 | The request entity was empty |
1017 | 403 | Operation not allowed for this transaction |
1018 | 403 | This refund amount will exceed the amount of the original transaction |
2002 | NOTAUTHED | The authorization session is timed out |
3033 | MALFORMED | In this, a Related Security Key is required |
4020 | Invalid IP Address | |
4046 | REJECTED | 3D-Authentication required. Cannot authorize this card |
4047 | INVALID | The account of the vendor is not there or closed |
5003 | ERROR | There is an Internal server error in your account |
5004 | INVALID | There is an invalid state of the transaction |
5025 | NOT AUTHED | You have exceeded the number of attempts limit in the authorization |
5029 | The user 3D authentication is failed according to the vendor’s rules | |
5080 | Form Transaction Registration Failed | |
9998 | 408 | Request timeout |
9999 | 500 | An internal error occurred at Sage Pay |
11003 | The transaction timed out | |
11007 | The transaction was declined by the bank |
End