There is a nice article related to this topic on Smashing Magazine:
http://www.smashingmagazine.com/2010/06/02/getting-started-with-e-commerce-your-options-when-selling-online/comment-page-1/#comment-462851

Regards
Anand

On Jun 3, 10:23 pm, Richard <richar...@gmail.com> wrote:
> I would also trust someone known like PayPal more than the average
> website.
>
> Hopefully a good PayPal solution can be implemented like PHP has. But
> it's a lot of work for a hobby programmer.
>
> What do you think about having some kind of bounty system where people
> interested in a difficult feature like this could contribute money as
> an incentive for someone to implement it. On the uservoice page
> (http://web2py.uservoice.com) a lot of people are interested in DAL
> support for NoSQL databases.
> I have heard of other open source projects doing this, though they
> don't seem to have been overly successful.
>
> Richard
>
> On Jun 3, 11:39 am, howesc <how...@umich.edu> wrote:
>
> > I use paypal "Website Payments Standard" and the *best* part about
> > that is that while the user experience is crappy with the redirection,
> > i *never* learn the user's credit card number, and therefore don't
> > have to worry about regulations in how that info is handled (which
> > extends to your server logs if they log parameters).  So, just for
> > legal reasons i'll continue to avoid doing credit card processing on
> > my site.
>
> > cfh
>
> > On Jun 1, 8:59 pm, Miguel Goncalves <goncalvesmig...@gmail.com> wrote:
>
> > > Paypal has multiple workflows and products.
>
> > > The simplest one is "*Website Payments Standard*" where you direct the 
> > > user
> > > to the paypal website for payment. Not great for the user experience but
> > > workable and above all there is no monthly fee associated with it.
>
> > > Another version is "*Website Payment Pro*" where your visitors stay on 
> > > your
> > > website and your server contacts Paypal servers to validate the payment.
>
> > > One of the websites I administer has been using the payment standards and
> > > now is migrating to the pro version. Of course the software they use 
> > > (x-cart
> > > -php cart-) integrates nicely with paypal so I did not have to do much 
> > > work
> > > :)
>
> > > I think these 2 paypal methods would be the most interesting to have
> > > integrated in web2py since they both support credit cards processing and 
> > > are
> > > a cheap and easy way to support payments.
>
> > > -Miguel
>
> > > On Tue, Jun 1, 2010 at 7:58 PM, mdipierro <mdipie...@cs.depaul.edu> wrote:
> > > > 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 <richar...@gmail.com> 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 <mdipie...@cs.depaul.edu> wrote:
>
> > > > > > good point. I was not aware of that.
>
> > > > > > On Jun 1, 2:04 am, Richard <richar...@gmail.com> 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 <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