beam-community/stripity-stripe
Description and use
**Summary**
Stripity‑Stripe (beam‑community/stripity‑stripe) is an actively‑maintained Elixir library that wraps the Stripe API, letting developers add billing, checkout, and other payment‑service‑provider (PSP) flows to their applications with minimal boilerplate. With over 1 000 GitHub stars, frequent releases (last update 2026‑05‑11) and solid community adoption, it is ready for a production pilot in any Elixir‑based backend.
**Value**
The library abstracts Stripe’s REST endpoints into idiomatic Elixir functions and structs, accelerating the implementation of monetisation features such as subscription management, one‑off payments, and webhook handling. By handling request signing, pagination, and error mapping, it reduces boiler‑plate code, lowers the risk of integration bugs, and lets teams focus on business logic rather than low‑level API details.
**Practical adoption path**
- **Add the dependency** – include
{:stripity_stripe, "~> x.y"}inmix.exsand runmix deps.get. - **Configure credentials** – set
STRIPE_SECRET_KEY(or configure viaconfig.exs). - **Use the provided modules** – call
Stripe.Customer.create/1,Stripe.Subscription.list/1, etc., and hook into the built‑in webhook verification helpers for event processing. - **Extend or replace** – the library is modular; you can swap out the HTTP client or add custom middleware if needed.
**Production readiness**
- **Activity & adoption**: 1 067 stars, 376 forks, recent commits, and multiple downstream projects already depend on it.
- **Stability**: Semantic versioning is followed; major breaking changes are rare and documented.
- **Ecosystem fit**: Pure Elixir implementation integrates cleanly with Phoenix, Ecto, and other BEAM tools.
- **Risks**: License and security posture need a final check, but no major metadata issues have been identified. Overall, Stripity‑Stripe is a high‑confidence OSS candidate for production use in any Elixir‑based payment service.
Use in a workflow
beam-community/stripity-stripe helps integrate monetization, billing, or PSP flows faster.
- integrate billing or checkout
- evaluate PSP flows
- automate payment operations
Limitations and review notes
High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.
- Source: github
- Language: Elixir
- Record date: 2026-09-05T17:30:49.404Z