Hello Forum,
Instead of asking questions I'm actually posting something for info today !
since updating to Sagepay v3, and Sellerdeck 2014 we have had some issues in some clients not managing the jump to Sagepay.
We now know that if a client puts in Bill or Gates as opposed to Bill Gates or adds in extra characters to the postcode, Sagepay will throw up a message when saving the order which is unhelpful and leaves the client no where. We have changes this message in actininextras.js and it now means something to the client. i.e your 1st name / surname / postcode is incorrect.
That was the easy bit.....
But on Sagepay back office, I'm not sure if its widely known but you can see in "INVALID TRANSACTIONS" the failed orders that don't even make it to PSP pending.
Then you can contact them if they fail to get to orders......
Just thought i's contribute - hope it helps.....
Instead of asking questions I'm actually posting something for info today !
since updating to Sagepay v3, and Sellerdeck 2014 we have had some issues in some clients not managing the jump to Sagepay.
We now know that if a client puts in Bill or Gates as opposed to Bill Gates or adds in extra characters to the postcode, Sagepay will throw up a message when saving the order which is unhelpful and leaves the client no where. We have changes this message in actininextras.js and it now means something to the client. i.e your 1st name / surname / postcode is incorrect.
That was the easy bit.....
But on Sagepay back office, I'm not sure if its widely known but you can see in "INVALID TRANSACTIONS" the failed orders that don't even make it to PSP pending.
Then you can contact them if they fail to get to orders......
Just thought i's contribute - hope it helps.....