We were doing some testing today and noticed we cannot void a tranaction. Selecting void sends an abort condition. Voiding gives a Sagepay '4006' error. We must refund instead.
Whats happening?
Is it related to the rebrand URL issue?
If not I'm asking two questions...
We did the Sagepay rebrand of URLs way back. Works fine in all other respects.
I see:
https://ukvpstest.protx.com/vspgatew...vice/abort.vsp
(now updated to)
https://live.sagepay.com/gateway/service/abort.vsp
Should there be a:
https://live.sagepay.com/gateway/service/void.vsp
as per Sagepays rebrand spec.
Whats actually happening?
Note: Even after the rebrand and URL cahnges,4 x URLs
https://ukvps.protx.com/vps200/dotransaction.dll
https://ukvpstest.protx.com/vps200/dotransaction.dll
https://ukvpstest.protx.com/VSPSimul...verGateway.asp
https://ukvpstest.protx.com/VSPSimul...endorReleaseTx
Got left in the cold. There are no listed Sagepay rebarnd equivelant and asking Sagepay, they say thse never did exist.Which is odd. Is this the probelm?
What did or do the dotransaction.dll etc URLs do? Seems to cope with them not changed. So waht are they for?
Thanks Martin
AspDotNetStorefront ML 8.0.1.2/8.0.1.2