Skip to content
Balanced API library in ruby.
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
doc remove
lib 1.2.1
scenarios Add account and settlement scenarios. Update scenarios.
snippets Account and Settlement snippets
spec Fix tests
.gitignore Get scenario.cache from Github when rendering scenarios.
.rspec Add basics for specs to run properly.
.ruby-gemset Add ruby-gemset and ruby-version
.ruby-version default to ruby 2.1.5
.travis.yml Test on 1.8.7, 1.9.3, 2.1.1 v1.2
Gemfile Hook into webmock in tests as workaround for Faraday VCR bug
Guardfile adds guard+rspec support
LICENSE Update LICENSE correct example scripts link
Rakefile Rakefile updates
balanced.gemspec Reduce upper Faraday bounds to <= 0.9.0


Online Marketplace Payments

Build Status Code Climate

v1.x requires Balanced API 1.1. Use v0.x for Balanced API 1.0.


Add this line to your application's Gemfile:

gem 'balanced'

And then execute:

$ bundle

Or install it yourself as:

$ gem install balanced

Documentation & Usage


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Write your code and unit tests
  4. Ensure all tests still pass (bundle exec rspec)
  5. Commit your changes (git commit -am 'Add some feature')
  6. Push to the branch (git push origin my-new-feature)
  7. Create new pull request


The spec suite is a work in progress. Existing specs can either be run using guard or rake.


$ bundle exec guard


$ rake spec

We use VCR to stub out and save http interactions. Cassettes are not stored in the repo. They are generated the first time the spec suite is run and stored in spec/cassettes. To clear them and regenerate:

$ rm -rf spec/cassettes


All issues should be documented at balanced-ruby/issues



To render executable files from scenario templates run rake render_executables Check /scenarios and make sure each scenario has an executable.rb file


To delete previously generated executable files run rake delete_executables


After generating executable files, make sure they are valid Ruby files by running rspec scenarios/execute.rb from the root directory


SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)

The machine's Ruby/OpenSSL environment can't find any root certificates to trust. Please refer here to find the best solution for your environment.

Something went wrong with that request. Please try again.