Just weeks after rolling out our new website, we’ve just completed a huge server infrastructure upgrade (with zero downtime- woop!).

Customers rarely comment when the software is blisteringly fast, so we’ll instead be looking out for the lack of comments about things being a little slow at peak times.

If you don’t use SagePay, code against our API or use SPF records then you don’t need to do a thing.

However, if you do then read on…

SagePay

If you use SagePay as your integrated credit card processor then you’ll need to add our new server IP addresses to your SagePay settings:

Login to your SagePay account.

From the ‘Administration’ menu, choose ‘Account Parameters

Scroll down to the section labeled ‘Valid IP Addresses for this Account’

Add a new entry with the following details:

IP Address: 31.222.144.2
Subnet Mask: 255.255.255.000
Comment: KashFlow

and then another as

IP Address: 31.222.144.0
Subnet Mask: 255.255.255.000
Comment: KashFlow

SPF Records

If you’ve created SPF records to help ensure delivery of emails we send on your behalf then you may need to update them.

All mail sent by our system will now be delivered from kyle.kashflow.com  (31.222.144.1)

If you don’t know what to do with this information then talk to whoever manages your Email or set up the SPF records for you in the firs place

API

If you’re programming against our API and you’ve been with us a few years, there’s a small possibility you’re still using the old ancient endpoint of https://secure.KashFlow.co.uk/api/service.asmx.
This is finally being switched off in a week or so. You should upgrade your code to instead use the URL https://securedwebapp.com/api/service.asmx

Nothing else has changed, just the URL

Share this article

See how KashFlow works with your business and your books