If the OP wants to process payements he cant use a crappy SSL certificate that can be decrypted by any old script kiddy I think there's even an extension in wireshark for this. So yes a couple of hundred pounds is reasonable.
I'm fairly confident there isn't any extension that'll allow you to bruteforce any resonable SSL on the wire.
There are two aspects of an SSL, #1 is the encryption that can be gained by using a freely generated SSL which will give you a big warning in your browser, despite doing the job just as well as a pay for SSL. Whilst you can pay for heavier levels of encryption, thats really not what the cost is associated with. I'd dare say the encryption is near foolproof.
The second aspect of an SSL is the trust facility. Basically the whole reason you pay for an SSL is to prove that the person you're communicating with securely is actually the person you think it is. This is very much a false economy given the history of the browser supported SSL providers being ****, and the fact that open source software solved this issue without paying people many moons ago. Irregardless, the more you pay is almost always more about upping the trust ratio, as this is what the public has been coerced to believe in. This is supposed to stop MITM attacks, which are the real threat.
Again if he wants to process payments it needs to be on its own server with a proper firewall and ids/ips system. This is all stuff needed to comply with PCI DSS (if you loose card details there is a maximum fine of 10k per card) so loose 100 card details there is a potential fine of 1 million pounds. I have never seen a company fined this much but I have seen fines that have put companies out of business.
No, it doesn't. He can process payments by passing them straight to a 3rd party payment portal, such as datacash, who'd take care of the PCI-DSS requirment providing him with some sort of customer-id and boolean for a transaction. For 'storing card' details, you need only keep the customer-id, and you can process future payments with datacash without keeping the card details on file (though the customer will need to re-enter their security number, which I believe even datacash can't keep on file).
There are a lot of sites big and small that don't do things properly ie sony/amazon. The UK has in my opinion the best security standards in the world. Crest have a 50% pass rate in the UK in the US crest is down to 10% thats why most Americans go for the tiger standard.
I tend to agree with you here.
A lot of companies don't do this properly because their coders either don't know what they're doing or where to find out more, or aren't given a resonable amount of time to do it right. I suspect many of these companies are in danger of massive fines, thus it is advised to pay someone who actually knows what they're talking about a decent amount, and actually listen to their advice.
This is why, I've agreed with the others in this thread that you need to be paying a living wage to get quality work (people oft seem to think all programmers live in their moms basement, and eat ramen exclusively. and thus can afford to work for below minimum wage and still develier a professional level of work) but unfortauntly too many people scrimp and save, because they don't know how to differentiate between quality work.
Processing payments costs a lot of money. So until you are turning over around half a million depending on margin its not worth considering. Natwest have really good API's as somebody mentioned before. 1k should be a good figure to look around for a site that integrates 3rd party payment just have a look at there other work
See this is where you should have started, but I'd go further than that. Everyone should be using a payment gateway, unless they have a strong reason for not doing so. So by default it's an entirely feasible project, and until you're a lot bigger, you shouldn't need to be worrying about anything such as PCI compliance.