Heartland & Global Payments Java SDK

This SDK makes it easy to integrate your Java application with our Card Not Present and Card Present APIs.

Solutions

General / Omnichannel

• API Payment Processing
• Apple Pay & Google Pay
• Secure Card Storage & Customer Management
• Subscriptions / Recurring Billing Solutions
• Credit, Debit, Gift & Loyalty, and eCheck/ACH

Card Not Present (Ecommerce & MOTO) Specific

• Minimize PCI compliance requirements with Hosted Payment Solutions
• 140+ Authorization Currencies & 16 Settlement Currencies
• 150+ Local Payment Methods Worldwide
• Account Updater
• Inbuilt Fraud Prevention Rules
• 3D Secure, AVS and CVV Checks
• 260+ Global Enterprise Fraud Rules

Card Present (Terminal & POS) Specific

• Minimize PCI Compliance requirements with Semi-Integrated / Out of Scope devices
• Secure End-To-End Encryption

Requirements

• Java 7+

Installation

Installing the SDK into your solution is usually be done by using Maven.

To install via Maven:

<dependency>
  <groupId>com.heartlandpaymentsystems</groupId>
  <artifactId>globalpayments-sdk</artifactId>
  <version>1.4-SNAPSHOT</version>
</dependency>

Documentation and Examples

You can find the latest SDK documentation along with code examples and test cards on the Global Payments and Heartland Developer Hubs.

In addition you can find working examples in the our example code repository.

Quick Tip: The included test suite can be a great source of code samples for using the SDK!

Process a Payment Example

CreditCardData card = new CreditCardData();
card.setNumber("4111111111111111");
card.setExpMonth("12");
card.setExpYear("2025");
card.setCvn("123");

try
{
    Transaction response = card.authorize(new BigDecimal("129.99"))
        .withCurrency("EUR")
        .execute();

    String result = response.getResponseCode(); // 00 == Success
    String message = response.getResponseMessage(); // [ test system ] AUTHORISED
}
catch (ApiException e)
{
    // handle errors
}

Test Card Data

Testing Exceptions

During your integration you will want to test for specific issuer responses such as 'Card Declined'. Because our sandbox environments do not actually reach out to issuing banks for authorizations, there are specific transaction amounts and/or card numbers that will trigger gateway and issuing bank responses. Please contact your support representative for a complete listing of values used to simulate transaction AVS/CVV results, declines, errors, and other responses that can be caught in your code. Example error handling code:

try
{
    Transaction response = card.authorize(new BigDecimal("-5.00"))
        .withCurrency("EUR")
        .withAddress(address)
        .execute();
}
catch (BuilderException e)
{
    // handle builder errors
}
catch (ConfigurationException e)
{
    // handle errors related to your services configuration
}
catch (GatewayException e)
{
    // handle gateway errors/exceptions
}
catch (UnsupportedTransactionException e)
{
    // handle errors when the configured gateway doesn't support
    // desired transaction
}
catch (ApiException e)
{
    // handle all other errors
}

Contributing

All our code is open sourced and we encourage fellow developers to contribute and help improve it!

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Ensure SDK tests are passing
4. Commit your changes (git commit -am 'Add some feature')
5. Push to the branch (git push origin my-new-feature)
6. Create new Pull Request

License

This project is licensed under the GNU General Public License v2.0. Please see LICENSE.md located at the project's root for more details.