An Elixir library for working with Stripe.
The old 1.x.x line of releases has been kept and is being published separately for backwards compatibility, since 2.0 was a complete rewrite. To contribute to that line (bugfixes, mainly), create pull requests against the 1.x.x branch.
The actively developed line of releases is 2.x.x and is contained within the master branch. New features are being added to this line of releases, so to develop this library further, create pull requests against the master branch.
2.x.x Works with Stripe API version 2018-05-21
Install the dependency:
{:stripity_stripe, "~> 2.0"}Next, add to your applications:
Not necessary if using elixir >= 1.4
defp application do
[applications: [:stripity_stripe]]
end
## Configuration
To make API calls, it is necessary to configure your Stripe secret key.
```ex
use Mix.Config
config :stripity_stripe, api_key: "YOUR SECRET KEY"Some Stripe API endpoints support returning related objects via the object expansion query parameter. To take advantage of this feature, stripity_stripe accepts
a list of strings to be passed into opts under the :expand key indicating which objects should be expanded.
For example, calling Charge.retrieve("ch_123") would return a charge without expanding any objects.
%Charge{
id: "ch_123",
balance_transaction: "txn_123",
...
}However if we now include an expansion on the balance_transaction field using
Charge.retrieve("ch_123", expand: ["balance_transaction"])We will get the full object back as well.
%Charge{
id: "ch_123",
balance_transaction: %BalanceTransaction{
id: "txn_123",
fee: 125,
...
},
...
}For details on which objects can be expanded check out the stripe object expansion docs.
Click to expand
Works with API version 2015-10-16
Install the dependency:
{:stripity_stripe, "~> 1.6"}Next, add to your applications:
defp application do
[applications: [:stripity_stripe]]
endTo make API calls, it is necessary to configure your Stripe secret key (and optional platform client id if you are using Stripe Connect):
use Mix.Config
config :stripity_stripe, secret_key: "YOUR SECRET KEY"
config :stripity_stripe, platform_client_id: "YOUR CONNECT PLATFORM CLIENT ID"To customize the underlying HTTPoison library, you may optionally add an :httpoison_options key to the stripity_stripe configuration. For a full list of configuration options, please refer to the HTTPoison documentation.
config :stripity_stripe, httpoison_options: [timeout: 10000, recv_timeout: 10000, proxy: {"proxy.mydomain.com", 8080}]If you start contributing and you want to run mix test, first you need to export STRIPE_SECRET_KEY environment variable in the same shell as the one you will be running mix test in. All tests have the @tag disabled: false and the test runner is configured to ignore disabled: true. This helps to turn tests on/off when working in them. Most of the tests depends on the order of execution (test random seed = 0) to minimize runtime. I've tried having each tests isolated but this made it take ~10 times longer.
export STRIPE_SECRET_KEY="yourkey"
mix test
I've tried to make the API somewhat comprehensive and intuitive. If you'd like to see things in detail be sure to have a look at the tests - they show (generally) the way the API goes together.
In general, if Stripe requires some information for a given API call, you'll find that as part of the arity of the given function. For instance if you want to delete a Customer, you'll find that you must pass the id along:
{:ok, result} = Stripe.Customers.delete "some_id"For optional arguments, you can send in a Keyword list that will get translated to parameters. So if you want to update a Subscription, for instance, you must send in the customer_id and subscription_id with the list of changes:
# Change customer to the Premium subscription
{:ok, result} = Stripe.Customers.change_subscription "customer_id", "sub_id", [plan: "premium"]Metadata (metadata:) key is supported on most object type and allow the storage of extra information on the stripe platform. See test for an example.
That's the rule of thumb with this library. If there are any errors with your call, they will bubble up to you in the {:error, message} match.
# Example of paging through events
{:ok, events} = Stripe.Events.list(key, "", 100) # second arg is a marker for paging
case events[:has_more] do
true ->
# retrieve marker
last = List.last( events[:data] )
case Stripe.Events.list key, last["id"], 100 do
{:ok, events} -> events[:data]
# ...
end
false -> events[:data]
endStripe Connect allows you to provide your customers with an easy onboarding to their own Stripe account. This is useful when you run an e-commerce as a service platform. Each merchant can transact using their own account using your platform. Then your platform uses Stripe's API with their own API key obtained in the onboarding process.
First, you need to register your platform on Stripe Connect to obtain a client_id. In your account settings, there's a "Connect" tab, select it. Then fill the information to activate your connect platform settings. The select he client_id (notice there's one for dev and one for prod), stash this client_id in the config file under
config :stripity_stripe, platform_client_id: "ac_???"or in an env var named STRIPE_PLATFORM_CLIENT_ID.
Then you send your users to sign up for the stripe account using a link.
Here's an example of a button to start the workflow: Connect with Stripe
You can generate this URL using:
url = Stripe.Connect.generate_button_url csrf_tokenWhen the user gets back to your platform, the following url (redirect_uri form item on your "Connect" settings) will be used:
//yoursvr/your_endpoint?scope=read_write&code=AUTHORIZATION_CODE
or
//yoursvr/your_endpoint?error=access_denied&error_description=The%20user%20denied%20your%20request
Using the code request parameter, you make the following call:
{:ok, resp} -> Stripe.Connect.oauth_token_callback code
resp[:access_token]resp will look like this:
%{
token_type: "bearer",
stripe_publishable_key: PUBLISHABLE_KEY,
scope: "read_write",
livemode: false,
stripe_user_id: USER_ID,
refresh_token: REFRESH_TOKEN,
access_token: ACCESS_TOKEN
}You can then pass the access_token to the other API modules to act on their behalf.
See a demo using the Phoenix framework with the bare minimum to get this working.
The tests are currently manual as they require a unique OAuth authorization code per test. You need to obtain this code manually using the stripe connect workflow (that your user would go through using the above url).
First, log in your account. Then go to the following url: https://dashboard.stripe.com/account/applications/settings
Create a connect standalone account. Grab your development client_id. Put it in your config file. Enter a redirect url to your endpoint. Capture the "code" request parameter. Pass it to Stripe.Connect.oauth_token_callback or Stripe.Connect.get_token.
Feedback, feature requests, and fixes are welcomed and encouraged. Please make appropriate use of Issues and Pull Requests. All code should have accompanying tests.
Please see LICENSE for licensing details.
Why another Stripe Library? Currently there are a number of them in the Elixir world that are, well just not "done" yet. I started to fork/help but soon it became clear to me that what I wanted was
- an existing/better test story
- an API that didn't just mimic a REST interaction
- a library that was up to date with Elixir > 1.0 and would, you know, actually compile.
- function calls that returned a standard
{:ok, result}or{:error, message}response
As I began digging things up with these other libraries it became rather apparent that I was not only tweaking the API, but also ripping out a lot of the existing code... and that usually means I should probably do my own thing. So I did.
As of October 18th, Rob has graciously handed over the reins to the teams at Code Corps and Strumber. To addresses the concerns Rob mentioned above and update the high level api to work with all of the Stripe API Endpoints, they have since worked to release and stripity_stripe 2.0, which is now the actively developed line of releases.