An automatic redirect from page 3 to 4 can be done easily using a meta-redirect in the HMTL you serve on page 3.

Daniel

I completely agree that WorldPay’s customer service is, at best, one eyed on this issue, and given the demand you’d think they’d take a more holistic approach to this issue. Almost certainly to be their loss in the long term.

I have already looked into using Ravi’s approach with the client and once we’ve got the client’s WorldPay account details will look to implement this. We’re even hoping to incorporate it into an auto-redirect back to the client’s site (ie from Page 3-Page 4) to get around the extra click. If I can personally understand how we do this with the coding, which isn’t guaranteed, I’ll pass the comment onto Ravi’s blog.

Thanks again,

Matt

Our solution currently works in boh the live and the test environments, as long as you disable the ‘whitelisting’ option. This is still possible, because WorldPay keeps on postponing the final changes, and I guess we won’t see them in place any time soon (but who knows?).

However, once WorldPay finalizes the changes, whitelisting will be enforced, and the solution in the main article won’t work. This is because WorldPay will strip out (‘whitelist’) not only javascript, but also the iframe on the payment notification page. Therefore, the tracking code inside the iframe will not be executed.

Unfortunately, I feel WorldPay is not very customer friendly with respect to this issue. When I called last time, I’ve quite abruptly been told Google Analyitcs is a 3rd party tool and WorldPay is not responsible that their service works with 3rd party tools. Sure, right. But GA is the de-facto standard for web analyses, and WorldPay just one of many payment “service” providers. I told them in that case, I cannot really recommend WorldPay to clients and partners anymore.

In any way, you can always use Ravi’s solution (see above), at the expense of an additional click for the customer.

Anybody else tried calling WorldPay on that issue?

Best,
Daniel

I’m quite the novice with WorldPay and cross domain tracking but am working on a client and this appears to potentially solve our problem. Any news on how this has been affected by World Pay’s whitelisting? From what I understand from the comments I can’t be totally sure if your suggestion would work if implemented so would be good to get an idea of current/future situations with this.

Thank you,
Matt

I read through your article. Good idea. The drawback of your solution is that you require the user to click one more time, hence adding an extra burden (when in fact, he has paid already). Anyway, I assume everybody will click and the tracking will work, as they want to ‘complete the order’ after paying.

Thanks for letting us know.
Daniel

Great post ! I had looked up this one when I tried doing this.We at Tatvic just finished one implementation of Ecommerce tracking for Google Analytics if Worldpay is a payment Gateway. Have a look at it . It will be great to hear your feedback !

Cheers,
Ravi

[code]
tag name="iframe" action="remove"
tag name="frameset" action="remove"
tag name="frame" action="remove"
[/code]

It works in my (clients) live env too, unfortunately not in the Test env. After a bit of digging this is down to the whitelist of allowed HTML tags that they are implementing on the live env on 23rd September (well so they say). This is active on the test env by default. But you can login to the payment gateway and turn this off in the installation setup untick the ‘Enable whitelisting?’ checkbox and it will work once more on the test env. Unfortunately they will be implementing this on the live env on the 23rd September, but will allow developers to disable it until the 14th October when it will be enforced on all env’s. Another sad face!

See http://www.rbsworldpay.com/support/bg/index.php?page=news&sub=xss&c=UK#pptech for the full detail. They are using AntiSamy Project allowed attribute list as the whitelist which if you download and look through it has the following directive;
[code]

[/code]

Evidentailly it is this that is the scurge of worldpay marketeers the world over! Thinking of putting in a support request to worldpay to highlight this as an issue. Although dont like my chances of getting this omitted!

Thanks for your comment. The described method currently DOES work in the live environment. We also encountered some strange behavior in the test environment today (it was working a few days ago), and we are investigating this. Unfortunately, I noticed that WorldPay tends to announce changes, then postpones them, and then appears to implement them step-by-step at ‘random’, unannounced intervals, with very vague descriptions. We will investigate it further and report on updates. Would be nice if you could keep us updated as well.

Anybody from WorldPay reading this?

Cheers,
Daniel – http://www.GuideGecko.com