Can't your custom payment module be built in such a fashion to store all this data in some Model that has a key back to the proper Order it is attached to? Then you could pull it up via Django's standard treatment of related models.
On Mon, Oct 19, 2009 at 6:59 PM, Alex Hayes <[email protected]> wrote: > > I have built a custom payment module that talks with an Australian > provider NetRegistry and I have been cleaning up the authorisations > part however I have an issue. > > When you perform a pre-auth with NetRegistry they give you back a > transaction_id but also a pre_auth_id. The pre_auth_id is what must be > used when you complete a pre-auth, not the transaction_id. > > So, how can I attach some extra information to the transaction so that > I can retrieve the pre_auth_id when its time to process the pre-auth? > I could just store the pre_auth_id as the transaction_id however I > don't really want to lose that transaction_id. > > I was thinking that I could create a model that contains the extra > data and after I call record_payment in my custom payment module I > store this extra information. > > Is this the best thing to do? If I do this, will the model be picked > up by a syncdb? > > Thanks > Alex > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
