The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Pay Alternatives
Similar projects and alternatives to pay
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Stripe.Net
Stripe.net is a sync/async .NET 4.6.1+ client, and a portable class library for stripe.com.
-
cashier-stripe
Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
saasblog
Ruby on Rails SaaS blog with Stripe. Active Subscribers can view premium posts. User can select Plan and subscribe. User can manage subscription via Stripe Billing Portal.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
pay reviews and mentions
-
Implement paypal in my Rails 6 app
I believe he was talking about the gem called "pay", see https://github.com/pay-rails/pay
-
June Stripe Developer Digest
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.
- PayPal checkout integration with v2 API
-
DB Design for SaaS Subscriptions
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.
-
User registration for SaaS businesses - with a bonus!
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.
-
Help with simple payment app! Which components can I use to build a full stack Rails and Hotwire based page, that can take subscription based payments?
I'd suggest checking out the pay gem. It won't do everything for you, but it'll get you part of the way.
-
New Episode! Chris Oliver on Code and the Coding Coders who Code it
Pay gem
- Payments Engine for Ruby on Rails
- Pay – Payments Engine for Ruby on Rails
-
A note from our sponsor - WorkOS
workos.com | 23 Apr 2024
Stats
pay-rails/pay is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of pay is Ruby.
Sponsored