@Rob I have uploaded the code for your perusal to: getpaid- [email protected]
On Feb 10, 7:04 pm, Rob LaRubbio <[email protected]> wrote: > Is the code/config up somewhere I can take a look? That would help a lot. > I know I ran into problems similar to this with the payflowpro processor > when I missed a couple of steps. I also had this problem at the end since > my processor wasn't in the getpaid recipe so I had to manually add the egg > instead of using addPackages in the recipe. > > -Rob > > On Mon, Feb 9, 2009 at 11:21 PM, hannesc <[email protected]> wrote: > > > Recently I started the development of a payment processor for VCS, a > > South African company. I asked around for help, and it was suggested > > that I use one of the other payment processors, and just edit that > > according to my needs. > > > As VCS requires the user to be redirected to an external page, I found > > the Ogone processor to be the closest to what I need, and thus started > > working on that. I edited where needed (eg. Ogone uses GET, VCS uses > > POST), and once done, I created the egg. I included the egg into my > > buildout, but with no happiness. For some reason, GetPaid is not > > picking up the new Payment Processor. > > > Can anyone perhaps point me to some documentation that covers Payment > > Processor Development? I mean perhaps if I could get to that, I can > > figure out what I am doing wrong. > > > Thanks guys :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" 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/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
