Thread: Sagepay Alert to all: They are Changing their API

Sagepay UK (known as ProTx in the cart) have alerted us to an API change.

I'm no ASP techie, so this may be a damn-fool post. Do our devs need to get on this one?? Does this affect ASPDNSF?

See: Sagepay Reporting and Admin API protocol. http://sagepay-email.com/8Z4-7UA9-2HQX8A-3AYUE-1/c.aspx

They write:

=================================

IP Addresses

We will be changing the IP Address of the following domains during this upgrade: live.sagepay.com and test.sagepay.com.

Therefore you may need to make some technical changes if ANY of the following statements are true:

1) You have hardcoded IP addresses within your clients website/shopping cart

2) You have cached DNS entries

3) Your clients have firewall rules in place to only accept access to and from your systems from specific IP addresses

If you answer Yes to any of the above you'll need to download technical details to configure your systems

If you answer NO to all of the above:

You will not need to make any changes and transactions will not be affected by the IP Address switch. The local DNS server will automatically update with the correct IP Address.

Reporting and Admin API

If any of your clients are using Sage Pay's Reporting and Admin API (formerly known as Access), you may need to look over the updated Reporting and Admin API Protocol on their behalf. As part of the upgrade we're significantly improving the API, however this means some functionality from previous protocols will not work.

The three key areas to check are:

* The transaction list details
* The transaction list and batch detail commands
* The 'get transactions summary' format of XML

Please note,the work is being undertaken between 27th-29th of August. Therefore, we strongly advise that you carry out any necessary work over this weekend or soon after.

You may have already received communication regarding this and if so, we apologise. As this is a large and important project, we want to ensure everyone has all the information they need in order to prepare for the changes.

=================================

TTFN

Hi

We've also received notification of these IP address and API changes.

Would be good to get official confirmation from the ASPDNSF support team but I'm pretty sure that the SagePayUK (Protx) gateway is unaffected by this.

AspDotNetStorefront is unaffected with those changes, that's right. There's nothing hard-coded in their APIs also, everything is populated in the appconfig parameters.

Thanks for that Alfred. Saves us some hassle. And any Yanks looking at this - don't worry, its not the US Sagepay. Tis' for Brits only.

BTW: On all things Sagepay related - Becasue credit is due, I keep plugging a function, done for us by for Webopius, see his site. (hello Adam) the lad does a great toy for Sagepay error reporting. It has signifianly reduced our 'failed tranactions' See it running on our site omax org. .

We've changed to the new SagePay URL's today and tested extensively....seems fine...no errors to report.

We're Brits too !

i didn't think there were too amny Brits on this cart...

Now you have me panicing (a little)

All my URLs are still as protx. See the PNG

Alfred says no work to be done, but I take it you've done a Appconfig change. Can i beg a screen grab off you with those changes?? Or is it some cahnging whereever it says protx to sagepay

Pretty please?



Martin

You just need to change the live url to the new sagepay ones. It is very quick and painless. We done it as soon as we had the email telling us (good 4 months ago!) it was all done within 2 minutes of coping and pasting.

I then called sagepay to check it was all good, to which it was, then tested a few transactions. Everything was perfect.

I encourage everyone to update from the protx urls to the sagepay urls (The service is faster as well) as soon as possible!

Martin

Thanks for the mention!

SagePay currently automatically redirects all the old Protx URLs for you.

e.g, type: https://ukvps.protx.com/ into a browser and you'll be taken to SagePay.

As far as I know, these will continue to work after they have changed things at their end. The only time you would need to change anything is if you've ever used a specific SagePay IP address in your config (you haven't).

Adam

Thanks Adam & etradecounter.

I'd'd guesssed protx URLs route to sagepay, but as etradecounter suggests, it has to be better to have it going without a reroute.

Is it jsut an copy & paste job?

Those Appconfigs reading:

"Do not change this unless you know you are clueless.'

Thus:

https://ukvps.protx.com/

becoems:

https://ukvps.sagepay.com/

https://ukvps.sagepay.com/vspgateway/service/abort.vsp
https://ukvps.sagepay.com/vspgateway/service/abort.vsp
https://ukvps.sagepay.com/vspgateway...3dcallback.vsp

etc etc?

Not on the Sagepay site. i had to work quite hard to get this, on hold for half hour, twice. Lumpy PDF but at least we ahve it. Why its not on hte Sagepay site, I can't say!

For the benifit of all.

This will do it via SQL:

Code:

UPDATE [AppConfig]
SET [ConfigValue] = REPLACE([ConfigValue], 'ukvps.protx.com/vspgateway/', 'live.sagepay.com/gateway/')
WHERE [Name] LIKE 'ProtxURL.Live.%'

And this will undo it:

Code:

UPDATE [AppConfig]
SET [ConfigValue] = REPLACE([ConfigValue], 'live.sagepay.com/gateway/', 'ukvps.protx.com/vspgateway/')
WHERE [Name] LIKE 'ProtxURL.Live.%'

It should update only 5 records

You flash git! I'll crib that if its OK with you. Actually i came back here to say to one and all that my first posted list was not complete.

Sagepay have only translated soem of teh URLs you'll see in Appconfig.

Translations missing x 4 are:

https://ukvps.protx.com/vps200/dotransaction.dll
https://ukvpstest.protx.com/VSPSimul...endorReleaseTx
https://ukvpstest.protx.com/VSPSimul...verGateway.asp
https://ukvpstest.protx.com/vps200/dotransaction.dll


Most are test URLs but what is:

https://ukvps.protx.com/vps200/dotransaction.dll

I assume we need it?

As ever you have to work very hard to get info out of Sagepay. so far I've failed. When i get an answer I'll put it up. so far;

i've put it up here as I have it so far;

http://www.omax.org/SagepayProtx%20translationURL.html




.

Worked for us Thanks

UPDATE [AppConfig]
SET [ConfigValue] = REPLACE([ConfigValue], 'ukvps.protx.com/vspgateway/', 'live.sagepay.com/gateway/')
WHERE [Name] LIKE 'ProtxURL.Live.%'

NOTE: Sagepay will actully be ceasing the old ProTx URLs (end Sept 2010) so Sagepay users will ahve to amke this update.