Announcement

Collapse
No announcement yet.

SagePay: Error initialising payment service. Please try another payment method

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SagePay: Error initialising payment service. Please try another payment method

    When bouncing to Sage Pay, you may see this error:

    Error initialising payment service. Please try another payment method.

    There are two things which can cause this error:

    1) This can mean that the IP address of the server sending the request is not known to Sage Pay.

    Before using the new Sage Pay integration, you need to register your server IP address or addresses with Sage Pay via 'MySagePay' and selecting 'Settings | Valid IPs’.

    Detailed instructions can be found here:

    http://www.sagepay.co.uk/support/16/...o-your-account

    You will be able to find out what your servers IP address is either from your hosting company, or using tools such as:

    http://www.who.is/dns/

    2) Crypt::SSLeay needs to be installed on your web server in order for the new integration to work, it is not included with Perl 5.8 and below. Crypt::SSLeay is installed as standard with later versions of Perl.

    To check what Perl modules you have installed on your server, please see this knowledge base article:

    http://community.sellerdeck.com/showthread.php?t=49361

    If you find Crypt::SSLeay is not installed, please contact your hosting company and advise that Crypt::SSLeay must be installed in order for Sage Pay to work on your website.

    If your web server has Crypt::SSLeay installed and the Sage Pay integration does not work, it is likely your hosting company is using a very old version of Crypt::SSLeay. SellerDeck would recommend installing at least Crypt::SSLeay 0.57 or above.

    PLEASE NOTE: We have become aware that version 0.64 of Crypt::SSLeay will not work with the Sage Pay integration, so if your hosting company are currently running this will need to be upgraded.
Working...
X