You need to upload the resultC.html and resultY.html files to the Worldpay system
They are included in the plugin but might need tweaking
Also, be careful because worldpay will only redirect if the filenames are exactly correct and is also case sensitive!
…Spence
Read the documentation and do exact as explained there.
Thread Starter
evbob
(@evbob)
Thank you both, yes not sure how I missed it as it was in the documentation; the redirect is now working correctly Thanks! However I now get an email from WorldPay saying “callback error”, see below:
Our systems have detected that your callback has failed.
This callback failure means we were unable to pass information to your server about the following transaction:
Transaction ID: 3056423935
Cart ID: 467
Installation ID: 1099854
Error reported: Callback to http://artisansurveyors.co.uk/wc-api/MDS_Worldpay_Gateway/: NOT OK, recevied HTTP status: 404
Server Reference: ukdc1-pz-cen07:callbackFailureEmail-3724:MerchReq-557-18
Also, if you usually return a response page for us to display to the Shopper within the time allowed (1 minute), this will not have been displayed.
WorldPay will have displayed to the Shopper the response page file (resultY.html or resultC.html) held for your installation on the WorldPay server. This will be your own custom version, if you have supplied one, or, if not, the WorldPay default version.
We hope this information will be of assistance. Please refer to the WorldPay Knowledgebase – http://www.worldpay.com/support – or contact your local Technical Support team if you want help or advice about using the callback facility or about this particular callback failure.
Any ideas on this? Thanks again.
Your website needs to be live, meaning your url must be available to everybody so Worldpay can send the response back to the website. If you are on localhost or use any kind of under construction plugin that limits website access you will get that error.
Thread Starter
evbob
(@evbob)
ok, yes thanks for that. That is what I thought as I was developing on an internal dev box, however the problem seemed to continue after the website had been made live. I will continue to monitor this. By the way, thanks for a great plug in.
