Commits

Steven Kryskalla  committed d53c28a

docs: pro/cons of using stripe and some tweaks

  • Participants
  • Parent commits db7f8b9
  • Tags 0.2

Comments (0)

Files changed (1)

File docs/philosophy.rst

 Philosophy
 ==========
 
-* inspired by `thylacine`_, which is a rails app that lets you sell a single
+Some notes on how itemshop was created:
+
+* it was partially inspired by `thylacine`_, which is a rails app that lets you sell a single
   digital download (with stripe)
 
-* this isn't a full ecommerce platform / shopping cart / online store (like django's
+* it is not a full ecommerce platform / shopping cart / online store (like django's
   `Satchmo`_), but could be used to build something like that, see the demos for
   some ideas
 
-* this is also a little experiment in re-usable apps; the :class:`ItemBP` class is meant
+* it is an attempt at creating a re-usable app; the :class:`ItemBP` class is meant
   to be overridden, have new routes added to it, integrated with a larger app, etc.
 
+Reasons **for** using `stripe`_:
+
+* no monthly fee or setup fee, just 2.9% + 30¢ for each transaction
+* their JS library (``stripe.js``) allows you to integrate credit card processing into your site, no redirects, no externally hosted pages, etc.
+* nice Python library and REST API
+
+Reasons **not to use** stripe:
+
+* you have to live in the US to sign up for an account
+* it doesn't allow users to use their existing Paypal, Google Checkouts,
+  Amazon Payments, etc. accounts
+* if users are more comfortable with using services like Paypal, they may
+  be wary of entering a credit card number directly on your site
+
 .. _thylacine: https://github.com/2tablespoons/thylacine
 .. _Satchmo: http://www.satchmoproject.com/
+.. _stripe: http://www.satchmoproject.com/
 
 Sensitive information
 ---------------------
 the form gets submitted without javascript, you won't get the raw credit card
 data.
 
+Even though you do not need to host your site with HTTPS, it's probably best
+if your site is hosted with HTTPS anyway, to reaffirm with users that the
+payment process is secure.
+
 Persistence
 -----------
 
 ``stripe_token``.
 
 The demos include some Javascript validation. In my opinion, you should
-validate using javascript (or AJAX) because A.) the stripe.js API validates
-the credit card information for you, and returns a decent error message B.)
+validate using javascript (or AJAX) because **A.)** the stripe.js API validates
+the credit card information for you, and returns a decent error message **B.)**
 you should not be sending users' credit card information to your server for
-validation, and C.) you want to avoid doing a page refresh, which will clear
+validation, and **C.)** you want to avoid doing a page refresh, which will clear
 the credit card fields and annoy users who will then have to reenter their
 information.