Braintree v0.7.0 API Reference

Modules

A native Braintree client library for Elixir. Only a subset of the API is supported and this is a work in progress. That said, it is already uned in production, and any modules that have been implemented can be used

Add-ons and discounts are created in the Control Panel. You cannot create or update them through the API

Generate a token required by the client SDK to communicate with Braintree

CreditCard structs are not created directly, but are built within responsees from other endpoints, such as Braintree.Customer

You can create a customer by itself, with a payment method, or with a credit card with a billing address

Add-ons and discounts are created in the Control Panel. You cannot create or update them through the API

A general purpose response wrapper that is built for any failed API response

Base client for all server interaction, used by all endpoint specific modules. This request wrapper coordinates the remote server, headers, authorization and SSL options

Create, update, find and delete payment methods. Payment methods may be a CreditCard or a PaypalAccount

Create a payment method nonce from an existing payment method token

Find, update and delete Paypal Accounts using PaymentMethod token

Plans represent recurring billing plans in a Braintree merchant account. The API for plans is read only

The settlement batch summary displays the total sales and credits for each batch for a particular date. The transactions can be grouped by a single custom field’s values

A record contains details for a transaction in a summary

Manage customer subscriptions to reocurring billing plans

The functions contained in the Braintree.Testing.CreditCardNumbers module provide credit card numbers that should be used when working in the sandbox environment. The sandbox will not accept any credit card numbers other than the ones listed below

These are vendor specific numbers that will always fail verification

The functions contained in this module provide pre-defined nonces that can be used when working with the sandbox. Nonces are preferred over credit card numbers when testing payment methods

Create a new sale

General purpose utility functions

XML dumping tailored to encoding params sent by Braintree

XML encoding tailored to dumping Braintree compatible params

Exceptions

Raised at runtime when a config variable is missing