Yeah, I saw that. I thought I would need to keep them around to do recurring
charges. However, it looks like authorize.net has a recurring solution, so I
won't need to keep the numbers around after all.

Why is it that all you have to do is ask a question publicly to immediately
find the solution yourself?

Thanks for you help,
Alex

On Tue, Aug 18, 2009 at 2:36 PM, kcharvey <[email protected]> wrote:

>
> Hey Alex,
>
> The default behavior is to NOT save credit card numbers (at least if
> you're using the Authorize.net module). You can turn the option on in
> the Site Settings, but Satchmo assumes that you don't want to.
>
> Kevin
>
> On Aug 18, 1:01 pm, Alex Robbins <[email protected]>
> wrote:
> > Hey guys, I am new to Satchmo and trying to figure out how exactly the
> > payment modules work.
> > The goal: Use satchmo, but have a custom payment module that saves
> > sensitive info like the credit card number to a Customer Information
> > Manager[1]. The client doesn't want credit card info on their server
> > any more.
> > I'm looking through the source, and it looks like this will be a large
> > amount of work. I could listen for a signal (maybe the pre_save on the
> > CreditCard model) to stop the save, but then I need to put the data
> > somewhere else...
> > Or maybe just redefining the credit card model to be a fake model that
> > makes http requests when it is saved or instantiated?
> >
> > Anyway, is there a good way to do this in Satchmo, or is it too much
> > against the grain of the existing code?
> >
> > Thanks,
> > Alex
> >
> > 1http://www.authorize.net/solutions/merchantsolutions/merchantservices.
> ..
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to