Would the fact that the server processes the actual credit card number (even though it doesn't store it) make it so I would have to deal with PCI compliance stuff?
On Wednesday, April 10, 2013 7:24:08 PM UTC-4, Massimo Di Pierro wrote: > > You are right that what web2py does it server side. It does not store the > credit card info (not by default) but this allows the server to know if a > transaction went through or not. > I would like to see a prototype of client-size integration and a > server-side notifications of payments success/failure. > > massimo > > On Wednesday, 10 April 2013 14:02:20 UTC-5, David Ripplinger wrote: >> >> I'm recently learning about Stripe, and so far it seems like a great >> option for credit card processing. I noticed that there is a very simple >> add-on Massimo wrote to do Stripe charges and similar actions, but it does >> not seem to at all follow the pattern Stripe was intended to be used. >> Massimo's module requires actually entering the credit card number, but >> Stripe is built so that the web app doesn't need to ever see credit card >> numbers but instead use Stripe provided tokens that represent the credit >> card info that Stripe has saved. >> >> Stripe already has a server-side library that can be installed, which I >> intend to do (once I figure out how to do it successfully on >> pythonanywhere---for some reason it isn't working). But it would be nice, I >> think, to include Stripe's library in the out-of-the-box installation of >> web2py. >> >> What are people's thoughts on this subject? >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
