drf-stripe-subscription
gringotts
drf-stripe-subscription | gringotts | |
---|---|---|
3 | 1 | |
99 | 476 | |
- | -0.2% | |
5.1 | 2.4 | |
4 months ago | 3 months ago | |
Python | Elixir | |
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.
drf-stripe-subscription
-
Suggested way to receive payments?
Hopefully this provides you with some ideas: https://github.com/oscarychen/drf-stripe-subscription
-
django and stripe connect for mulitparty payment system
https://github.com/oscarychen/drf-stripe-subscription this one is meant more for DRF
-
Django Stripe Subscription & Payment Integration
I hope this will be useful to you as I'm sure many of you also have small Django + SPA projects that need some kind of subscription and payment features but cannot justify spending too much time on it (especially all those side gig and weekend projects :) ). Feel free to clone/fork and make suggestions. More info in the README: https://github.com/oscarychen/drf-stripe-subscription
gringotts
-
Learning Ruby: Things I Like, Things I Miss from Python
Thanks.
> Stripe, including webhooks support, actively developed
I've looked into Stripity Stripe. For some time it was unmaintained and ended up getting taken over by another maintainer. It's also not as comprehensive as the official Stripe libraries. There's also a very big difference in using an official Stripe library and hoping for the best with a random one someone developed. Just skimming the code base it looks like the Checkout module is missing features that exist in the official Stripe library in every other supported language.
According to the README file for Stripity Stripe it's also using Stripe's API version from 2019. There have been multiple major API updates since then, and there's been an open issue since November 2020 to add support for newer API versions with no replies. Personally I would be using one of those major features too.
And this really is the point I'm trying to drive home. With Ruby, Python, Go, PHP, Node, Java and .NET these are problems you don't even need to think about. You just pick the payment provider's official SDK and start coding immediately, often times there's also an abundance of resources to implement the billing code itself into your app too through blog posts, official docs, YouTube videos, and even paid products like https://spark.laravel.com/. Stuff that makes integrating billing into your app (through Stripe, BrainTree and Paddle) being something you get done in 1 day instead of 3 months.
With Elixir it becomes weeks of comprehensive research, evaluating questionable libraries, opening PRs, and becoming a full time library developer just to get to the point where you could even maybe begin to start accepting payments with just Stripe.
> the best I've found is https://github.com/aviabird/gringotts
I asked the Gringotts developers if they would be supporting PayPal about 5 hours after they announced the project ~3 years ago. He said it was coming and to stay tuned. It's now ~3 years later and PayPal support isn't there. Neither is BrainTree or Paddle. Here's the open issue for PayPal support from 2018 (not by me, I asked on another site) https://github.com/aviabird/gringotts/issues/114. The Stripe integration is also missing a ton and hasn't been touched since 2018.
By the way, the Pay gem is really good. It's a smart abstraction and supports a ton of different subscription / 1 off payment use cases. Even complex ones like the type of app I was building.
> It's definitely a few weeks work to roll your own from scratch so to be honest I'd probably just integrate with Twilio and just pay for someone else to handle this for me.
Twilio ends up being 1 potential delivery method, it's not really someone you pay to solve the problem for you.
There's wanting to show notification in the app over websockets, saving them into a database, emailing them out only if they are unread, maybe sending an SNS through Twilio, Slack and other providers.
The noticed gem handles all of this for you (and supports Twilio too).
Notifications in general is another example where other frameworks have this solved in very good ways, but it becomes another example where you have to stop developing your app and start developing a notification library with Elixir.
At this point we've only talked about payments and notifications too. There's lots of other examples.
What are some alternatives?
dj-stripe - dj-stripe automatically syncs your Stripe Data to your local database as pre-implemented Django Models allowing you to use the Django ORM, in your code, to work with the data making it easier and faster.
stripity_stripe - An Elixir Library for Stripe
Vestaboard - An API Wrapper for Vestaboards written in Python
airbrake - An Elixir notifier to the Airbrake/Errbit. System-wide error reporting enriched with the information from Plug and Phoenix channels.
Paycord - Paid roles for discord using Stripe, Python, Flask & Docker
instrumental - An Elixir client for Instrumental
django-payments - Universal payment handling for Django.
elixtagram - :camera: Instagram API client for the Elixir language (elixir-lang)
forecast_io - Simple wrapper for Forecast.IO API
slack - Slack real time messaging and web API client in Elixir
ex_twiml - Generate TwiML with Elixir
currently - currently is a tool to display cards currently assigns on Trello.