Heartland Ruby SDK
This SDK makes it easy to integrate your Ruby application with Heartland's Portico Gateway API. Supported features include:
- Card Not Present (eCommerce and mobile)
- Card Present (Retail and Restaurant)
- Secure Submit single-use tokenization and multi-use tokenization
- Heartland Secure End-to-End Encryption (E3)
- Credit, Gift & Loyalty,and eCheck/ACH
- Recurring Payments
Supported Gateway Calls
|Data Security||API Reference||Testing & Certification||API Keys||Links|
|Register an Account
Partner with Heartland
You are not alone! If you have any questions while you are working through your development process, please feel free to reach out to our team for assistance.
The SDK can be added into your application via a Ruby Gem command:
gem install 'hps'
You can also use Bundler Gemfiles to have it automatically installed. Add the following to your gemfile:
And then run Bundler :
API Keyshttp://developer.heartlandpaymentsystems.com/). Your keys are located under your profile information.
You will use your public key when implementing card tokenization and your private key will be used when communicating with our Portico Gateway. More details can be found in our documentation.
Note: Multi-Use tokenization is not enabled by default when creating an account. You can contact Heartland's Specialty Products Team to have this enabled. This is also true if you wish to use Gift & Loyalty, ACH, and Debit.
- Self-Hosted Fields - this approach relies upon the standard, appropriately named, HTML form controls on the integrator's served web page.
- Heartland Hosted Fields - this approach combines the Secure Submit service with iframes to handle presentation of the form fields and collection of sensitive data on Heartland servers. Since PCI version 3.1 the PCI Council and many QSAs advocate the iframe-based approach as enabling a merchant to more readily achieve PCI compliance via the simplified SAQ-A form. Check out the CoalFire's whitepaper for more information.
- Heartland Secure for card-present retailers, hospitality, and other "POS" applications, comprises three distinct security technologies working in concert:
- End-to-End Encryption (E3) - combines symmetric and asymmetric cryptography to form an "Identity-Based Encryption" methodology which keeps cardholder data encrypted from the moment of the swipe.
- Tokenization - replaces sensitive data values with non-sensitive representations which may be stored for recurring billing, future orders, etc.
- EMV - though less about data security and more about fraud prevention, EMV or chip card technology guarantees the authenticity of the payment card and is thus an important concern for retailers.
Depending on your (or your customers') payment acceptance environment, you may need to support one or more of these technologies in addition to this SDK. This SDK also supports the ability to submit cleartext card numbers as input, but any developer who does so will be expected to demonstrate compliance with PA-DSS. Likewise any third party integrator who is planning on handling cleartext card data on behalf of other merchants will be expected to demonstrate their PCI DSS compliance as a Service Provider prior to completing certification with Heartland.
If you implement Secure Submit tokenization for your web or mobile application you will never have to deal with handling a card number - Heartland will take care of it for you and return a token to initiate the charge from your servers.
Similarly, if you implement Heartland Secure with E3 (for both swiped and keyed entry methods) then your POS application will be out-of-scope for PA-DSS. Heartland Secure certified devices will only ever return E3 encrypted data which can safely be passed through your systems as input to this SDK. Heartland Secure devices include many popular models manufactured by PAX and Ingenico.
To summarize, when you create a payment method using this SDK you have the following options for securely avoiding interaction with sensitive cardholder data:
- Card data (track or PAN) may be sent directly from a web browser to Heartland, returning a SecureSubmit single use token that is then sent to your server.
- Encrypted card data (track or PAN) may be obtained directly from a Heartland Secure device and passed to the SDK
Documentation and Exampleshttp://developer.heartlandpaymentsystems.com/documentation). In addition the included [test suite](http://github.hps.com/DevPortal/Ruby-SDK/tree/master/tests) can be a great source of code samples for using the SDK!
Testing & Certificationcontact Heartland in order to initiate a certification project.
Quick Tip: You can get a head start on your certification by reviewing the certification tests in the included test suite.
Test Card Data
The following card numbers are used by our Certification environment to verify that your tests worked. Note that while variations (such as 4111111111111111) will work for general testing the cards listed below are required to complete certification.
|Name||Number||Exp Month||Exp Year||CVV||Address||Zip|
|Visa||4012002000060016||12||2025||123||6860 Dallas Pkwy||750241234|
|MasterCard||5473500000000014||12||2025||123||6860 Dallas Pkwy||75024|
During your integration you will want to test for specific issuer responses such as 'Card Declined'. Because our sandbox does not actually reach out to issuers we have devised specific transaction amounts that will trigger issuer response codes and gateway response codes. Please contact Heartland for a complete listing of values you can charge to simulate AVS, CVV and Transaction declines, errors, and other responses that you can catch in your code:
begin credit_service.charge(-5, 'usd', credit_card, card_holder) rescue HpsInvalidRequestException => e # handle error for amount less than zero dollars rescue HpsAuthenticationException => e # handle errors related to your HpsServiceConfig rescue HpsCreditException => e # handle card-related exceptions: card declined, processing error, etc end
More exceptions can be found here.
All our code is open sourced and we encourage fellow developers to contribute and help improve it!
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Ensure SDK tests are passing
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request
Included Test Suite
The included test suite can help ensure your contribution doesn't cause unexpected errors and is a terrific resource of working examples that you can reference. As mentioned earlier, the certification folder contains tests that mirror the types of requirements you will encounter when you certify your integration for production.