pay VS Stripe

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.

In the Pay gem, we model all these tables and sync from Stripe using webhooks so that your local copy is always up-to-date and fast.

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'd suggest checking out the pay gem. It won't do everything for you, but it'll get you part of the way.

Pay gem

First let's introduce the tool: Sorbet is a gem developed by Stripe that aims to bring type notation syntax and type checking support for the Ruby ecosystem by utilizing the "Gradual typing" philosophy, it also provide type generation from YARD comments via the tapioca gem, allowing to grow alongside the already built Ruby codebase.

The problem is stripe.com charges 4.6% total in fees. Wise charges 1.89%.

For me Stripe is the peak for a product/company website:

https://stripe.com/

I heard some people admire https://linear.app/ but I don't see the appeal myself

Majority of websites often fall into one of two categories:

1. Traditional off the shelf template

2. Look cool but fail when it comes to usability and robustness (those featured on awwwards)

You could have the best service in the world, but if you have a payment gateway that leaves people feeling uncomfortable, you'll lose them. Not only that, but you have PCI compliance you would need to deal with and a slew of other things that are handled for you with a payment vendor like Stripe, Square, or PayPal.

Your payment and data is processed safely through Stripe. We are verified and also accept Paypal.

First you'll want to go to Stripe's website and setup an account. Then install Stripe with pip install stripe. In this example I'm using Flask for the backend and React for the frontend. The website is an e-commerce page for buying and selling skateboards. Now create some models for the product to sell and the receipts then run flask db init, flask db migrate, and flask db upgrade to create the database. My models look like so:

Kick uses a Payment Processor called Stripe

I did that with Vue and Laravel a few times. If you need Stripe data linked to a user account your best bet is Laravel Cashier. Otherwise you'll have to use the PHP SDK.

stripe allows issuing cards, similar to how cash app, Venmo and other payment platforms issues cards to users. I’ve personally never issued a card but the documentation is there and should be simple!

A verified Stripe account is one that has been examined and certified by Stripe as belonging to a real company. This indicates that Stripe has received all necessary information and documentation from the account holder and that Stripe has confirmed that the account is actually owned and run by an authorized company. Buy Verified Stripe Account