Both paypal and google require redirection to their sites. The workflow is more complex that needs to be.
There is this: http://www.scribd.com/doc/30661771/Web2py-Paypal-Integration Massimo On Jun 1, 8:54 pm, Richard <[email protected]> wrote: > would be great if web2py had a robust Paypal solution, which by > extension would support credit cards too. > > Though maybe this is more difficult than it sounds - I know Django has > not yet achieved this. > Recently I signed up for a conference that used a Django registration > system and the Paypal support was extremely fragile. To pay it > redirected you to PayPal and then if you pressed back before > completing it would list you as paid anyway and wouldn't let you pay > again! > > On Jun 1, 11:21 pm, mdipierro <[email protected]> wrote: > > > good point. I was not aware of that. > > > On Jun 1, 2:04 am, Richard <[email protected]> wrote: > > > > 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_Min...... > > > > darn... > > > > If that does rule out non-US developers perhaps it doesn't belong in > > > trunk. > > > > Richard > > > > On Jun 1, 4:38 pm, Richard <[email protected]> wrote: > > > > > paypal is definitely complex, but it is also popular! > > > > > On Jun 1, 12:16 pm, mdipierro <[email protected]> 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 <[email protected]> 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 <[email protected]> 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.
