Is any one else having a problem ?
| 9:45 pm on Jun 20, 2001 (gmt 0)|
We use an integrated cart and credit clearance system form Worldpay.
Early in june the introduced some additional security changes and software and since then we have had a regular problem with customers placing duplicate orders.
The report that the server either freezes or gives an error message.
The result is a duplicate order, resulting in refund charges each time
So far Worldpay have just reponded with automated "allocated ticket numbers" to our E-mails, which suggest they may be having a widescale problem.
Any one else having the same problem ?
| 4:36 pm on Apr 23, 2002 (gmt 0)|
Did you ever resolve your problems with WorldPay spiky? They ought to do more than hand out tickets. I had some fun'n'games with them last summer also, for slightly different reasons
| 9:46 pm on Apr 23, 2002 (gmt 0)|
blimey, youve been digging around a bit talltroll!!
i dont remember having any similar problems like that. what was your problem talltroll?
| 8:39 am on Apr 24, 2002 (gmt 0)|
One of the e-comm packages I work with has an option to use WorldPay in conjunction with the cart. You need to have a separate WP agreement, but once they send you the account details, you enter that into the e-comm package, and it wouldn't validate a txn until it got the authorisation code back.
Then WP changed the formatting of the data packets they sent and recieved, without telling anyone, and that of course broke every e-comm site we had that was using WP. Fortunately, that wasn't too many, and it got fixed in a hurry, but still...
From the timing of spikys post, it seems he got stung by more or less the same thing, the timing seems to fit. I seem to recall that they also changed the structure of their customer accounts at the same time.
Again, fortunately for us, WP headquarters is just down the road from the company I was working for at the time, and one of our directors was friendly with WP, so we got sorted out in a hurry. Not everyone was so lucky it seems
| 10:00 am on Apr 24, 2002 (gmt 0)|
hmmm... i'd guess it could have been one of those changes they needed to make ASAP and didn't have time to tell everyone in advance - there are too many configurations to check and test all of them prior to an urgent change. at least you got it fixed fairly quickly.