Advertisement
Guest User

Untitled

a guest
Mar 29th, 2017
151
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.15 KB | None | 0 0
  1. * Learn what makes Stripe great
  2. * Read about this book
  3. * Learn how the book is organized
  4.  
  5.  
  6. Before Stripe came onto the scene, alternatives for accepting payments online were either expensive, annoying, complicated, or all three. PayPal had (and still has) a large portion of the business, but the API is very old and the payment flow is not conducive to a modern application. To accept credit cards, you either you had to use PayPal or integrate at least three separate services: a merchant account, a credit card gateway, and a recurring subscription service. You had the responsibility to make sure every piece was secure, and all of the software that integrated them had to be maintained.
  7.  
  8. Stripe makes all of this irrelevant. You can create an account on Stripe's website and be making real live charges the next day with simple, easy to use APIs and documentation. The power of this is huge: you can go from idea to accepting payments in very little time, often less than a day.
  9.  
  10.  
  11. # Why this guide?
  12.  
  13. If Stripe is so easy to use, why read a whole book about it? There's a few reasons. Stripe's documentation often does not go far enough. It assumes that Stripe will always be available and responsive. It also only gives small or limited examples that don't directly apply to production applications.
  14.  
  15. This guide goes farther and deeper than Stripe's documentation. It builds up a complete production-level Rails application and covers every step along the way.
  16.  
  17. In this guide we're going to cover a basic Stripe integration and then expand upon it to cover things like background workers, subscriptions, marketplaces, audit trails, PCI compliance, and more. When you're done with the guide you should have a good grasp on how to build a complete, robust Stripe integration.
  18.  
  19.  
  20. # How does the guide work?
  21.  
  22. This guide builds an application to sell downloadable products. By the end of the book it will be a full marketplace where sellers can upload one-off and subscription content.
  23.  
  24. Each chapter has a GitHub discussion thread associated with it that you can get to by clicking on the Discuss button in the upper left-hand corner. Here, you can ask questions and give help to your fellow readers.
  25.  
  26.  
  27. # Who am I?
  28.  
  29. My name is Pete Keen. I've been working with the Stripe API for a little over three years now and have built many applications with it. In addition, I've worked with a wide variety of other payment systems at my full time and consulting jobs and learned quite a lot about how to handle payments in general.
  30.  
  31. # Conventions
  32.  
  33. ```
  34. Code examples are marked out like this.
  35. ```
  36.  
  37. Shorter code snippets are `marked` like this.
  38.  
  39. Links are [underlined]() and are all clickable from all of the electronic versions.
  40.  
  41.  
  42. # Reporting Bugs
  43.  
  44. Every technical book is going to have bugs, it's just the nature of the beast. To report a bug you can either use the "Report a bug" link in the book dropdown on any chapter page, or you can email it to bugs@petekeen.net.
  45.  
  46. # Versions
  47.  
  48. Versions of software used in the examples:
  49.  
  50. * Ruby 2.3.1
  51. * Rails 4.2.6
  52. * Stripe Ruby API 1.43.1
  53. * Devise 4.1.1
  54. * Paper Trail 5.2.0
  55. * PostgreSQL 9.4
  56.  
  57. The current version of the guide is v2.0.12. See the [Changelog]() for details about guide changes.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement