Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
ruby client for balanced payments
Ruby
Pull request Compare This branch is 264 commits behind balanced:master.

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
doc
examples
lib
spec
.gitignore
.rbenv-version
.rspec
.travis.yml
CONTRIBUTORS
Gemfile
Guardfile
LICENSE
README.md
Rakefile
balanced.gemspec
upload_docs.rb

README.md

Balanced

Online Marketplace Payments

Build Status Code Climate

Installation

Add this line to your application's Gemfile:

gem 'balanced'

And then execute:

$ bundle

Or install it yourself as:

$ gem install balanced

Usage

See https://www.balancedpayments.com/docs/overview?language=ruby for tutorials and documentation.

Contributing

  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

Specs

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

Guard

$ bundle exec guard

Rake

$ 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

Issues

All issues should be documented at balanced-ruby/issues

Building Documentation

Documentation is built using YARD - http://rubydoc.info/docs/yard

export AMAZON_ACCESS_KEY_ID='xxx'
export AMAZON_SECRET_ACCESS_KEY='yyy' 
./upload_docs.rb

Troubleshooting

OpenSSL
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.