pesapal 1.8.0 → 2.0.0

data/docs/index.md

@@ -0,0 +1,302 @@
+---
+title: Get
+layout: default
+---
+
+Synopsis
+--------
+
+Basically it's a gem that makes it easy to integrate your app with
+[Pesapal's][24] payment gateway. It Handles all the [oAuth stuff][1] abstracting
+any direct interaction with the API endpoints so that you can focus on what
+matters. _Building awesome_.
+
+All this with no 3rd party oAuth library dependencies, it handles all the oAuth
+flows on its own so your app is one dependency less.
+
+The gem should be [up on RubyGems.org][7], it's [accompanying API reference
+here][13], the [CHANGELOG here][21] and [all the releases here][12].
+
+Ps: This documentation is based off `v2.0.0`. For older versions, rely on the
+version specific documentation. You can find the link on [RubyGems.org][7].
+
+Installation
+------------
+
+Add this line to your application's Gemfile:
+
+    gem 'pesapal'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install pesapal
+
+Usage
+-----
+
+### Initialization
+
+Initialize Pesapal object and choose the environment, there are two environments;
+`:development` and `:production`. They determine if the code will interact
+with the testing or the live Pesapal API.
+
+```ruby
+# Sets environment to :development
+pesapal = Pesapal::Merchant.new(:development)
+
+# Sets environment to :production
+pesapal = Pesapal::Merchant.new(:production)
+```
+
+### Configuration
+
+Use a hash as shown below (please note that Pesapal provides different keys for
+different environments, make sure you choose the right one).
+
+```ruby
+pesapal.config = {
+  callback_url: 'http://0.0.0.0:3000/pesapal/callback',
+  consumer_key: '<YOUR_CONSUMER_KEY>',
+  consumer_secret: '<YOUR_CONSUMER_SECRET>'
+}
+```
+
+### Posting An Order
+
+Once you've finalized the configuration, set up the order details in a hash as
+shown in the example below ... all keys **MUST** be present. If there's one that
+you wish to ignore just leave it with a blank string but make sure it's included
+e.g. the phonenumber.
+
+```ruby
+pesapal.order_details = {
+  amount: 1000,
+  description: 'this is the transaction description',
+  type: 'MERCHANT',
+  reference: '808-707-606',
+  first_name: 'Swaleh',
+  last_name: 'Mdoe',
+  email: 'user@example.com',
+  phonenumber: '+254722222222',
+  currency: 'KES'
+}
+```
+
+Then generate the transaction url as below. In the example, the value is
+assigned to the variable `order_url` which you can pass on to the templating
+system of your choice to generate an iframe. Please note that this method
+utilizes all that information set in the previous steps in generating the url so
+it's important that it's the last step in the post order process.
+
+```ruby
+# generate transaction url
+order_url = pesapal.generate_order_url
+
+# order_url will a string with the url example;
+# http://demo.pesapal.com/API/PostPesapalDirectOrderV4?oauth_callback=http%3A%2F%2F1.2.3.4%3A3000%2Fpesapal%2Fcallback&oauth_consumer_key=A9MXocJiHK1P4w0M%2F%2FYzxgIVMX557Jt4&oauth_nonce=13804335543pDXs4q3djsy&oauth_signature=BMmLR0AVInfoBI9D4C38YDA9eSM%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1380433554&oauth_version=1.0&pesapal_request_data=%26lt%3B%3Fxml%20version%3D%26quot%3B1.0%26quot%3B%20encoding%3D%26quot%3Butf-8%26quot%3B%3F%26gt%3B%26lt%3BPesapalDirectOrderInfo%20xmlns%3Axsi%3D%26quot%3Bhttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instance%26quot%3B%20xmlns%3Axsd%3D%26quot%3Bhttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%26quot%3B%20Amount%3D%26quot%3B1000%26quot%3B%20Description%3D%26quot%3Bthis%20is%20the%20transaction%20description%26quot%3B%20Type%3D%26quot%3BMERCHANT%26quot%3B%20Reference%3D%26quot%3B808%26quot%3B%20FirstName%3D%26quot%3BSwaleh%26quot%3B%20LastName%3D%26quot%3BMdoe%26quot%3B%20Email%3D%26quot%3Bj%40kingori.co%26quot%3B%20PhoneNumber%3D%26quot%3B%2B254722222222%26quot%3B%20xmlns%3D%26quot%3Bhttp%3A%2F%2Fwww.pesapal.com%26quot%3B%20%2F%26gt%3B
+```
+
+_Ps: Please note the `:callback_url` value in the `pesapal.config` hash ...
+after the user successfully posts the order, the response will be sent to this
+url. Refer to [official Pesapal Step-By-Step integration guide][18] for more
+details._
+
+### Querying Payment Status
+
+Use this to query the status of the transaction. When a transaction is posted to
+Pesapal, it may be in a PENDING, COMPLETED, FAILED or INVALID state. If the
+transaction is PENDING, the payment may complete or fail at a later stage.
+
+Both the unique merchant reference generated by your system (compulsory) and the
+pesapal transaction tracking id (optional) are input parameters to this method
+but if you don't ensure that the merchant reference is unique for each order on
+your system, you may get INVALID as the response. Because of this, it is
+recommended that you provide both the merchant reference and transaction
+tracking id as parameters to guarantee uniqueness.
+
+```ruby
+# option 1: using merchant reference only
+payment_status = pesapal.query_payment_status("<MERCHANT_REFERENCE>")
+
+# option 2: using merchant reference and transaction id (recommended)
+payment_status = pesapal.query_payment_status("<MERCHANT_REFERENCE>","<TRANSACTION_ID>")
+```
+
+### Querying Payment Details
+
+Same as querying payment status above, but the return value contains more
+information (and is a hash as opposed to a string).
+
+```ruby
+# pass in merchant reference and transaction id
+payment_details = pesapal.query_payment_details("<MERCHANT_REFERENCE>","<TRANSACTION_ID>")
+```
+
+The result is a hash that looks something like this ...
+
+```ruby
+{
+  method: "<PAYMENT_METHOD>",
+  status: "<PAYMENT_STATUS>",
+  merchant_reference: "<MERCHANT_REFERENCE>",
+  transaction_tracking_id: "<TRANSACTION_ID>"
+}
+```
+
+### IPN Listening
+
+Use the `ipn_listener` method to listen to Pesapal IPN calls to easily create an
+appropriate response, example below.
+
+```ruby
+# pass in the notification type, merchant reference and transaction id
+response_to_ipn = pesapal.ipn_listener("<NOTIFICATION_TYPE>", "<MERCHANT_REFERENCE>","<TRANSACTION_ID>")
+```
+
+The variable, `response_to_ipn`, now holds a response as the one shown below.
+Using the status you can customise any actions (e.g. database inserts and
+updates) and finally, it's up to you to send the `:response` back to pesapal. The
+hard part is done for you.
+
+```ruby
+{
+  status: "<PAYMENT_STATUS>",
+  response: "<IPN_RESPONSE>"
+}
+```
+
+_Ps: Refer to Pesapal official documentation to make sure you understand what
+data Pesapal sends to IPN and what result they expect back._
+
+
+Support & Issues
+----------------
+
+In case you are having any issues using this gem please **_do not_** email me
+directly, I'd rather you [submit new issues (and even requests) here][23] ...
+obviously after [checking if the issue has already been raised and closed][6].
+This way, other people get to share in the conversation that would have been
+private and out of their reach.
+
+
+Contributing
+------------
+
+### To gem's code
+
+Submitting a pull request;
+
+1. [Fork the repository][fork].
+2. [Create a topic branch][branch] (`git checkout -b BRANCH_NAME`).
+3. [Install bundler][bundler].
+4. Check that tests pass with `rspec spec`.
+5. Write a failing test to capture existing bug or lack of feature.
+6. Run `rspec spec` to verify that test fails.
+7. Implement your feature or bug fix.
+8. Ensure tests pass.
+9. If it's a new feature or a bug fix, please add an entry to the CHANGELOG file.
+10. Check code style violations using [Rubocop][rubocop].
+11. Add a commit (`git commit -am 'AWESOME COMMIT MESSAGE'`).
+12. Push your changes to the branch (`git push origin BRANCH_NAME`).
+13. [Submit a pull request.][pr]
+14. You will get some feedback and may need to push additional commits
+    with more fixes to the same branch; this will update your pull request
+    automatically.
+
+[branch]: http://git-scm.com/book/en/Git-Branching-Branching-Workflows#Topic-Branches
+[bundler]: http://bundler.io
+[fork]: https://help.github.com/articles/fork-a-repo/
+[pr]: https://help.github.com/articles/using-pull-requests
+[rubocop]: https://github.com/bbatsov/rubocop
+
+
+### To gem's documentation
+
+Gem documentation is of two types, feel free to contribute to any;
+
+1. Gem home page at [itskingori.github.io/pesapal-gem][26] _(simple step-by-step)_
+2. API documetation generated by [Yard][25] _(very comprehensive)_
+
+Gem home page is built on [Jekyll][27], which is a fun and easy to use static
+site generator and [hosted on GitHub Pages][30]. The code is in the `docs/`
+folder if you want to have a peek.
+
+Preview the gem API documentation locally by installing [Yard][25] (`gem install
+yard`) and call `$ yard server` to set up a local documentation server usually
+running on `http://0.0.0.0:8808`. The result should be similar to the API
+documention up on [rubydoc.info/gems/pesapal][13].
+
+_Ps: If you've written code and can't figure out why they aren't passing (or if
+you've written your own tests ... just send a pull a request. We can then do a
+[code review][32])_.
+
+
+Testing
+-------
+
+Tests run [RSpec][31] which is a Behaviour-Driven Development tool. To run
+tests, call;
+
+```bash
+$ bundle exec rspec spec
+```
+
+
+References
+----------
+
+* [oAuth 1.0 Spec][1]
+* [Developing a RubyGem using Bundler][2]
+* [RailsGuides][20]
+* [Make your own gem][3]
+* [Getting started with RSpec][33]
+* [Pesapal API Reference (Official)][4]
+* [Pesapal Step-By-Step Reference (Official)][18]
+* [Pesapal PHP API Reference (Unofficial)][5]
+
+
+License
+-------
+
+[King'ori J. Maina][10] © 2013-{{ 'now' | date: "%Y" }}. The [MIT License bundled therein][11] is a
+permissive license that is short and to the point. It lets people do anything
+they want as long as they provide attribution and waive liability.
+
+
+[1]: http://oauth.net/core/1.0/
+[2]: https://github.com/radar/guides/blob/master/gem-development.md
+[3]: http://guides.rubygems.org/make-your-own-gem/
+[4]: http://developer.pesapal.com/how-to-integrate/api-reference
+[5]: https://github.com/itskingori/pesapal-php#pesapal-php-api-reference-unofficial
+[6]: https://github.com/itskingori/pesapal-gem/issues?state=closed
+[7]: https://rubygems.org/gems/pesapal
+[8]: https://github.com/itskingori/pesapal-gem/fork
+[9]: https://github.com/itskingori/pesapal-gem#contributing--testing
+[10]: http://kingori.co/
+[11]: https://raw.githubusercontent.com/itskingori/pesapal-gem/master/LICENSE.txt
+[12]: https://github.com/itskingori/pesapal-gem/releases/
+[13]: http://rubydoc.info/gems/pesapal/frames/file/README.md
+[14]: https://github.com/itskingori/mo
+[15]: https://github.com/itskingori/mo/tree/master/convention#-convention
+[16]: http://kingori.co/articles/2013/09/modus-operandi/
+[17]: https://github.com/itskingori/pesapal-gem/pulls
+[18]: http://developer.pesapal.com/how-to-integrate/step-by-step
+[19]: https://github.com/itskingori/pesapal-gem/graphs/contributors
+[20]: http://guides.rubyonrails.org/
+[21]: https://raw.githubusercontent.com/itskingori/pesapal-gem/master/CHANGELOG.md
+[22]: https://travis-ci.org/itskingori/pesapal-gem/pull_requests
+[23]: https://github.com/itskingori/pesapal-gem/issues/new
+[24]: https://www.pesapal.com/
+[25]: http://yardoc.org/
+[26]: https://itskingori.github.io/pesapal-gem
+[27]: http://jekyllrb.com/
+[28]: http://jekyllrb.com/docs/home/
+[29]: https://github.com/itskingori/pesapal-gem/tree/gh-pages
+[30]: https://pages.github.com/
+[31]: https://relishapp.com/rspec/
+[32]: http://en.wikipedia.org/wiki/Code_review
+[33]: https://relishapp.com/rspec/docs/gettingstarted

data/lib/pesapal.rb

@@ -7,5 +7,3 @@ require 'pesapal/helper/status'
 require 'pesapal/merchant'
 require 'pesapal/oauth'
 require 'pesapal/version'
-
-require 'pesapal/railtie' if defined?(Rails)

data/lib/pesapal/helper/details.rb

@@ -43,10 +43,12 @@ module Pesapal
       #   query parameters and the `oauth_signature` itself.
       def self.set_parameters(consumer_key, merchant_reference, transaction_tracking_id)
         timestamp = Time.now.to_i.to_s
-        { oauth_consumer_key: consumer_key,
-          oauth_nonce: "#{timestamp}" + Pesapal::Oauth.generate_nonce(12),
+
+        {
+          oauth_consumer_key: consumer_key,
+          oauth_nonce: timestamp + Pesapal::Oauth.generate_nonce(12),
           oauth_signature_method: 'HMAC-SHA1',
-          oauth_timestamp: "#{timestamp}",
+          oauth_timestamp: timestamp,
           oauth_version: '1.0',
           pesapal_merchant_reference: merchant_reference,
           pesapal_transaction_tracking_id: transaction_tracking_id

data/lib/pesapal/helper/post.rb

@@ -163,11 +163,13 @@ module Pesapal
       # @return [Hash] parameters to be used in generating the oAuth 1.0 URL query parameters and the `oauth_signature` itself.
       def self.set_parameters(callback_url, consumer_key, post_xml)
         timestamp = Time.now.to_i.to_s
-        { oauth_callback: callback_url,
+
+        {
+          oauth_callback: callback_url,
           oauth_consumer_key: consumer_key,
-          oauth_nonce: "#{timestamp}" + Pesapal::Oauth.generate_nonce(12),
+          oauth_nonce: timestamp + Pesapal::Oauth.generate_nonce(12),
           oauth_signature_method: 'HMAC-SHA1',
-          oauth_timestamp: "#{timestamp}",
+          oauth_timestamp: timestamp,
           oauth_version: '1.0',
           pesapal_request_data: post_xml
         }

data/lib/pesapal/helper/status.rb

@@ -39,13 +39,14 @@ module Pesapal
       # @return [Hash] parameters to be used in generating the oAuth 1.0 URL query parameters and the `oauth_signature` itself.
       def self.set_parameters(consumer_key, merchant_reference, transaction_tracking_id = nil)
         timestamp = Time.now.to_i.to_s
-        params = { oauth_consumer_key: consumer_key,
-                   oauth_nonce: "#{timestamp}" + Pesapal::Oauth.generate_nonce(12),
-                   oauth_signature_method: 'HMAC-SHA1',
-                   oauth_timestamp: "#{timestamp}",
-                   oauth_version: '1.0',
-                   pesapal_merchant_reference: merchant_reference
-                }
+        params = {
+          oauth_consumer_key: consumer_key,
+          oauth_nonce: timestamp + Pesapal::Oauth.generate_nonce(12),
+          oauth_signature_method: 'HMAC-SHA1',
+          oauth_timestamp: timestamp,
+          oauth_version: '1.0',
+          pesapal_merchant_reference: merchant_reference
+        }
         params[:pesapal_transaction_tracking_id] = transaction_tracking_id unless transaction_tracking_id.nil?
         params
       end

data/lib/pesapal/merchant.rb

@@ -64,7 +64,7 @@ module Pesapal
 
     private
 
-    attr_reader :api_domain, :api_endpoints, :env
+    attr_reader :env
 
     def params
       @params ||= nil
@@ -87,71 +87,22 @@ module Pesapal
     # will interact with the testing or the live Pesapal API. Like so ...
     #
     # ```ruby
-    # # Sets environment intelligently to 'Rails.env' (if Rails) or :development (if non-Rails)
-    # pesapal = Pesapal::Merchant.new
-    #
-    # # Sets environment to :development
+    # # Sets environment to :development explicitly
     # pesapal = Pesapal::Merchant.new(:development)
     #
     # # Sets environment to :production
     # pesapal = Pesapal::Merchant.new(:production)
     # ```
     #
-    # A few things to note about the constructor as it behaves differently
-    # depending on the context within which it is called i.e. _Rails_ app vs
-    # _non-Rails_ app ...
-    #
-    # ### Case 1: Rails app
-    #
-    # The constructor attempts to set configuration details that should be
-    # available at runtime from `Rails.application.config.pesapal_credentials`.
-    # This contains values loaded at application start from a YAML file located
-    # at `config/pesapal.yml` which typically looks like this:
-    #
-    #  ```yaml
-    # development:
-    #   callback_url: 'http://0.0.0.0:3000/pesapal/callback'
-    #   consumer_key: '<YOUR_DEV_CONSUMER_KEY>'
-    #   consumer_secret: '<YOUR_DEV_CONSUMER_SECRET>'
-    #
-    # production:
-    #   callback_url: 'http://1.2.3.4:3000/pesapal/callback'
-    #   consumer_key: '<YOUR_PROD_CONSUMER_KEY>'
-    #   consumer_secret: '<YOUR_PROD_CONSUMER_SECRET>'
-    # ```
-    #
-    # The appropriate credentials are picked and set to {#config} instance
-    # attribute depending on set environment. The setting of environment is
-    # explained above. It's worth nothing that if for some reason the YAML file
-    # could not be read, then it fallbacks to setting {#config} instance
-    # attribute with default values. The exact definition of default values is
-    # shown below.
-    #
-    # ### Case 2: Non-Rails app
-    #
-    # Since (and if) no predefined configuration files are available, the
-    # constructor sets the {#config} instance attribute up with default values
-    # as shown below:
-    #
-    # ```
-    # {  :callback_url => 'http://0.0.0.0:3000/pesapal/callback',
-    #    :consumer_key => '<YOUR_CONSUMER_KEY>',
-    #    :consumer_secret => '<YOUR_CONSUMER_SECRET>'
-    # }
-    # ```
-    #
-    # @note You can change the environment at runtime using {#change_env}
-    #
     # @param env [Symbol] the environment we want to use i.e. `:development` or
-    #   `:production`. Leaving it blank sets environment intelligently to
-    #   `Rails.env` (if Rails) or `:development` (if non-Rails).
-    def initialize(env = false)
-      change_env env
-      if defined?(Rails)
-        configure Rails.application.config.pesapal_credentials
-      else
-        configure
-      end
+    #   `:production`.
+    def initialize(env = :development)
+      @env = env.to_s.downcase
+      @config = {
+        callback_url: 'http://0.0.0.0:3000/pesapal/callback',
+        consumer_key: '<YOUR_CONSUMER_KEY>',
+        consumer_secret: '<YOUR_CONSUMER_SECRET>'
+      }
     end
 
     # Generate URL that's used to post a transaction to PesaPal.
@@ -185,17 +136,20 @@ module Pesapal
       # build xml with input data, the format is standard so no editing is
       # required
       @post_xml = Pesapal::Helper::Post.generate_post_xml @order_details
-
       # initialize setting of @params (oauth_signature left empty)
       @params = Pesapal::Helper::Post.set_parameters(@config[:callback_url], @config[:consumer_key], @post_xml)
-
       # generate oauth signature and add signature to the request parameters
-      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature('GET', @api_endpoints[:postpesapaldirectorderv4], @params, @config[:consumer_secret], @token_secret)
-
+      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature(
+        'GET',
+        postpesapaldirectorderv4_url,
+        @params,
+        @config[:consumer_secret],
+        @token_secret
+      )
       # change params (with signature) to a query string
       query_string = Pesapal::Oauth.generate_encoded_params_query_string @params
 
-      "#{@api_endpoints[:postpesapaldirectorderv4]}?#{query_string}"
+      "#{postpesapaldirectorderv4_url}?#{query_string}"
     end
 
     # Same as {#query_payment_status}, but additional information is returned in
@@ -237,15 +191,19 @@ module Pesapal
     def query_payment_details(merchant_reference, transaction_tracking_id)
       # initialize setting of @params (oauth_signature left empty)
       @params = Pesapal::Helper::Details.set_parameters(@config[:consumer_key], merchant_reference, transaction_tracking_id)
-
       # generate oauth signature and add signature to the request parameters
-      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature('GET', @api_endpoints[:querypaymentdetails], @params, @config[:consumer_secret], @token_secret)
-
+      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature(
+        'GET',
+        querypaymentdetails_url,
+        @params,
+        @config[:consumer_secret],
+        @token_secret
+      )
       # change params (with signature) to a query string
       query_string = Pesapal::Oauth.generate_encoded_params_query_string @params
 
       # get status response
-      uri = URI.parse "#{@api_endpoints[:querypaymentdetails]}?#{query_string}"
+      uri = URI.parse "#{querypaymentdetails_url}?#{query_string}"
       http = Net::HTTP.new(uri.host, uri.port)
       http.use_ssl = true
       http.verify_mode = OpenSSL::SSL::VERIFY_PEER
@@ -253,7 +211,8 @@ module Pesapal
       response = CGI.parse response.body
       response = response['pesapal_response_data'][0].split(',')
 
-      { method: response[1],
+      {
+        method: response[1],
         status: response[2],
         merchant_reference: response[3],
         transaction_tracking_id: response[0]
@@ -290,15 +249,19 @@ module Pesapal
     def query_payment_status(merchant_reference, transaction_tracking_id = nil)
       # initialize setting of @params (oauth_signature left empty)
       @params = Pesapal::Helper::Status.set_parameters(@config[:consumer_key], merchant_reference, transaction_tracking_id)
-
       # generate oauth signature and add signature to the request parameters
-      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature('GET', @api_endpoints[:querypaymentstatus], @params, @config[:consumer_secret], @token_secret)
-
+      @params[:oauth_signature] = Pesapal::Oauth.generate_oauth_signature(
+        'GET',
+        querypaymentstatus_url,
+        @params,
+        @config[:consumer_secret],
+        @token_secret
+      )
       # change params (with signature) to a query string
       query_string = Pesapal::Oauth.generate_encoded_params_query_string @params
 
       # get status response
-      uri = URI.parse "#{@api_endpoints[:querypaymentstatus]}?#{query_string}"
+      uri = URI.parse "#{querypaymentstatus_url}?#{query_string}"
       http = Net::HTTP.new(uri.host, uri.port)
       http.use_ssl = true
       http.verify_mode = OpenSSL::SSL::VERIFY_PEER
@@ -307,50 +270,6 @@ module Pesapal
       response['pesapal_response_data'][0]
     end
 
-    # Set the environment in use.
-    #
-    # Useful especially if you want to change the environment at runtime from
-    # what was set during initialization in the constructor. It also makes sure
-    # that we use the appropriate endpoints when making calls to Pesapal. See
-    # below:
-    #
-    # ```
-    # # endpoint values set if :development
-    # {
-    #  :postpesapaldirectorderv4 => "http://demo.pesapal.com/API/PostPesapalDirectOrderV4",
-    #  :querypaymentstatus => "http://demo.pesapal.com/API/QueryPaymentStatus",
-    #  :querypaymentdetails => "http://demo.pesapal.com/API/QueryPaymentDetails"
-    # }
-    #
-    # # endpoint values set if :production
-    # {
-    #  :postpesapaldirectorderv4 => "https://www.pesapal.com/API/PostPesapalDirectOrderV4",
-    #  :querypaymentstatus => "https://www.pesapal.com/API/QueryPaymentStatus",
-    #  :querypaymentdetails => "https://www.pesapal.com/API/QueryPaymentDetails"
-    # }
-    # ```
-    #
-    # @note For a Rails app, you'd expect that calling this would also flip the
-    #   credentials if there was a YAML file containing both environment
-    #   credentials but that's not the case. It could be something that we can
-    #   add later.
-    #
-    # @param env [Symbol] the environment we want to use i.e. :development or
-    #   :production
-    #
-    # @return [Hash] contains Pesapal endpoints appropriate for the set
-    #   environment
-    def change_env(env = false)
-      env = env.to_s.downcase
-      if env == 'production'
-        @env = 'production'
-      else
-        @env = 'development'
-        @env = Rails.env if defined?(Rails)
-      end
-      assign_endpoints
-    end
-
     # Generates the appropriate IPN response depending on the status of the
     # transaction.
     #
@@ -393,9 +312,13 @@ module Pesapal
       status = query_payment_status(merchant_reference, transaction_tracking_id)
       output = { status: status, response: nil }
 
+      response = "pesapal_notification_type=#{notification_type}"
+      response += "&pesapal_transaction_tracking_id=#{transaction_tracking_id}"
+      response += "&pesapal_merchant_reference=#{merchant_reference}"
+
       case status
-      when 'COMPLETED' then output[:response] = "pesapal_notification_type=#{notification_type}&pesapal_transaction_tracking_id=#{transaction_tracking_id}&pesapal_merchant_reference=#{merchant_reference}"
-      when 'FAILED'    then output[:response] = "pesapal_notification_type=#{notification_type}&pesapal_transaction_tracking_id=#{transaction_tracking_id}&pesapal_merchant_reference=#{merchant_reference}"
+      when 'COMPLETED' then output[:response] = response
+      when 'FAILED'    then output[:response] = response
       end
 
       output
@@ -403,33 +326,24 @@ module Pesapal
 
     private
 
-    # Assign API endpoints depending on the environment.
-    def assign_endpoints
-      if @env == 'production'
-        @api_domain = 'https://www.pesapal.com'
-      else
-        @api_domain = 'https://demo.pesapal.com'
-      end
-
-      @api_endpoints = {}
-      @api_endpoints[:postpesapaldirectorderv4] = "#{@api_domain}/API/PostPesapalDirectOrderV4"
-      @api_endpoints[:querypaymentstatus] = "#{@api_domain}/API/QueryPaymentStatus"
-      @api_endpoints[:querypaymentdetails] = "#{@api_domain}/API/QueryPaymentDetails"
+    def api_domain
+      @env == 'production' ? 'www.pesapal.com' : 'demo.pesapal.com'
+    end
 
-      @api_endpoints
+    def api_endpoint
+      'https://' + api_domain
     end
 
-    # Configure credentials through hash that passed in (does a little
-    # processing to remove unwanted data & uses default if nothing is input).
-    def configure(consumer_details = {})
-      @config = { callback_url: 'http://0.0.0.0:3000/pesapal/callback',
-                  consumer_key: '<YOUR_CONSUMER_KEY>',
-                  consumer_secret: '<YOUR_CONSUMER_SECRET>'
-                }
+    def postpesapaldirectorderv4_url
+      api_endpoint + '/API/PostPesapalDirectOrderV4'
+    end
 
-      valid_config_keys = @config.keys
+    def querypaymentstatus_url
+      api_endpoint + '/API/QueryPaymentStatus'
+    end
 
-      consumer_details.each { |k, v| @config[k.to_sym] = v if valid_config_keys.include? k.to_sym }
+    def querypaymentdetails_url
+      api_endpoint + '/API/QueryPaymentDetails'
     end
   end
 end