bitpay-client 2.4.0 → 2.5.1905

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: dae6ef526679f3cbcc49840dd2e1558913d38af7
-  data.tar.gz: e5dd36e2dbfcd8f715c381c4e89a4b44c28aaa50
+SHA256:
+  metadata.gz: ec9264c9adfd34beec539276916e9c6edc02f522e479c937e21fd1ae65f0bbb8
+  data.tar.gz: 91398067b63bde27f49a30a329d3ec4f653daa1981c255933be3a376f386634f
 SHA512:
-  metadata.gz: 8555438f87edbb9c2480f422bb5eb35b3433441dfebe9f8d2633e3ff74e96fca8bfc4f774353c9628021b05104115ae18512108a2e2514f24ac74aee2f6a9476
-  data.tar.gz: ac5da6a74b4b8ac4157c3ea3a4914277a6de32cc230f7ba6e580d022dfd08565c476bbec6bbab75b10e2d71bf71703558c8fda9f99e07ee21914e9bb066c7c98
+  metadata.gz: ef6c129c0d8a95221a8385301ce27928388ee6561afdbbef61efbea969be92b5e316f7dea8eefee4e1d15f7d0811d38dccf7503f9e34d32a6cc525e49a128b40
+  data.tar.gz: 36d60973b7f38b87ac15187fc5c82686ceba5f82577beafbaba66e4053ba9d23545063121e359cafb570efcd2384a9612573cf0289efc5582159204380261a9d

data/.gitignore

@@ -5,5 +5,9 @@ pkg
 .c9
 .ruby-version
 .ruby-gemset
-.pem.data
+*.swo
+*.swp
+bitpaykey.pem
+constants.txt
 coverage/
+.pem.data

data/.travis.yml

@@ -1,3 +1,8 @@
 sudo: false
 rvm:
-  - 2.2.2
+- 2.1.10
+- 2.2.5
+- 2.3.1
+- 2.4.5
+- 2.5.3
+- 2.6.1

