pay VS bike_index

I believe he was talking about the gem called "pay", see https://github.com/pay-rails/pay

Pay for Ruby on Rails: Pay , a payments engine for Ruby on Rails, has made it easier to build custom webhooks.

Rails: Open-source maintainer @excid3 has released version 4.0 of Pay Rails with built-in support for Stripe Tax, metered billing, multiple subscription items, and pausing subscriptions. In addition, @JeffMorhous covers how to sell a one-time purchase in Rails with Stripe.

Again, you don't technically need to store anything in your database. However, I recommend storing at least the string ID of the Stripe Customer (which looks like cus_abc123) in your database. You can store this directly on the users or teams table, or create a separate table for storing Stripe Customer IDs and their relation to PaymentMethods and Subscriptions. Maintaining a separate table offers a bit more flexibility later if you decide to change from supporting single users to teams. It also separates concerns. Have a look at the open source pay-rails database schema or the cashier-stripe migrations for inspiration for modeling your database. If you’d like more suggestions about how to model your database to work well with SaaS, let me know on Twitter: @cjav_dev.

I recently laucnhed an app that captures screenshots, downloads source code, and monitors DNS records. reflect of it like the Wayback‍ Machine on steroids. I had a lot of fun working on this and wanted to share the source code and some concepts I learned. * Demo * Source Code # Concepts I learned * I took my first stab at metaprogramming. This came in handy when I needed to gather DNS records. I used the keys from an enum to dynamically instantiate different classes in Resolv. * I have a much better understanding of how to build subscription models now. I used the Pay Gem for the first time, and can't stress how helpful it is. You can see how I implemented it in the SubscriptionsContoller, ResumeSubscriptionsController, and the CreditCardsController. * I went headfirst into service objects. I structure them all using OpenStruct. I owe Nick Haskins' Playbook Thirty-Nine all the credit since I learned about that concept from his book. * I avoided using callbacks in favor of executing code in the controllers. I also started adding methods to my models that are more expressive like this. * I learned that has_one (and other similar methods) can be used to create more custom associations.

Version 3.0 of Pay Rails added support for Stripe Connect, all Stripe payment methods, and the ability to track multiple payment methods per customer.

I wrote the Pay gem which is officially sponsored by Stripe. It will help you handle the models, webhooks, one-time payments, subscriptions, etc.

Yeah :/ I think you have a project I'd pay for, though I'd totally encourage you to handle your own billing (I'm using https://github.com/pay-rails/pay on a new project) over jumping through the Marketplace hoops.

If you want to check out a real app using stripe, dig into bike_index : https://github.com/bikeindex/bike_index