Blackbaud Payment Service™, Blackbaud Merchant Services™, and Blackbaud Checkout (formerly Blackbaud Secure Payments™) moved to Blackbaud SKY™, our modern, integrated, and open cloud on February 11th, 2018. If your organization’s applications are not hosted by Blackbaud, please confirm access to the below hostnames. If your applications are hosted by Blackbaud, no action is needed.

In order to access the Blackbaud Payment Service, Blackbaud Merchant Services Portal, and Blackbaud Checkout, please allow all inbound and outbound traffic to the following hostnames:

We recommend using hostname based firewall rules. If you are unable to use the hostnames above, you must allow all traffic from the IP addresses utilized by Incapsula. Incapsula is a third party service utilized by Blackbaud for networking purposes, and all Incapsula IP addresses documented here must be allowed. If you use the host names above rather than IPs, no additional action is needed. The Incapsula IPs are automatically included in the hostnames above. 

If you encounter issues accessing the BBMS web portal or while using functionality within the portal, you may need to allow the IPs for Blackbaud SKY in Amazon Web Services (AWS). For Blackbaud SKY in AWS information, please refer to the documentation here
Note: Throughout this article, we have provided links to third-party websites. We provide links to third-party websites in an effort to help you resolve your issue. We are not responsible for the information on third-party websites, and we cannot assist in implementing the solutions on these websites.
If you are unable to connect to BBPS after updating the firewall, please follow these steps:
  1. Ping BBPS ( from the machine encountering the issue. You should receive the Incapsula IP address. If you receive the old IP address, proceed to Step 2.
  2. Flush the DNS
  3. Check the hosts file.  It’s possible the machine has been hardcoded to connect to BBPS on the old IP.  

You may receive the following error if these IPs aren't configured properly:
Error: The request failed with HTTP status 503: Service Unavailable. - when viewing testconfig/configinfo, submitting payment or attempting to access Secure Payment Page