Timeline for Storing credit card details
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 23, 2013 at 21:17 | history | edited | Zistoloen | CC BY-SA 3.0 |
Formatting + clarification
|
| Jun 23, 2013 at 20:07 | comment | added | Fiasco Labs | For an example, one such offering is Authorize.net Customer Information Manager (CIM) authorize.net/solutions/merchantsolutions/merchantservices/cim and since recurring billing was mentioned Automated Recurring Billing (ARB) authorize.net/solutions/merchantsolutions/merchantservices/… You can store them, but they'll never be safe. In the end you will pay about what the services would have cost you in lost reputation, lost sales, fines from your processor and any litigation that comes from data compromise. | |
| Jul 16, 2010 at 12:37 | comment | added | Milner | +1 for the idea of never storing CCs in your database. Our payment gateway provider stores all that information now, which is a huge relief on our security exposure. | |
| Jul 16, 2010 at 9:53 | history | answered | Whisk | CC BY-SA 2.5 |