pay VS stripe-node

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

Head to Stripe and register if you haven't already. We can use the Stripe API in Test Mode to build the e-commerce app. You can add a bank account and get verified later when you're ready to start collecting real payments.

Stripe published its 2023 annual letter last week. Much like the previous edition it was filled with a lot of interesting nuggets. Stripe has a strong history of being fairly transparent with its practices. These range from engineering challenges through its blogs as well as thought leadership in the financial and entrepreneurship space. I personally like the writing style of this letter as it doesn’t seem corporate or stuffy. Instead it is filled with humorous anecdotes, quirky observations and intelligent historical narratives which make it a compelling read. You can read the letter here → Stripe Annual Letter: 2023

Stripe – payments

Imagine you want to create an API endpoint that allows users to register in your backend, while simultaneously making a payment towards Stripe. This could be for something that's a subscription-based service, where you charge people for access to something.

Our app – Upollo – connects with your app event data (like Segment) and payment data (like Stripe) to analyze your users and instantly figure out if someone is an important player in your industry. We also help you convert more users, reduce churn, and expand single seats to teams within a company. We're SOC 2 certified and we take data security very seriously.

That's cool - my page is still under development. But have you tried running it on something like https://stripe.com/ to see if the generates interesting results. Could share results here? DMing you also

Stripe is a great example of this as their margins on the side are visible with a faint line. All content is inside this except for some images and decorations.

Before going through the integration process, you need to sign up for a Stripe account. Go to the Stripe website and follow the registration process. Once you're signed in, you'll have access to the API keys needed to communicate between the server and your Stripe.

While Poe from Quora is extempted from stripe restricted businesses, startups like GirlfriendGPT get bullied! The functionality of both AI chat engines is the same.