was looking around the Authorize docs and found:
"The merchant must have a U.S. based merchant bank account"
http://developer.authorize.net/guides/AIM/Introduction_to_AIM/AIM_Minimum_Requirements.htm
http://developer.authorize.net/guides/SIM/Introduction_to_SIM/SIM_Minimum_Requirements.htm

darn...

If that does rule out non-US developers perhaps it doesn't belong in
trunk.

Richard


On Jun 1, 4:38 pm, Richard <richar...@gmail.com> wrote:
> paypal is definitely complex, but it is also popular!
>
> On Jun 1, 12:16 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > Turns out that one has dependencies. Some in zope code.
> > This one seems a simpler option. Authorize.net is one of the best
> > options anyway.
>
> > Paypal and google have more complex workflow.
>
> > On May 31, 8:28 pm, Richard <richar...@gmail.com> wrote:
>
> > > sms handling and credit card payments - neat!
>
> > > That onlinepayment API you linked earlier (http://pypi.python.org/pypi/
> > > onlinepayment/1.0.0) offers more payment options, such as PayPal.
> > > Would it be worth integrating that instead?
>
> > > On May 31, 2:42 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > 1)
> > > > mail.settings.server='logging'
> > > > will pretend it is sending emails and just log them instead with a
> > > > warning.
>
> > > > 2) from gluon.contrib.sms_utils import SMSCODES, sms_email
> > > > sms_email(number,provider)
> > > > will send an sms via an email (free) where provider is in the list of
> > > > SMSCODES
>
> > > > 3) gluon/contrib/AuthorizeNet.py
> > > > look at the example at the bottom of the file. This is the easiest way
> > > > to accept credit card payments. It uses authorize.net API. I did not
> > > > write AuthorizeNet.py but adapted it from 
> > > > thishttp://www.johnconde.net/blog/integrate-the-authorizenet-aim-api-with...
> > > > and I am not sure what the license it. I think it is public domain,
> > > > anyway I emailed the author for confirmation and I am waiting for an
> > > > answer.

Reply via email to