If you have to ask, you don't want to do it. There is another solution that allows for essentially identical business logic - store the card number with your gateway.
Authorize.net provides Customer Information Manager. Quantum Gateway provides "quantum vault". Last time I looked paypal/google checkout didn't have this, they may now. Amazon payments may have something like this. There are also a number of startups whose names escape me at the moment who purport to solve payments. http://www.authorize.net/solutions/merchantsolutions/merchantservices/cim/http://www.authorize.net/solutions/merchantsolutions/merchantservices/cim/ http://www.quantumgateway.com/features.php Basics of how it works: You and your customer have a secure session. You get and send your customers's card number to the gateway (again over a secure session) The gateway provides you a unique identifier. In the future, when you want to charge that customer's card you send the gateway the unique identifier instead of the full card. If you want to chat more about specifics, send me an email offline. Ted On Oct 21, 4:03 am, django_jedi <pemaq...@gmail.com> wrote: > Hello all, > > Regarding Django and e-commerce - has anyone ever built a site that > stores credit card information for delayed processing? In other > words, the customer makes a purchase, but the Web site "remembers" > their information for future purchases? > > If you have, what special considerations are there for security, > storage in database, etc. > > Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
