When using ePay you may experience errors such as: 'Unable to connect to Bacs', 'error 500', or other issues that relate to communicating with the Bacs servers. This is particularly applicable if you have recently made any changes to your firewall or proxy server. All communications are handled from the ePay server, not from the client machine. To make sure the ePay server can communicate with Bacs please follow the instructions below:
We recommend that this is done by somebody in your IT department who has full access to the server and is familiar with your IT infrastructure.
- Log into your ePay server as the service user account. For information on finding which account this is, please see article: How can I find the account being used to run the ePay service (ePay service user account)?
- If you are unsure which machine is running the ePay server software, please see article: How can I locate my ePay server?
- Once you are logged into the server as the service user account open Internet Explorer and make sure you can browse the internet. If you are unable to access the internet you will need to correct this issue before proceeding.
- If you can browse the internet please go to: https://paymentservices.bacs.co.uk. If his page loads successfully your server can communicate with Bacs. If you do receive any errors, please speak to your infrastructure team to investigate these issues further.
- If all the above have been checked, restart the ePay service on the server via windows services.
'Start' > 'Run' or Search > 'Services.msc'.
If all the above are correct but you are still having issues sending your submission, please make contact with Bottomline support on 01189 258 250 option 2 or email firstname.lastname@example.org.