Protx not redirecting after entering card details

[meatbiscuit]

Hi,

Using V7, I am currently implementing protx into my site. All was going well until the point where I submit the test card details. I get presented with an http 500 error at this url

https://ukvpstest.protx.com/vspgatew.../authorisation

The transaction seems to go through ok as I receive an email and I can see the transaction in the protx admin page.

Protx support are telling me this is a question for Actinic.

[pinbrook]

Have you search the forum using Protx as a search phrase yet?

People have issues with protx all the time so i expect you will find an answer to your dilemma here already

[meatbiscuit]

I've tried searching the forum, that's why I'm posting here as a last ditch effort.
Plenty of info which I have followed, but not relevant to my problem!

It's almost all working except for the redirect from the protx webpage back to my actinic site thats the problem.

[TraceyHand]

just to clarify...are both Actinic AND Protx in test mode? or are you testing Protx in test mode on a live site?

[meatbiscuit]

they are both in test mode.

[meatbiscuit]

I've had a reply from Protx about this issue asking me to replace one url with another so they can find out what's going on.

I have looked through the perl script but cannot find any reference to "vspform-register.vsp"
Does anyone know where I might do this?



>In your website code you specify that your payments will be sent to our >test server and these payments are sent to the following URL:
>https://ukvpstest.protx.com/vspgatew...m-register.vsp
>You need to replace this URL with the showpost one provided below:
>
>https://ukvpstest.protx.com/showpost/showpost.asp
>
>This will mean that all the information you usually post to the test server >appears on our showpost screen and we can see exactly what information >you are posting to us in your crypt string.
>

[Bruce]

Please take this issue up with support as we need to get this properly checked.

Kind regards,

[meatbiscuit]

Just an update...

this seems to be working now - don't know why, Protx must have changed something on their site but they didn't tell me