Skip to content
💳 Native elixir client for Braintree
Elixir
Branch: master
Clone or download
dependabot-preview and sorentwo Bump credo from 1.1.3 to 1.1.4 (#72)
Bumps [credo](https://github.com/rrrene/credo) from 1.1.3 to 1.1.4.
- [Release notes](https://github.com/rrrene/credo/releases)
- [Changelog](https://github.com/rrrene/credo/blob/master/CHANGELOG.md)
- [Commits](rrrene/credo@v1.1.3...v1.1.4)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Latest commit 076ec3b Sep 3, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
config
lib Fix `Transaction` field names: `apple_pay` and `android_pay_card` (#60) May 24, 2019
priv This patch correctly handles &amp; that might appear in the XML retur… Aug 23, 2016
test Add assertions for `Transaction.credit_card` field (#61) May 24, 2019
.formatter.exs Introduce formatter config and format all files Jun 18, 2018
.gitignore Add ex_doc dependency and configure doc generation Feb 3, 2016
.travis.yml Upgrade libraries and general CI configuration Mar 26, 2019
CHANGELOG.md Release v0.10.0 Mar 26, 2019
LICENSE.txt Initial commit with accoutrements Jan 28, 2016
README.md Release v0.10.0 Mar 26, 2019
mix.exs Release v0.10.0 Mar 26, 2019
mix.lock Bump credo from 1.1.3 to 1.1.4 (#72) Sep 4, 2019

README.md

Braintree

Build Status Hex version Hex downloads Inline docs

A native Braintree client library for Elixir.

Installation

Add braintree to your list of dependencies in mix.exs:

def deps do
  [{:braintree, "~> 0.9"}]
end

Once that is configured you are all set. Braintree is a library, not an application, but it does rely on hackney, which must be started. For Elixir versions < 1.4 you'll need to include it in the list of applications:

def application do
  [applications: [:braintree]]
end

Within your application you will need to configure the merchant id and authorization keys. You do not want to put this information in your config.exs file! Either put it in a {prod,dev,test}.secret.exs file which is sourced by config.exs, or read the values in from the environment:

config :braintree,
  environment: :sandbox,
  master_merchant_id: {:system, "BRAINTREE_MASTER_MERCHANT_ID"},
  merchant_id: {:system, "BRAINTREE_MERCHANT_ID"},
  public_key:  {:system, "BRAINTREE_PUBLIC_KEY"},
  private_key: {:system, "BRAINTREE_PRIVATE_KEY"}

Furthermore, the environment defaults to :sandbox, so you'll want to configure it with :production in prod.exs.

You may optionally pass directly those configuration keys to all functions performing an API call. In that case, those keys will be used to perform the call.

You can optionally configure Hackney options with:

config :braintree,
  http_options: [
    timeout: 30_000, # default, in milliseconds
    recv_timeout: 5000 # default, in milliseconds
  ]

Usage

The online documentation for Ruby/Java/Python etc. will give you a general idea of the modules and available functionality. Where possible the namespacing has been preserved.

The CRUD functions for each action module break down like this:

alias Braintree.Customer
alias Braintree.ErrorResponse, as: Error

case Customer.create(%{company: "Whale Corp"}) do
  {:ok, %Customer{} = customer} -> do_stuff_with_customer(customer)
  {:error, %Error{} = error}    -> do_stuff_with_error(error)
end

Searching

Search params are constructed with a fairly complex structure of maps. There isn't a DSL provided, so queries must be constructed by hand. For example, to search for a customer:

search_params = %{
  first_name: %{is: "Jenna"},
  last_name: %{
    starts_with: "Smith",
    contains: "ith",
    is_not: "Smithsonian"
  },
  email: %{ends_with: "gmail.com"}
}

{:ok, customers} = Braintree.Customer.search(search_params)

Or, to search for pending credit card verifications within a particular dollar amount:

search_params = %{
  amount: %{
    min: "10.0",
    max: "15.0"
  },
  status: ["approved", "pending"]
}

{:ok, verifications} = Braintree.CreditCardVerification.search(search_params)

Testing

You'll need a Braintree sandbox account to run the integration tests. Also, be sure that your account has Duplicate Transaction Checking disabled.

Merchant Account Features

In order to test the merchant account features, your sandbox account needs to have a master merchant account and it needs to be added to your environment variables (only needed in test).

Your environment needs to have the following:

  • Add-ons with ids: "bronze", "silver" and "gold"
  • Plans with ids: "starter", "business"
  • "business" plan needs to include the following add-ons: "bronze" and "silver"

PayPal Account Testing

PayPal testing uses the mocked API flow, which requires linking a sandbox PayPal account. You can accomplish that by following the directions for linked paypal testing.

License

MIT License, see LICENSE.txt for details.

You can’t perform that action at this time.