duk wrote:I thought banks don't like this. I knew one bank asking all their merchants who are processing card-not-present transactions only through the EFTPOS, to apply for real-time gateway, because, even if the card details are stored in a PCI Compliant gateway, they are exposed to the merchant and their employees.
The vast majority of credit card theft comes from the interent. Hackers are getting good.
But when stuff is not stored online then its got to be safer, like when you hand your card to the restarant owner. Not much of a risk when its with the shop or restaurant owner, but a huge risk if your credit card details are permanently stored online.
I thnk people prefer to put their credit card details with the merchant account owner instead of it being permanently stored online in some online payment gateway's systems even when it is PCI compliant. PCI compliance is no guarantee of protection. The largest breach in e-commerce history where tens of milions of credit cards were stolen was from a PCI compliant real time payment gateway processor:
Check out:
Heartland data breach proves PCI compliance is not enough duk wrote:Also, in merchant's point of view, why process the transaction manually, when there is an option of automating it.
To easily identify when a fake transaction is attempted then to delete it so it doesn't get passed first base. So to answer your question, its all about preventing fraud and saving yourself from what could be huge cost.
There'as also a lot of people out there that don't want orders and credit cards charged online right away without them knowing about it. Some business owners like to have control. I do.
But I agree with you for businesses doing hgh transaction numbers a day. The real time system's automation is the only way to go.
duk wrote:If you want to vet the orders and check them (if the stock is available or the order is genuine) before processing then there is point in storing the card details and storing them manually. Even for this you can use some technique called triggered payment.
So the triggered payment technique sounds like its doing little more than emulating the manual payment gateway anyway, except that a manual payment gateway is a fair bit cheaper and you are not letting your customers credit card and identity details be permanently stored online in some online payment gateway's storage device. I know you will disagreee but stopping sensitive credit card and identity data from being stored online and removing it away from all the hackers and cyber-crooks I believe is a massive security advantage.
Over these last two weeks I've looked into things heaps, mainly because of what I've been reading about the new PCI DSS. And from where I stand if you are serious about protecting yourself and your cardholders then the manual payment gateways are the only way to go.
mAx