Hello
I am experiencing a rather strange problem with an eCom solution. Here is some info about the DW our customer is using:
DW
Content version: 18.16.1.13 (Updates.xml)
Assembly versions: Dynamicweb.dll 18.16.3.2
(File version: 18.16.3.2 Dynamicweb, Version=18.9.1.1, Culture=neutral, PublicKeyToken=null)
Dynamicweb.Admin.dll 18.16.3.2
(File version: Dynamicweb.Admin, Version=18.9.1.1, Culture=neutral, PublicKeyToken=null)
Dynamicweb.Controls.dll 18.16.3.2
(File version: Dynamicweb.Controls, Version=18.9.1.1, Culture=neutral, PublicKeyToken=null)
Build date: 12-05-2009 16:09:12
It is an old DW. I know. We have developed a custom gateway provider, to RBS. It is not supported by DW by default.
The problem is like this:
1. a user logs on the webshop
2. the user picks som goods
3. the user is sent to the gateway
4. the user fills the form
5. the user is sent back to the shop where an order is sent to the shop and a confirmation is sent to the user
For the most of the time, the user is sent back to the shop, but instead of a "thanks for your ordre" page, the user is shown a login page. Here the user does not receive a
order confirmation, nor do the shop receive the order, but the order is auth'ed in the RBS system. This has happend for alot of user. Mostly 95%, but the last 5% is sent through.
This url is the one handing over the the user from the shop to the RBS system: https://secure.worldpay.com/sc2/jsp/shopper/SelectPaymentMethod.jsp?OrderKey=DKRCPET%5EORDERs22048&successURL=http%3A%2F%2Froyalcanin.dk%2FDefault.aspx%3FID%3D170%26step=5%26order%3Dcomplete
telling the RBS system, to send the user back to http%3A%2F%2Froyalcanin.dk%2FDefault.aspx%3FID%3D170%26step=5%26order%3Dcomplete on success. I have for 2 days straight tried to regenerate the problem, and it have only succedded me
2 times. But then the returning URL is different: http://royalcanin.dk?ID=170&step=5&order=complete&orderkey=MARSCHOCO^DKRCPET^ORDERs21999&paymentStatus=AUTHORISED&paymentAmount=10500&paymentCurrency=DKK&mac=2707fdab769695276be660c195bcf5c6&jlbz=EZqDpGi0omlr052sPNemm6og0pxPKyg8RQkHsSrg
It has alot of extra parameters. And I am suspecting that this URL is what 95% of the users is getting. It sends the users to a login screen.
My question is therefore: Can the returning url be the sinner?
When I was retuned to the shop with this URL, I did not wait a long time on the RBS side. It took at most 1 minute. This I have replicated on a virtual box, with FF 5 and XP Proffessional.
I do not know what to do know. Hope there is someone out there who can help me.
An upgrade of the DW is not a solution for now. Because the customer has some failing custom modules attached to it that need to be handled first. But they want to use RBS right away.
Developer forum
E-mail notifications
Error when returning from gateway to eCom
Martin Slot
Posted on 02/11/2011 16:10:25
Replies
Merethe Nielsen
Posted on 08/11/2011 09:59:06
Hi
We have had an issue with the cart behind an extranet where orders do not get completed from payment gateway. It was a bug registered in the summer 2010 and fixed in 19.1.2.1 (oct. 2010). Maybe it's this bug that you experience?
It's not possible to upgrade to version 19.1.2.1 and see if this works?
A workaround is to put the cart outside the extranet.
/Merethe
Martin Slot
Posted on 08/11/2011 10:08:02
Thanks for the answer Merethe. I will look into that. I think we are going to put the cart outside if the problem continues, and spend some time on trying to upgrade and see if that corrects the problem. Which gateway provider did you use?
Martin Slot
Posted on 09/11/2011 13:41:05
This post has been marked as an answer
We had several issues with the code. All of which I thought was rooted in that the customer was redirected to the login page on return from the provider. I corrected the finale issue today, that infact was the root of the problem, and it is a rather easy problem to solve, and tell about so here we go.
The customer was allways redirected to the gateway with a static callback URL set to http://myserver.com?order=complete. But almost all customers used an URL on the form of www.myserver.com. So when they were redirected they would get the login screen. I simply changed the the redirect scheme, to dynamic set the callback url. That settled it.
Thanks to you Merethe. If that did not work, by dynamic set the callback, then I would have tried to put the cart outside extranet.
The customer was allways redirected to the gateway with a static callback URL set to http://myserver.com?order=complete. But almost all customers used an URL on the form of www.myserver.com. So when they were redirected they would get the login screen. I simply changed the the redirect scheme, to dynamic set the callback url. That settled it.
Thanks to you Merethe. If that did not work, by dynamic set the callback, then I would have tried to put the cart outside extranet.
Votes for this answer: 0
You must be logged in to post in the forum