Popularity
7.5
Stable
Activity
0.0
Stable
180
13
24
Monthly Downloads: 14
Programming language: Elixir
License: MIT License
Tags:
Third Party APIs
commerce_billing alternatives and similar packages
Based on the "Third Party APIs" category.
Alternatively, view commerce_billing alternatives based on common mentions on social networks and blogs.
-
ethereumex
Elixir JSON-RPC client for the Ethereum blockchain 0x063D3d782598744AF1252eBEaf3aA97D990Edf72 -
MongoosePush
MongoosePush is a simple Elixir RESTful service allowing to send push notification via FCM and/or APNS. -
cashier
Cashier is an Elixir library that aims to be an easy to use payment gateway, whilst offering the fault tolerance and scalability benefits of being built on top of Erlang/OTP -
airbrake
An Elixir notifier to the Airbrake/Errbit. System-wide error reporting enriched with the information from Plug and Phoenix channels.
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
Promo
coderabbit.ai
Do you think we are missing an alternative of commerce_billing or a related project?
README
Commerce.Billing
Payment processing library for Elixir. Based on Shopify's ActiveMerchant ruby gem
Supported Gateways
- Bogus
- Stripe
Advantages of Elixir
- Fault tolerant: Each worker is supervised, so a new worker is started in the event of errors. Network errors are caught and payment is retried (not yet working).
- Distributed: Run workers on different machines.
- Scalable: Run multiple workers and adjust number of workers as needed.
- Throughput: Takes advantage of all cores. For example on my laptop with 4 cores (2 threads per core), I can do 100 authorizations with Stripe in 10 seconds. Thats 864,000 transactions per day. ebay does 1.4M/day.
- Hot code swap: Update code while the system is running
Card processing example
alias Commerce.Billing
alias Billing.{CreditCard, Address, Worker, Gateways}
config = %{credentials: {"sk_test_BQokikJOvBiI2HlWgH4olfQ2", ""},
default_currency: "USD"}
Worker.start_link(Gateways.Stripe, config, name: :my_gateway)
card = %CreditCard{
name: "John Smith",
number: "4242424242424242",
expiration: {2017, 12},
cvc: "123"
}
address = %Address{
street1: "123 Main",
city: "New York",
region: "NY",
country: "US",
postal_code: "11111"
}
case Billing.authorize(:my_gateway, 199.95, card, billing_address: address,
description: "Amazing T-Shirt") do
{:ok, %{authorization: authorization}} ->
IO.puts("Payment authorized #{authorization}")
{:error, %{code: :declined, reason: reason}} ->
IO.puts("Payment declined #{reason}")
{:error, %{code: error}} ->
IO.puts("Payment error #{error}")
end
Road Map
- Support multiple gateways (PayPal, Stripe, Authorize.net, Braintree etc..)
- Support gateways that bill directly and those that use html integrations.
- Support recurring billing
- Each gateway is hosted in a worker process and supervised.
- Workers can be pooled. (using poolboy)
- Workers can be spread on multiple nodes
- The gateway is selected by first calling the "Gateway Factory" process. The "Gateway Factory" decides which gateway to use. Usually it will just be one type based on configuration setting in mix.exs (i.e. Stripe), but the Factory can be replaced with something fancier. It will enable scenarios like:
- Use one gateway for visa another for mastercard
- Use primary gateway (i.e PayPal), but when PayPal is erroring switch to secondary/backup gateway (i.e. Authorize.net)
- Currency specific gateway, i.e. use one gateway type for USD another for CAD
- Retry on network failure
License
MIT
@joshnuss is a freelance software consultant. [email protected]
*Note that all licence references and agreements mentioned in the commerce_billing README section above
are relevant to that project's source code only.