data/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Change Log
+All notable changes to this project will be documented in this file.
+This project adheres to [Semantic Versioning](http://semver.org/).
+
+## [2.4.4] - 2015-04-14
+### Changed
+- Separated key utilities into its own Gem
+
+## [2.4.3] - 2015-04-13
+### Changed
+- Loosened production gem requirements from patch level to major level
+
+## [2.4.2] - 2015-03-11
+### Fixed
+- GitHub issue 39: handling post paths that include a ? and require a token. A workaround exists for this issue.
+
+## [2.4.1] - 2015-03-11
+### Fixed
+- GitHub issue 40: error for endpoints that did not return a 'data' field
+
+## [2.4.0] - 2015-03-05
+### Changed
+- Add feature: Accept refunds
+- Fix Bug: Accept bitcoin payments like 0.003

data/GUIDE.md

@@ -0,0 +1,233 @@
+# Using the BitPay Ruby Client Library
+## Prerequisites
+You must have a BitPay merchant account to use this library.  It's free to [sign-up for a BitPay merchant account](https://bitpay.com/start).
+
+Once you have a BitPay merchant account, you will need [a working BitPay Access Token](/api/getting-access.html) – this can be done either [via the library](#pairing) or manually in [the BitPay Dashboard](https://bitpay.com/tokens).
+
+## Quick Start
+### Installation
+```bash
+gem install bitpay-sdk
+```
+
+In your Gemfile:
+
+```ruby
+gem 'bitpay-sdk', :require => 'bitpay_sdk'
+```
+
+Or directly:
+```ruby
+require 'bitpay_sdk'
+```
+
+### Configuration
+The bitpay client creates a cryptographically secure connection to your server by pairing an API code with keys generated by the library. The client can be initialized with pre-existing keys passed in as a pem file, or paired if initialized with a pem file and a tokens hash. Examples can be found in the cucumber step helpers.
+
+## Pairing
+Most calls to the BitPay REST API require that your client is paired with the bitpay.com server.  To pair with bitpay.com you need to have an approved merchant account.
+
+Your client can be paired via the `pos` (point-of-sale) or `merchant` facade (or both).  The `pos` facade allows for invoices to be created.  The `merchant` facade has broader privileges to view all invoices, bills, and ledger entries, as well as to issue refunds.  Consider the level of access required when you pair your client.
+
+### A quick note on keys
+
+The BitPay client gem includes the BitPay KeyUtilities gem, which can be used to generate new public private key pairs which it returns in PEM format. However, there are no methods which save the keys anywhere, so it is your responsibility to store the PEM file somewhere secure.
+
+### BitPay authentication
+
+BitPay authentication depends on four parts:
+
+1. An account on our servers.
+1. A token shared between the client and the server.
+1. A public key, shared between the client and the server.
+1. A private key, held exclusively by the client.
+
+In order to complete authentication, you have to associate your private key with a token, and associate that token with an account. Once this authentication is complete, as long as you have the private key, you never have to authenticate again. The token you created will always be associated with that private key, so any time you create a new bitpay client object with that key, it is authenticated with BitPay. This is true whether you use the ruby-client, python client, or no client at all, the key is the important thing. 
+
+There are two ways to authenticate, from the client side or the server side. The Ruby Client supports both.
+
+To pair from the server side, you log in to the BitPay server, navigate to dashboard/merchant/api-tokens, and create a new token. This creates a new token, which is associated with your account. It is not associated with a key, so we provide a pairing code that you can use as a one time secret to associate the token with a key. From the client side, you can use the client.pair_pos_client(<pairing_code>) method to associate that method with a key held by the client.
+
+To pair from the client side, you use the client to call the /tokens endpoint on the server with no parameters. This creates a token on the server and associates that token with a public key. What it doesn't do is associate that token to an account (because we don't know what account to associate with). This call returns a pairing code, which is a one time secret that allows you to find the token you just created. In order to associate the token with an account, you log in to the BitPay server, and use the dashboard/merchant/api-tokens interface to associate the token with a specific account. And example of client side pairing is shown below.
+
+### Pairing Programatically
+
+If you are developing a client with built-in pairing capability, you can pair programattically using the `pair_client` method.  This method can be called in two ways:
+
+  * `pair_client()` will perform a client-initiated pairing, and will provide a pairing code that can be entered at https://bitpay.com/dashboard/merchant/api-tokens to assign either `merchant` or `pos` facade.
+  * `pair_client('pairing_code')` will complete a server-initiated pairing, when provided a pre-generated pairing code from https://bitpay.com/dashboard/merchant/api-tokens.  In this case, the `pos` facade will be automatically assigned.
+
+This is an example of creating a paired client with the BitPay toolset.
+
+```bash
+$ gem install bitpay-sdk
+Successfully installed bitpay-sdk-2.2.0
+1 gem installed
+$ irb
+2.1.1 :001 > require 'bitpay_sdk'
+ => true 
+2.1.2 :002 > pem = BitPay::KeyUtils.generate_pem
+ => "-----BEGIN EC PRIVATE KEY-----\nMHQCAQEEIH8oSTRm8lVMTVOsDZleIB8AmkiuHnp+ctEknqeUmZahoAcGBSuBBAAK\noUQDQgAEbjhdKA+X8NEKgcbHhyJaBMvePV7Sj6AQuOMQzuZYdskdkPY1/jlfQwNG\n4GVd/zSw4uhfukw/SDBOEKlQGVAmxQ==\n-----END EC PRIVATE KEY-----\n" 
+2.1.1 :002 > client = BitPay::SDK::Client.new(api_uri: 'https://test.bitpay.com', pem: pem)
+ => #<BitPay::SDK::Client:0x000000019c6d40 @pem="---... @tokens={}> 
+2.1.1 :003 > client.pair_client()
+ => {"data"=>[{"policies"=>[{"policy"=>"id", "method"=>"inactive", "params"=>["Tf49SFeiUAtytFEW2EUqZgWj32nP51PK73M"]}], "token"=>"BKQyVdaGQZAArdkkSuvtZN5gcN2355c8vXLj5eFPkfuK", "dateCreated"=>1422474475162, "pairingExpiration"=>1422560875162, "pairingCode"=>"Vy76yTh"}]} 
+```
+
+As described above, using the value from the `pairingCode` element, visit https://test.bitpay.com/api-tokens and search to register for the appropriate facade. That client is now paired. As previously mentioned, you must save the pem string you generated in order to use the client again.
+
+## General Usage
+
+### Initialize the client
+
+```ruby
+client = BitPay::SDK::Client.new(pem: File.read('bitpaykey.pem'))
+```
+    
+Optional parameters:
+ * `api_uri` - specify a different api endpoint (e.g. 'https://test.bitpay.com').  Ensure no trailing slash.
+ * `tokens` - pass a stored hash of bitpay API tokens
+ * `user-agent` - specify a custom user-agent value
+ * `debug: true` - enable HTTP request logging to $stdout
+ * `insecure: true` - disable HTTPs certificate validation (for local test environments)
+
+### Create a new bitcoin invoice
+
+```ruby
+invoice = client.create_invoice(price: <price>, currency: <currency>)
+```
+
+With invoice creation, `price` and `currency` are the only required fields. If you are sending a customer from your website to make a purchase, setting `redirectURL` will redirect the customer to your website when the invoice is paid.
+
+Response will be a hash with information on your newly created invoice. Send your customer to the `url` to complete payment:
+
+```javascript
+{
+  "url": "https://bitpay.com/invoice?id=NKaqMuZWy3BAcP77RdkEEv",
+  "paymentUrls": {
+    "BIP21": "bitcoin:mvYRECDxKPaPHnjNz9ZxiTpbx29xYNoRy4?amount=0.3745",
+    "BIP72": "bitcoin:mvYRECDxKPaPHnjNz9ZxiTpbx29xYNoRy4?amount=0.3745&r=https://bitpay.com/i/NKaqMuZWy3BAcP77RdkEEv",
+    "BIP72b": "bitcoin:?r=https://bitpay.com/i/NKaqMuZWy3BAcP77RdkEEv",
+    "BIP73": "https://bitpay.com/i/NKaqMuZWy3BAcP77RdkEEv"
+  },
+  "status": "new",
+  "btcPrice": "0.3745",
+  "btcDue": "0.3745",
+  "price": 148,
+  "currency": "USD",
+  "exRates": {
+    "USD": 395.20000000000005
+  },
+  "invoiceTime": 1415987168612,
+  "expirationTime": 1415988068612,
+  "currentTime": 1415987168629,
+  "guid": "438e8237-fff1-483c-81b4-dc7dba28922a",
+  "id": "NKaqMuZWy3BAcP77RdkEEv",
+  "transactions": [
+
+  ],
+  "btcPaid": "0.0000",
+  "rate": 395.2,
+  "exceptionStatus": false,
+  "token": "9kZgUXFb5AC6qMuLaMpP9WopbM8X2UjMhkphKKdaprRbSKgUJNE6JNTX8bGsmgxKKv",
+  "buyer": {
+  }
+}
+```
+
+There are many options available when creating invoices, which are listed in the [BitPay API documentation](https://bitpay.com/bitcoin-payment-gateway-api).
+
+### Get invoice status
+The ruby library provides two methods for fetching an existing invoice:
+
+```ruby
+# For authorized clients with a 'merchant' token
+client.get_invoice(id: 'PvVhgBfA7wKPWhuVC24rJo')
+    
+# For non-authenticated clients (public facade)
+# Returns the public subset of invoice fields
+client.get_public_invoice(id: 'PvVhgBfA7wKPWhuVC24rJo')
+```
+
+### Create a refund request
+
+Clients with a `merchant` token can initiate a refund request for a paid invoice:
+
+```ruby
+client.refund_invoice(id: '6pbV13VBZfGFJ8BBmXmLZ8', params: {amount: 10, currency: 'USD'})
+```
+    
+Refund rules:
+
+ * Invoices cannot be refunded prior to 6 blockchain confirmations
+ * Invoices without `["flags"]["refundable"] == true` must specify a `bitcoinAddress` param (one was not provided as part of the transaction)
+ * Invoices that are paid in full must specify an `amount` and `currency` param to indicate the amount to be refunded
+
+### View Refund Requests
+
+The ruby library provides two methods for viewing refund requests.  Both require a `merchant` token.
+
+```ruby
+# To get an array of all refunds against a specific invoice
+client.get_all_refunds_for_invoice(id: 'PvVhgBfA7wKPWhuVC24rJo')
+    
+# To get a specific refund for a specific invoice
+client.get_refund(id: 'JB49z2MsDH7FunczeyDS8j', request_id: '4evCrXq4EDXk4oqDXdWQhX')
+```
+### Cancel Refund Requests
+
+Requires a `merchant` token.
+
+```ruby
+client.cancel_refund(id: 'JB49z2MsDH7FunczeyDS8j', request_id: '4evCrXq4EDXk4oqDXdWQhX')
+```
+
+### Make a HTTP request directly against the REST API
+
+For API tasks which lack a dedicated library method, BitPay provides methods that will automatically apply the proper cryptographic parameters to a request.
+
+```ruby
+client.send_request("GET", "invoices/JB49z2MsDH7FunczeyDS8j", facade: 'merchant')
+## This request is identical to:
+token = client.get_token("merchant")
+client.get(path: "invoices/JB49z2MsDH7FunczeyDS8j", token: token)
+
+## post requests are also possible
+token = client.get_token("merchant")
+client.post(path: "tokens", token: token, params: {facade: "pos"})  #returns a new token with pairing code
+## equivalent to
+client.send_request("POST", "tokens", facade: 'merchant', params: {facade: 'pos'})
+```
+Usage:
+ * Specify HTTP verb and REST endpoint
+ * Specifying a `facade` will fetch and apply the corresponding `token`
+ * Alternatively provide a `token` explicitly
+ * For `POST` requests, the `params` hash will be included as the message body
+
+## Testnet Usage
+
+During development and testing, take advantage of the [Bitcoin TestNet](https://en.bitcoin.it/wiki/Testnet) by passing a custom `api_uri` option on initialization:
+
+```ruby
+BitPay::SDK::Client.new({api_uri: "https://test.bitpay.com/api"})
+```
+
+Note that in order to pair with testnet, you will need a pairing code from test.bitpay.com and will need to use the bitpay client with the --test option.
+
+## API Documentation
+
+API Documentation is available on the [BitPay site](https://bitpay.com/api).
+
+## Running the Tests
+
+In order to run the tests, you must have phantomjs installed and on your PATH.
+
+The tests require that environment variables be set for the bitpay server, user name, password, an invoice id for refunds and a valid testnet bitcoin address for refunds. First run:
+
+```bash 
+$ source ./spec/set_constants.sh https://test.bitpay.com <yourusername> <yourpassword> <a-confirmed-invoice-id> <a-valid-testnet-address>
+$ bundle install
+$ bundle exec rake
+```
+
+Tests are likely to run up against rate limiters on test.bitpay.com if used too frequently. Rake tasks which interact directly with BitPay will not run for the general public.

data/Gemfile

@@ -1,6 +1,2 @@
 source 'https://rubygems.org'
 gemspec
-
-platform :jruby do
-  gem 'jruby-openssl'
-end

data/LICENSE.md

@@ -1,7 +1,7 @@
-Copyright (C) 2015 BitPay
+Copyright (C) 2014 BitPay
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,88 +1,17 @@
-# BitPay Library for Ruby
+# BitPay Library for Ruby 
 
-[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](https://raw.githubusercontent.com/bitpay/ruby-cli/master/LICENSE.md)
-[![Travis](https://img.shields.io/travis/bitpay/ruby-cli.svg?style=flat-square)](https://travis-ci.org/bitpay/ruby-cli)
-[![Gem](https://img.shields.io/gem/v/bitpay-client.svg?style=flat-square)](https://rubygems.org/gems/bitpay-client)
-[![Coveralls](https://img.shields.io/coveralls/bitpay/ruby-cli.svg?style=flat-square)](https://coveralls.io/github/bitpay/ruby-cli)
-[![Code Climate](https://img.shields.io/codeclimate/github/bitpay/ruby-cli.svg?style=flat-square)](https://codeclimate.com/github/bitpay/ruby-cli)
+[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](https://raw.githubusercontent.com/bitpay/ruby-client/master/LICENSE.md)
+[![Travis](https://img.shields.io/travis/bitpay/ruby-client.svg?style=flat-square)](https://travis-ci.org/bitpay/ruby-client)
+[![Gem](https://img.shields.io/gem/v/bitpay-sdk.svg?style=flat-square)](https://rubygems.org/gems/bitpay-sdk)
+[![Code Coverage](https://img.shields.io/coveralls/bitpay/ruby-client.svg?style=flat-square)](https://coveralls.io/r/bitpay/ruby-client?branch=master)
+[![Code Climate](https://img.shields.io/codeclimate/github/bitpay/ruby-client.svg?style=flat-square)](https://codeclimate.com/github/bitpay/ruby-client)
 
 Powerful, flexible, lightweight interface to the BitPay Bitcoin Payment Gateway API.
 
-## Installation
+The `bitpay-sdk` gem provides all the programattic tools required to implement a ruby client application for the BitPay REST API.
 
-    gem install bitpay-client
+## [Getting Started »](https://github.com/bitpay/ruby-client/blob/master/GUIDE.md)
 
-In your Gemfile:
-
-    gem 'bitpay-client', :require => 'bitpay'
-
-Or directly:
-
-    require 'bitpay'
-
-## Configuration
-
-The bitpay client creates a cryptographically secure connection to your server by pairing an API code with keys stored on your server. The library generates the keys as a .pem file, which is stored in `$HOME/.bitpay/bitpay.pem` or preferentially in an environment variable.
-
-The client will generate a key when initialized if one does not already exist.
-
-## Basic Usage
-
-### Pairing with Bitpay.com
-
-To pair with bitpay.com you need to have an approved merchant account.  
-1. Login to your account  
-2. Navigate to bitpay.com/api-tokens (Dashboard > My Account > API Tokens)  
-3. Copy an existing pairing code or create a new token and copy the pairing code.  
-4. Use the bitpay command line tool to pair with bitpay.com `bitpay pair <pairing_code>`
-
-### To create an invoice with a paired client:
-
-The command line utility will save a PEM file in the file $HOME/.bitpay/bitpay.pem. When creating new clients, this pem file is needed in order to have an authorized client.
-
-    client = BitPay::Client.new(pem: File.read("#{ENV['HOME']}/.bitpay/bitpay.pem"))
-    invoice = client.create_invoice (id: <id>, price: <price>, currency: <currency>, facade: <facade>)
-
-With invoice creation, `price` and `currency` are the only required fields. If you are sending a customer from your website to make a purchase, setting `redirectURL` will redirect the customer to your website when the invoice is paid.
-
-Response will be a hash with information on your newly created invoice. Send your customer to the `url` to complete payment:
-
-    {
-      "id"             => "DGrAEmbsXe9bavBPMJ8kuk",
-      "url"            => "https://bitpay.com/invoice?id=DGrAEmbsXe9bavBPMJ8kuk",
-      "status"         => "new",
-      "btcPrice"       => "0.0495",
-      "price"          => 10,
-      "currency"       => "USD",
-      "invoiceTime"    => 1383265343674,
-      "expirationTime" => 1383266243674,
-      "currentTime"    => 1383265957613
-    }
-
-There are many options available when creating invoices, which are listed in the [BitPay API documentation](https://bitpay.com/bitcoin-payment-gateway-api).
-
-To get updated information on this invoice, make a get call with the id returned:
-
-    invoice = client.get_public_invoice(DGrAEmbsXe9bavBPMJ8kuk)'
-
-The BitPay CLI gem requires the BitPay SDK gem. See the [BitPay SDK Gem](https://github.com/bitpay/ruby-client/blob/master/GUIDE.md) documentation for more details on using the BitPay Client SDK.
-
-## Testnet Usage
-
-In order to pair with testnet, you will need a pairing code from test.bitpay.com and will need to use the bitpay client with the --test option.
-
-## API Documentation
-
-API Documentation is available on the [BitPay site](https://bitpay.com/api).
-
-## RDoc/YARD Documentation
-The code has been fully code documented, and the latest version is always available at the [Rubydoc Site](http://rubydoc.info/gems/bitpay-client).
-
-## Running the Tests
-
-    $ bundle install
-    $ bundle exec rake
-jj
 ## Found a bug?
 Let us know! Send a pull request or a patch. Questions? Ask! We're here to help. We will respond to all filed issues.
 

data/Rakefile

@@ -1,14 +1,48 @@
 require "bundler/gem_tasks"
 require 'rspec/core/rake_task'
-
+require 'mongo'
+require 'cucumber'
+require 'cucumber/rake/task'
 require_relative 'config/constants.rb'
 
 RSpec::Core::RakeTask.new(:spec)
 
-task :default => :spec
+#task :default => :spec
+task :default => :default_tasks
+
+Cucumber::Rake::Task.new(:features) do |t|
+    t.cucumber_opts = "features --format pretty"
+end
+
+desc "Run BitPay tests"
+task :default_tasks do
+  Rake::Task["spec"].invoke
+  Rake::Task["features"].invoke
+end
 
 desc "Bitpay Tasks"
 namespace :bitpay do
+
+  desc "Clear all claim codes from the test server."
+  task :clear_claim_codes do
+    puts "clearing claim codes"
+    client = Mongo::MongoClient.new
+    db     = client['bitpay-dev']
+    coll   = db['tokenaccesses']
+    coll.remove()
+    puts "claim codes cleared"
+  end
+
+  desc "Clear rate limiters from local mongo host"
+  task :clear_rate_limiters do
+    puts "clearing rate limiters"
+    client = Mongo::MongoClient.new
+    db     = client['bitpay-dev']
+    coll   = db['ratelimiters']
+    coll.remove()
+    puts "rate limiters cleared"
+  end
+
   desc "Clear local pem and token file"
   task :clear_local_files do
     puts "clearing local files"
@@ -19,4 +53,25 @@ namespace :bitpay do
     File.delete(TOKEN_FILE) if File.file?(TOKEN_FILE)
     puts "local files cleared"
   end
+
+  desc "Clear tokens, rate limiters, and local files."
+  task :clear do
+    ["bitpay:clear_local_files", "bitpay:clear_rate_limiters", "bitpay:clear_claim_codes"].each{|task| Rake::Task[task].reenable}
+    ["bitpay:clear_local_files", "bitpay:clear_rate_limiters", "bitpay:clear_claim_codes"].each{|task| Rake::Task[task].invoke}
+  end
+
+  desc "Run specs and clear claim codes and rate_limiters."
+  task :spec_clear => ['spec', 'clear_claim_codes', 'clear_rate_limiters']
+
+  desc "Run specs, clear data, run cukes, clear data"
+  task :tests_clear do
+    Rake::Task["bitpay:clear"].invoke
+    Rake::Task["spec"].invoke
+    Rake::Task["bitpay:clear"].reenable
+    Rake::Task["bitpay:clear"].invoke
+    Rake::Task["features"].invoke
+    Rake::Task["bitpay:clear"].reenable
+    Rake::Task["bitpay:clear"].invoke
+  end
+
 end