A comprehensive Elixir library for interacting with the Stripe API, supporting payments, customers, and subscriptions.
Stripity Stripe is an Elixir library that provides a full-featured client for the Stripe payment platform. It allows developers to integrate payment processing, manage customers and subscriptions, and handle Stripe Connect workflows directly from their Elixir applications. The library wraps Stripe's REST API with an idiomatic Elixir interface, simplifying complex financial operations.
Elixir developers building applications that require payment processing, subscription management, or e-commerce capabilities. It's particularly useful for teams using Phoenix or other Elixir web frameworks who need reliable Stripe integration.
Developers choose Stripity Stripe because it offers comprehensive, up-to-date coverage of Stripe's API with a clean Elixir-style interface. Its support for modern payment intents, configurable retries, and seamless testing with stripe-mock makes it a robust and maintainable choice over DIY implementations or outdated alternatives.
An Elixir Library for Stripe
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports all major Stripe features like Payments, Customers, Subscriptions, and Connect, ensuring comprehensive integration capabilities as listed in the key features.
Built-in support for SetupIntents and PaymentIntents, essential for SCA compliance in European markets, with clear examples in the README for intent-based workflows.
Allows object expansion to fetch nested related objects in single API calls, optimizing performance as detailed in the Note section on object expansion.
Offers customizable timeouts, retry logic via Hackney options, and integrates with stripe-mock for reliable offline testing, with Docker instructions provided.
Library releases are tightly coupled to specific Stripe API versions, requiring careful upgrades to avoid breaking changes, as shown in the version table in the README.
Testing requires running stripe-mock separately, often via Docker, which adds complexity for CI/CD pipelines or developers unfamiliar with containerization.
Demands explicit configuration for API keys, JSON libraries, and HTTP settings, which can be cumbersome compared to more automated or convention-over-configuration approaches.