WebpayRails is an easy solution for integrate Transbank Webpay in Rails applications.
This gem (including certificates used in tests) was originally based on the SDK for Ruby (distributed under the open source license) available in www.transbankdevelopers.cl
This README is only valid for the master branch, click here for see the latest released version.
You can add it to your
Run the bundle command to install it.
After that, extend the model to
WebpayRails and add
webpay_rails to this, like below.
class Order < ActiveRecord::Base extend webpay_rails( commerce_code: 123456789, private_key: '-----BEGIN RSA PRIVATE KEY----- ... -----END RSA PRIVATE KEY-----', public_cert: '-----BEGIN CERTIFICATE----- ... -----END CERTIFICATE-----', webpay_cert: '-----BEGIN CERTIFICATE----- ... -----END CERTIFICATE-----', environment: :integration, log: Rails.env.development? ) end
As you can see for
webpay_cert, the content of the files is entered, without prejudice to the above you can also indicate the absolute path to these files.
:integration, and the valid environments are
:production. Depending on the environment is assigned the wsdl path.
log is very useful when generating the evidence of integration, and is enabled by default.
Obviously all these values should not be defined directly in the model. It is strongly recommended to use environment variables for this (dotenv).
Initializing a transaction
First we need to initialize an transaction, like below:
@transaction = Order.init_transaction(amount: amount, buy_order: buy_order, session_id: session_id, return_url: return_url, final_url: final_url)
amount is an integer that define the amount of the transaction (_obviously_),
buy_order is an string that define the order number of the buy,
session_id is an string that define a local variable that will be returned as part of the result of the transaction,
final_url are a string for the redirections.
This method return a
Transaction object, that contain a redirection
token for redirect the customer through POST method, like below.
<% if @transaction.success? %> <%= form_tag(@transaction.url, method: :post) do %> <%= hidden_field_tag(:token_ws, @transaction.token) %> <%= submit_tag("Pagar con Webpay") %> <% end %> <% end %>
Once Webpay displays the form of payment and authorization of the bank, the customer will send back through POST method to the
return_url with a
token_ws. (If the customer cancels the transaction is directly returned to the
final_url in the same way).
Getting the result of a transaction
When Webpay send a POST to
token_ws, we need to ask for the transaction result, like below.
@result = Order.transaction_result(params[:token_ws])
This method return a
TransactionResult object, that contain an
At this point we have confirmed the transaction with Transbank, performing the operation
acknowledge_transaction by means of
Now we need to send back the customer to
token_ws through GET method.
Ending a transaction
When Webpay send customer to
final_url, we are done. Finally the transaction has ended. :clap:
Nullify a transaction
To cancel a transaction we must use the method described below.
@transaction = Order.nullify(authorization_code: , authorize_amount: , buy_order: buy_order, nullify_amount: nullify_amount)
buy_order, are known and corresponds to the transaction to be canceled, and
nullify_amount it corresponds to the amount to be canceled.
This method return a
TransactionNullified object, that contain an
Note that you can only make a single cancellation, whether total or partial.
Any contribution is welcome. Personally I prefer to use English to do documentation and describe commits, however there is no problem if you make your comments and issues in Spanish.
Please try to answer the following questions in your bug report:
- What did you do?
- What did you expect to happen?
- What happened instead?
Make sure to include as much relevant information as possible. Ruby version, WebpayRails version, OS version and any stack traces you have are very valuable.
Add tests! Your patch won't be accepted if it doesn't have tests.
Document any change in behaviour. Make sure the README and any relevant documentation are kept up-to-date.
Create topic branches. Please don't ask us to pull from your master branch.
One pull request per feature. If you want to do more than one thing, send multiple pull requests.
Send coherent history. Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before sending them to us.