pay
cashier-stripe
pay | cashier-stripe | |
---|---|---|
17 | 12 | |
1,818 | 2,327 | |
0.9% | 0.3% | |
9.1 | 8.7 | |
2 days ago | 14 days ago | |
Ruby | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pay
-
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
cashier-stripe
-
June Stripe Developer Digest
Laravel Cashier Stripe v14.12.2: The latest version of Laravel Cashier Stripe , v14.12.2, focuses on improving the handling of the “payment_method.automatically_updated” webhook.
-
January Stripe Developer Digest
Laravel Cashier Stripe released v14.4.0 – v14.7.0, adding support for Laravel 10, stripe-php v10, and the latest version of the Stripe API.
-
November Stripe Developer Digest
Laravel Stripe released version 14.3.0.
-
Laravel Spark—missing basic features?
Currently, Spark allow only to change your subscription, not adding new ones. Why is that? This was address already 2 years ago on Laravel Cashier https://github.com/laravel/cashier-stripe/issues/922
-
October Stripe Developer Digest
Laravel Cashier Stripe has released version 14.2 with support for guest checkout and a rebranded shipped receipt template.
-
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.
-
April Developer Digest: ACH Direct Debit now available
Check out the latest updates to Laravel Cashier.
-
January Developer Digest: The new Payment Links API, automatic payment methods, and Checkout updates
Versions 13.6.0 and 13.6.1 of Laravel Cashier are out.
-
November Developer Digest: The *new* Payment element, Node SDK + Cloudflare Workers, and Stripe Identity samples
Learn how to get started with Cashier Stripe and Cashier Paddle. [Video course from Dries Vints, co-maintainer of Cashier Stripe and Cashier Paddle]
- Executing the right controller method based on a route's parameter
What are some alternatives?
Stripe.Net - Stripe.net is a sync/async .NET 4.6.1+ client, and a portable class library for stripe.com.
cashier-paddle - Cashier Paddle provides an expressive, fluent interface to Paddle's subscription billing services.
Stripe - Java library for the Stripe API.
vue-stripe - Stripe Checkout & Elements for Vue.js
paddle-billing-sdk - Paddle Billing API SDK for Node
deno - A modern runtime for JavaScript and TypeScript.
bike_index - All the code for Bike Index, because we love you
stripe-node - Node.js library for the Stripe API.
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.
Stripe - Stripe iOS SDK
stripe-android - Stripe Android SDK
laravel - A package to easily integrate your Laravel application with Lemon Squeezy.