Sage Pay Error

[Krithika]

I have passed this on to the development team to check with Sage Pay directly. Will post here once I have an update.

[benh777]

Fingers crossed, I think I've fixed it now, I deleted all the other forms of payment in the Actinic business settings menu. Before I didn't think this would affect it as the Website and Desktop check boxes weren't ticked for the other options.

I think that's what fixed it anyway!

Thanks for the help.

Ben

[janimal]

I have passed this on to the development team to check with Sage Pay directly. Will post here once I have an update.

Thanks.

I think my client has also now spoken with support too.

Hopefully we'll get to the bottom of it.

[auztin100]

I'm having similar problems, has anyone got a solutions as yet ? I'm not getting the psp bounce to Protx, and the next button gets errors on sage pay ...

Upgrade from v7 - v9 ...

[TraceyHand]

I'm having similar problems, has anyone got a solutions as yet ? I'm not getting the psp bounce to Protx, and the next button gets errors on sage pay ...

Upgrade from v7 - v9 ...

You need to be more specific. Saying th problem
is similar means it's differernt but you haven't told us how!
What is the sagepay error you're getting with the next
button?

[janimal]

Mysteriously fixed

We suspended the catalog and then uploaded the site in test mode (with payment set to test mode too) and had the same error with sagepay (5050 invalid characters in address)

By this time Sage Pay had told us we had to upgrade actinic and Actinic support had said they would look into our issue.

The following day I mentioned the nightmare we were having to a friend. Who being that kind of person, went to the test site and attempted a purchase. He did not get the 5050 error.

So I tried it, no error. I tried the version I had uploaded previously to my own test server (which had also been getting the same error) it worked.

So put the site back in production mode, put the payment configuration into production mode and tried a purchase and it worked.

So now we are taking orders again without having changed any of our actinic code or setup. This suggests to me it was a Sage Pay problem, perhaps a setting on our account? Since they are the only ones who could have made a change which fixed it across our live server and test server installations.

However if my friend hadn't tried the site again, we would still be in suspended mode, waiting for Atinic or Protx support to get back to us.

I am glad the site is working, but disappointed we have had no feedback or explanation from SagePay or Actinic support.

[auztin100]

I have the site working now.

The only problem I have left is the PSP bounce page does not auto jump to Protx (or PayPal) ?

[Duncan Rounding]

Probably the onloadscript is missing from the body tag or the script is missing from the head. This has been reported quite a few times following an upgrade. Search for PSP Bounce in the Google search box above and you should find information which may help.