I'm currently trying to integrate Worldpay as our payment method. All provider settings have been set and it seems to be working fine. I can work through every step followed by a redirect to the succes page which is the cart confirmation step as set in the 'succesURL' option.
However, orders are NOT being added on completion and I'm having trouble figuring out why. They simply won't show up under Orders.
Try check the DB and the umbracoLog table and see if any errors regarding worldpay is present. It could indicate what might be wrong when it tries to finalize the order.
I checked the table and no error messages are added during the order process.
I'm running the WorldPay checkout in Test Mode, could that be the reason? Also, after finishing the payment and the redirect I get a (test) confirmation email from WorldPay, but not from the TeaCommerce solution.
World pay sends a confirmation email - this is not the Tea Commerce order confirmation. I think you can turn off the World pay email when switching to production. The Tea Commerce order confirmation email is only send when the order is finalized. So it makes sense no email is send as you say the order isnt finalized.
Don't know why no now error is in the umbracoLog. Do you get redirected correctly?
Have just noticed the same thing happening on our sites.
It works fine on our test environment. But on the live site the orders never get finalized. I've gone through all the settings with a fine toothed comb and it all looks correct. Once you've completed the payment, worldpay redirects you to the correct page. Confirms the order was a success, but in the tea commerce back end the worldpay orders aren't there. Only once I search for orders in the "inital" state can I see them.
In a macro on the confirmation page which worldpay redirects to I have the following razor script which would redirect if the order hadn't been finalized, but it doesn't.
if (!TeaCommerce.Razor.TeaCommerce.HasFinalizedOrder())
So how come it's not being processed properly? The teacommerce confirmation emails don't get sent either. No errors appear in any of the logs. We have two other payment methods (account and no value payments) which all work fine. Just the world pay stuff.
The reason why your redirect is executed is that the HasFinalizedOrder doesnt rely on the callback from the payment gateway as this can have a delay. But when you are redirected from the payment gateway to your shop again - Tea Commerce moved the order from currentOrder to finalizedOrder - BUT it doesnt mean that it is truely finalized. We can only finalized with 100% trust, when the payment gateway makes a callback. So the thing that isnt executed is the callback url - which is why the order isnt marked as finalized and and the email isnt send.
Are there nothing in your umbracoLog? Does the world pay provider make a http call to the callback url?
Your comments pointed me in the right direction. I checked on worldpay and the "Payment response enabled" option was not checked (it was for our test environment.) This is probably the cause of the problem.
Worldpay paid orders not being added
Hi there,
I'm currently trying to integrate Worldpay as our payment method. All provider settings have been set and it seems to be working fine. I can work through every step followed by a redirect to the succes page which is the cart confirmation step as set in the 'succesURL' option.
However, orders are NOT being added on completion and I'm having trouble figuring out why. They simply won't show up under Orders.
Am I missing something?
Any help would be appreciated!
Thanks
Hi d-Tail
Try check the DB and the umbracoLog table and see if any errors regarding worldpay is present. It could indicate what might be wrong when it tries to finalize the order.
Kind regards
Anders
I checked the table and no error messages are added during the order process.
I'm running the WorldPay checkout in Test Mode, could that be the reason? Also, after finishing the payment and the redirect I get a (test) confirmation email from WorldPay, but not from the TeaCommerce solution.
Any other ideas?
Thanks!
World pay sends a confirmation email - this is not the Tea Commerce order confirmation. I think you can turn off the World pay email when switching to production. The Tea Commerce order confirmation email is only send when the order is finalized. So it makes sense no email is send as you say the order isnt finalized.
Don't know why no now error is in the umbracoLog. Do you get redirected correctly?
I'm going to bump this.
Have just noticed the same thing happening on our sites.
It works fine on our test environment. But on the live site the orders never get finalized. I've gone through all the settings with a fine toothed comb and it all looks correct. Once you've completed the payment, worldpay redirects you to the correct page. Confirms the order was a success, but in the tea commerce back end the worldpay orders aren't there. Only once I search for orders in the "inital" state can I see them.
In a macro on the confirmation page which worldpay redirects to I have the following razor script which would redirect if the order hadn't been finalized, but it doesn't.
So how come it's not being processed properly? The teacommerce confirmation emails don't get sent either. No errors appear in any of the logs. We have two other payment methods (account and no value payments) which all work fine. Just the world pay stuff.
Thanks, Ian
Hi Ian
The reason why your redirect is executed is that the HasFinalizedOrder doesnt rely on the callback from the payment gateway as this can have a delay. But when you are redirected from the payment gateway to your shop again - Tea Commerce moved the order from currentOrder to finalizedOrder - BUT it doesnt mean that it is truely finalized. We can only finalized with 100% trust, when the payment gateway makes a callback. So the thing that isnt executed is the callback url - which is why the order isnt marked as finalized and and the email isnt send.
Are there nothing in your umbracoLog? Does the world pay provider make a http call to the callback url?
Hi Anders.
Your comments pointed me in the right direction. I checked on worldpay and the "Payment response enabled" option was not checked (it was for our test environment.) This is probably the cause of the problem.
Thanks for your help, Ian
Great you got it solved :)
is working on a reply...