For credit card companies to allow you to do that sort of behaviour, your site must be PCI-DSS compliant, and your site/code will be audited once a year (at your cost) by your acquiring bank. The requirements for PCI-DSS compliance are widely available on the internet.
Due to these reasons, unless you will be processing a large number of transactions, it is normally easier to use a payment processor that provides the same features (eg worldpay, etc). Cheers Tom On Thu, Oct 21, 2010 at 12:03 PM, 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. > > -- 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.
