README.md in ebanx-1.3.1 vs README.md in ebanx-1.3.2

- old
+ new

@@ -1,6 +1,7 @@ # EBANX Ruby gem [![Build Status](https://travis-ci.org/ebanx-integration/ebanx-ruby.svg?branch=master)](https://travis-ci.org/ebanx-integration/ebanx-ruby) [![Code Climate](https://codeclimate.com/github/ebanx-integration/ebanx-ruby/badges/gpa.svg)](https://codeclimate.com/github/ebanx-integration/ebanx-ruby) [![Test Coverage](https://codeclimate.com/github/ebanx-integration/ebanx-ruby/badges/coverage.svg)](https://codeclimate.com/github/ebanx-integration/ebanx-ruby/coverage) + Gem to communicate with EBANX. Documentation: https://developers.ebanx.com/ ## Installation @@ -16,13 +17,21 @@ $ gem install ebanx ## Usage +#### Auth +```ruby +Ebanx.tap do |e| + e.integration_key = '<<< Your integration key >>>' + e.test_mode = true +end +``` + #### Create a new Boleto using Direct API ```ruby -response = ebanx.do_direct { +response = Ebanx.do_direct( operation: 'request', mode: 'full', payment: { name: 'João da Silva', email: 'joao@mailinator.com', @@ -40,11 +49,11 @@ state: 'DF', country: 'br', phone_number: '6130001111', due_date: (Time.now + 86400).strftime('%d/%m/%Y') } -} +) ``` ## Automated Tests We use minitest for testing this Gem. @@ -57,6 +66,6 @@ 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) -5. Create new Pull Request \ No newline at end of file +5. Create new Pull Request