Just had a response from Worldpay:
As mentioned, I had to raise this with our next level support team to investigate and we noticed that it seems you’re currently submitting 2 IP values in the ‘shopperIP’ field.
This is causing a conflict and unreadable request which responds back with an EXT_62 message.
For one of your transactions, this is listed as:
‘shopperIP=*.***.**.**, 127.0.0.1’
It appears you’re sending localhost on all of your transactions which we don’t permit. Looking into this, it seems that one reason this happens is if the shopper is hiding behind a proxy.
This issue has been raised with with products team, but we don’t currently have an ETA on resolving this.
For the time being however, you will need to have a catch that restricts or specifies the shopperID attribute.
Should I be of any further help or assistance, in this matter or any other, please do not hesitate to get in touch.
Regards,
Michael Barford
Gateway Technical Support Consultant
—————-
Any thoughts on how I can resolve this issue?
Ben