WorldPay Business Gateway not returning

-- HikaShop version -- : 2.6.3
-- Joomla version -- : 3.4.8

I have read everything I can on this subject but I can find no solution.

I have got the correct callback in the WorldPay admin setting and this all matching, orders are successfully being completed in the test environment, however I cannot despite trying , get the browser to return to the store upon completion of the Worldpay transaction. It just sits there on the 'Thank you for your simulated payment' page of WorldPay.

Can anyone suggest where I might be going wrong please :0(

I have payment response enabled and URL set to <WPDISPLAY ITEM=MC_callback>

I have tried it with and without shopper response, but all just stops at the same point whether successful or failed.

Please don't direct me to the Documentation here or on Brainforge, neither helped.

Hi,

Can you provide a screenshot of the settings of your payment method so that we can check the settings ?

Thanks Nicolas, I attach the screenshot and also the array...

Thanks for your help.

Hello,

Thanks for your return and informations, but can you please add a screenshot of your WorldPay plugin backend configuration, like this for example :



Please note, that here the screenshot is uncomplete, the most important part for help you is the specific configuration part.

Awaiting news from you.

Regards.

Hi Philip,

Thanks for looking at this, I attach the spec screenshot.

Hello,

I noticed something strange in your Specific Configuration, you haven't the Return url input option.
Have you really updated your HikaShop version AND plugins ?

Awaiting news from you.

Regards.

Hi Philip,

Plugin was latest, I have upgraded Hikashop, from 2.6.1 to 2.6.3

Attached new screenshot.

I await your instruction, many thanks

Hello,

I just noticed something right now, see by yourself :




For me you have to change this Url to switch to production phase and I hope that will leads your process to reach the thank you page.
Because for me, it look like a sandbox url, but I can't be sure of it.
Replace it by the Production phase Url that Worldpay give you (we don't have this elements on our side).

And define, the return url for where you want redirect your customer.

Awaiting news from you.

Regards.

Hi Phillipe,

Sorry for the delay in responding, we have been having mega-problems getting worldpay to communicate.

The site is now switched live and validated.

We have put through a live transaction, we have received notification of transaction completion to Hikashop Orders Section.

However, we are still stuck on this final page and no callback to the site. Could you help any further please?

Hello,

Did you try to fill this input in your backend plugin configuration ?



For successful return use this kind of code : YOURWEBSITE/index.php?option=com_hikashop&ctrl=checkout&task=after_end
And for cancel url : YOURWEBSITE/index.php?option=com_hikashop&ctrl=order&task=cancel_order

Hope this will help you !

Regards.

Hello,
I have exactly the same issue. Does the return url only work when using the production mode of WorldPay and not Test Mode?

This is what I have on my config and plugin screesn

Please help!

Lee

Hello,

Unfortunately I can be sure of it, but yes maybe return Urls set here (see screenshot on below) may be only use for production phase ?...



For this precise point, maybe you can have more details from Worldpay support ?

Awaiting news from you.

Regards

Phillip,
I have now had help from Worldpay and the redirect is now running correctly and directing back to my site. However the url I am using results in an error page:

www.MYDOMAIN.COM/index.php?option=com_hi...ckout&task=after_end

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

Is this the correct return URL? do i need to configure something within HikaSHop?

Hello,

Strange, your Url is correct and must work... Can you make a screenshot of the screen after redirection ?
Do you have an error message ? Other possible way to find issue roots, do you have some override view on your after_end view ?



Do you have this little trash icon ?

Awaiting news from you.

Regards

Philippe,
I do not have a custom after_end setup, this is the error message I get attached.

Lee

Hello,

Here, you are in Chrome, Right ?
Can you try to test with other navigators, see if that work ?
Other thing you can try, is to rename your htacess.txt for something like htacess1.txt, and make another test.

This different tests may allow us to know the root issue.

Regards

Philip,
I have tried in numerous browser with SEO turned off. There are no custom templates being used and I'm still getting the same error message no matter which browser.

is there any configuration I need to check?

Lee

This is the code in my after_end file:

Hello,
And do you rename the htaccess file ? This test is important to understand the issue.
Awaiting news from you.

Regards

Philip,
That iss weird! I had SEO URL's turned off in the backend but still had a .htaccess file on my root. When I renamed the file it then processed correctly. What is the issue with the htaccess file? As I will need it to activate the SEO URL's once the site is live.

I have attached the htaccess file.

Lee

Hi,

This means that the issue is linked to the SEF system.
One thing to try:
just before going back to your website, open your browser's inspector and go in the tab network. Activate it if it's not already done and configure it to "preserve log" or something like that (the name will vary based on your browser). That way, you'll see the requests to the thank you page and the several redirects that are done on it. Looking at the requests and responses there should provide information as to why this happens. For example, it could be that the URL is redirected to the https version of the website, which itself redirects to the same URL in the http version, etc. which would indicate a problem with the setup of the SSL redirection ( which is usually done in the htacess file, but that's not the case on your website).