An example Braintree integration with the GraphQL API using Ruby on Rails. Forked from braintree/braintree_rails_example.

1. Install bundler:

   gem install bundler

2. Bundle:

   bundle

3. Copy the contents of example.env into a new file named .env and fill in your Braintree API credentials. Credentials can be found by navigating to Account > My User > View Authorizations in the Braintree Control Panel. Full instructions can be found on our support site.

4. Start rails:

   rails server

You can deploy this app directly to Heroku to see the app live. Skip the setup instructions above and click the button below. This will walk you through getting this app up and running on Heroku in minutes.

Unit tests do not make API calls to Braintree and do not require Braintree credentials. You can run this project's unit tests by calling rake (or rails -R spec) on the command line.

Integration tests make API calls to Braintree and require that you set up your Braintree credentials. You can run this project's integration tests by adding your sandbox API credentials to .env and calling rake spec:integration (or rails spec:integration) on the command line.

You can run both unit and integrations tests by calling rake spec (or rails spec) on the command line.

Sandbox transactions must be made with sample credit card numbers, and the response of a Braintree::Transaction.sale() call is dependent on the amount of the transaction.

• Run rails s -b 0.0.0.0 when launching Rails server to listen on all interfaces.

• Found a bug? Have a suggestion for improvement? Want to tell us we're awesome? Submit an issue
• Trouble with your integration? Contact Braintree Support / [email protected]
• Want to contribute? Submit a pull request

This code is provided as is and is only intended to be used for illustration purposes. This code is not production-ready and is not meant to be used in a production environment. This repository is to be used as a tool to help merchants learn how to integrate with Braintree. Any use of this repository or any of its code in a production environment is highly discouraged.