Simple SDKs

eWAY is the easiest way to accept payments in your app or on your website. Get integrated and start selling more, faster - in a range of languages using the eWAY SDKs, helpful documentation, and 24/7 support from real humans. eWAY - with you every step of the way.

Ruby SDK


Accept payments quickly and easily with eWAY using the eWAY Rapid Ruby SDK (also known as the eWAY Ruby Gem). Using the Ruby SDK provides convenient access to all the features of eWAY’s Rapid API, so you can create transactions, process refunds, query transactions, create token customer and more!

Getting Started


The easiest way to add the eWAY Ruby SDK to your project is using RubyGems and Bundler – it will add the eWAY Rapid Ruby Gem along with its required dependencies.

To add the eWAY Rapid Ruby Gem, in your project’s Gemfile add the following line:

  1. gem 'eway_rapid'
And then execute the following on the command line:

  1. bundle
Or you can install it globally by running the following on the command line:

  1. gem install eway_rapid
To make development and testing with eWAY easy, get a free partner account which provides access to the eWAY Sandbox.

Now you are all set to build your eWAY integration! You can find code samples for integrating various eWAY functions as part of the eWAY Rapid API reference 

Example Integration

To demonstrate using the eWAY Ruby Gem, this example will show how to accept a payment with the Responsive Shared Page.  This example assumes that Ruby, RubyGems and Bundler are already installed. Only the eWAY specific code is shown so it can be added to your preferred framework.

1. Add the eWAY Ruby Gem

In the project’s Gemfile, add the Ruby Gem: 

  1. gem 'eway_rapid'

Then on the command line execute: 

  1. bundle

to install the Gem and its dependencies. 

2. Load the eWAY Client

With the eWAY Ruby Gem installed, the next step is to add the eWAY integration to your project. To start, generate an instance of the eWAY Client which interacts with eWAY’s Rapid API. It needs an eWAY Rapid API Key & password, along with the endpoint to connect to (either ‘Production’ or ‘Sandbox’):

  1. require 'eway_rapid'

  2. api_key = '60CF3Ce97nRS1Z1Wp5m9kMmzHHEh8Rkuj31QCtVxjPWGYA9FymyqsK0Enm1P6mHJf0THbR'
  3. password = 'API-P4ss'
  4. endpoint = 'Sandbox'

  5. client =, password, endpoint)

3. Create a Shared Payment URL

In order to send a customer to the Responsive Shared Page, a URL must be generated using the create_transaction function. This accepts a PaymentMethod and a transaction object.

The PaymentMethod determines how the card data will be accepted (in this case RESPONSIVE_SHARED) while the Transaction object contains customer and invoice details – more details of the variables that can be passed can be found in the Rapid API reference.

This step would usually take place after collecting the customer’s information in a checkout process. For this example, just some dummy data will be used:
  1. transaction =
  2. payment_details =
  3. payment_details.total_amount = 1000
  4. transaction.payment_details = payment_details
  5. transaction.redirect_url = ''
  6. transaction.cancel_url = ''
  7. transaction.transaction_type = EwayRapid::Enums::TransactionType::PURCHASE

  8. response = client.create_transaction(EwayRapid::Enums::PaymentMethod::RESPONSIVE_SHARED, transaction)

To make sure everything went well, check the errors array is empty. If it isn’t, user_display_message can be used to convert any error codes to human readable messages:

  1. if !response.errors.empty?
  2.   response.errors.each { |e| puts "Error message: "+ EwayRapid::RapidClient.user_display_message(e) }
  3. end

4. ​Redirect the Customer

​Once the shared page URL has been created, the customer can be redirected. How this is done will depend on the project and framework being used. For example, if using Ruby on Rails, the method would be:

  1. redirect_to response.shared_payment_url

So now a Responsive Shared Page URL has been created and the customer is redirected to complete their payment.

5. ​​Fetch the Result

Once the customer has gone to the Responsive Shared Page and submitted their payment information, they will be redirected back to the RedirectUrl specified in the request. This page should use the AccessCode (passed as a query variable) to fetch the result of the transaction.  

  1. response =
  2. client.query_transaction_by_access_code(params[:AccessCode])

Key information such as the success of the transaction and the transaction ID can be found in the transactionStatus of the response. If the transaction wasn’t successful, the reason can be found in the ResponseMessage. An example of handling this information would be:

  1. if response.transaction_status.status?
  2.   puts "Payment successful! ID: #{response.transaction_status.transaction_id.to_s}"
  3. else
  4.   puts "Failed! Message #{response.transaction_status.processing_details.response_message}"
  5. end

That’s it – a complete Responsive Shared Page integration! 

For more information on the functions available in the eWAY ​Ruby Gem, check out the eWAY Rapid API Reference

Image: The Ruby logo is Copyright © 2006, Yukihiro Matsumoto.


eWAY makes it easy for us to process and manage payments. They have an SDK that my developers liked working with and their payment management tools are very easy to use.

Dean Van Es, Managing Director FastCover