While I sympathise with Vasco's plight it's a bit unfair to rule someone out due to their need to accept payments through a third party. And let's not forget there are many people out there happy to rip of genuine retailers too. To me there is a vital question of a need to trust on both sides of the fence - which parties such as banks and a bit of lateral thinking from ISPs could help effect but won't.

PS if Anonymous Coward Directs Comments does that make him AC/DC? We should be told!

Your comments re worldpay are way wide of the mark.

You could have contacted worldpay for a refund and your bank should have also taken more action. The line they span you only really applies to people like paypal who operate in the manner you mention.

My company use worldpay and once or twice a year we get subject to charebacks - only once in 5 years has this been valid - it was a fraudulent transaction - in all other cases the customer simply didn't recognise the transaction.

All you had to do was write to the credit card company asking them to do a charge back and providing copies of the correspondence between you and the company concerned. I've done this myself when I had a problem with a supplier in the USA and the money reappeared within days.

If a charge back is done on Worldpay the retailer gets charged £25, plus the original transaction fees so it is in the retailers interest to refund before the transaction is disputed.

We use worldpay because we don't want to be responsible for the security of your credit cards details. We are quite happy to leave that in the hands of a well recognised quality payment gateway used by 10s of thousands of companies would wide to securely process your card transaction.

Much better to use a site driven by a well known payment company who can therefore verify the company you are buying from actually exists rather than sending your credit card details to some random web site designed to rip you off with no way of tracking them down.

If you buy as you suggest from sites what manage the process themselves then you risk your card details being stored insecurely or transmitted insecurely, take for instance a recent occaision where I booked a hotel online. My full card details were email to me and the hotel in the booking confirmation. The site in question thought this was entirely acceptable even though it stated it used the latest security encryption and was totally secure.

As for stock levels, many, I'd guess most online stores have no true picture of stock levels, so the stock levels are updated as and when the trader does it and between then and them processing the orders it is easy for them to sell out. Clearly this trader was a bit suss as they did not offer a refund as they should and did not provide the refund quickly when asked. Your bad experience was down to a bad trader.

If you are buying from a company you do not know and want some idea whether they are genuine, pick up the phone and ring them. If they don't have a phone number don't touch them. Often the number advertised on fraudulent web sites doesn't exist or belongs to someone else. Check 192.com or companies house for the company concerned and check they exist and are at the address shown.

Can't reproduce your 403 error with Google using search term Evans.

Even so it is purely a search engine, you then clicked thru to a website, when that happens google are not in control and nor would you want them to be.

The 403 error is thrown by the website you have clicked thru to, its either faulty, has ceased to exist or the web server is badly configured.

Clearly you have no concept of how the internet works or what a 403 error is. Perhaps you should learn a little more and then you would understand what you are seeing on your screen and know what to do when it happens.

In this case click back (to google) and follow a different link.

Google will eventually drop the broken web site from its listings, but since there are billions of web sites it will take a little time for google to do this.

Worldpay also allow for cards to be billed once items are shipped rather than at the point of order, as a supplier you can just validate the card and then continue the transaction when you are ready to ship.

The site you used just decided to bill up front. Unfortunately many sites don't make it clear when payment is taken. I suggest you look for it in the future. The cheapest site isn't always the best.

One of my friends has just enabled taking payment on shipment as he was getting so many fraudulent transactions (within days of setting up) that he now carries out his own checks before processing any orders in addition to the ones the payment handler makes.

Our own business generally sees about 1 in 5 transactions coming up as a warning, this is generally down to the card holder putting in a wrong billing address, or the card company not supporting all the checks that are possible. We have only had one actual fraudulent payment in 5 years - we quickly put a number of measures in place after the first one to help prevent any more and to stop people using our site to validate whether stolen cards are still working.

"Look for a padlock symbol in the bottom right of the browser window and for the website address to begin with 'https://'"

No! Look for where your browser (which may not be Internet Explorer) normally puts the padlock symbol, it should be on part of the browsers toolbars and not in the web page itself. You've had article before about how people are fooled by a padlock symbol appearing anywhere.

http://www.theregister.co.uk/2006/06/07/why_phishing_works/

Oi, thick as shit anonymous coward. It was google throwing the error. It didn't return any results - only the error. Do you need a picture? Hence blame google, not the site I was trying to find. Next time try reading and then you might understand as clearly you don't. And no, it's no longer giving the error; everything is fine with the world again.

"The difference between straight credit card payment and WorldPay is the speed the money is debited."

No - its down to how the merchant builds their web site. Payment can be taken either way using worldpay and how the merchant operates their business is purely a business process.

Worldpay can be integrated just like any other payment gateway (including from the banks) so that the process is just the same.

Its just a matter of choice from the trader whether they want to risk holding card details themselves or allow a 3rd party to take the risk and have to pay more comission. A risk we are happy to place in Worldpays hands.

There is nothing to stop the trader operating like you suggest regardless of the whether the payment method is worldpay or direct through a bank/credit card company.

We could have a direct credit card facility like you mention and it would be totally up to us when we take the payment and when we ship the goods, similarly if we use worldpay we can select whether to take the payment immediately or do an authorise only transaction and then take the actual payment when we ship the goods.

The problem you had was with a crap trader and that can happen whether you pay by cheque, over the phone or online, whether you pay by paypal, direct by credit card or via secpay/world pay etc.

Put the blame where it lies, with the trader.

I see no need to call me a thick shit.

If I misunderstood your posting and was perhaps a little terse in my reply I apologise, however it does not change the fact that a 403 error is a general error thrown by a web server when something goes wrong. Perhaps it could be a little more helpful, explain more and give you the option to try again or something I'm not sure what you expect it to do when an error happens. Errors happen from time to time and this one could happen on any web site anywhere and the same sort of message would be displayed.

Clearly users need to be educated to understand what they see on the internet and what precautions to take.

Simply a matter of the merchant logging on to worldpay, typing in the transaction number, click view transaction and click on refund full payment. Takes about 30 seconds at most. Much the same as any other payment gateway of any type.