security - Collecting Credit Card Information - not to collect payment -
i working in php on linux server mysql.
i have requirement (that have attempted talk them out of) collect credit card information users our company can use card numbers hold hotel rooms conference. not charging cards ourselves @ all, instead sending them hotel. need able download csv file , each time signs email go admin information.
i tried explain wasn't secure, several other developers have done them in past before working here.
my question is; there anyway make secure? if not there third party options make happen?
edit:
i appreciate has posted far, has made me want attempt less , less. if add answers simple explanations, oriented @ non-tech people, appreciated, in fact site source , links me great deal. haven't found sites explain in non-tech way.
it's bad idea storing card details. you're opening world of pain in form of pci-dss audits. not simple 'use encryption', need have processes in place securely manage encryption keys, schedule key rotation, securely log access , on , on... storing card details absolutely want avoid.
if have have in place, best option may (as company) take payments credit cards own merchant account, pay hotels separately (from bank account/whatever). act proxy client making payment hotel.
most payment gateways allow store card details securely, , charge @ later date (using token id returned gateway), useful here. wont able retrieve card details pass them through hotel in way, why need take payment, organise separate payment hotel.
its still quite undertaking though because lot of areas of pci-dss come play simplified solution.
you asked, here more information:
pci-dss payment card industry data security standard. it's set of guidelines apply company 'touches' cardholder data, in particular card number. touching literally means handling of data, having pass through network without ever being persisted disk enough mandate must comply, (though easier if don't persist details disk)
you didn't yet state part of world you're in, or how these card details captured (internet/telephone/in person). these details significant how can achieve compliance.
start taking @ pci-dss saq (self assessment questionnaires). these saq's minimum requirements companies do not store cardholder details disk, , should give impression of security needs in place across network , policies should applied across company.
as said, if you're thinking of storing card details things more complicated, because general rule saq no longer enough. need enrol assistance of qsa (qualified security assessor) visit , advise on best practice data storage , various other points come play. level of compliance you're looking @ yearly audits (carried out qsa), , quarterly network scans. take @ audit procedures detailed @ involved. in particular take @ section 3 , not underestimate difficulty of implementing proper key management.
in summary, full pci compliance costly. company already has pretty strong security policies cost of bringing in qsa , running quarterly scans , yearly audits alone cost $thousands.
Comments
Post a Comment