2.21 Commerce Release Guide - Heartland Payment Gateway

Owned by Jenni Buonanni
Last updated: Mar 24, 2023 by Sarah Holst
3 min read

This feature is supported for: All resorts with an active agreement with Heartland Payments. Note that this feature is most full-featured for resorts that use RTP|One as a POS. The RTP|One version 2021 has token integration from Commerce into RTP|One so that credit card tokens used online can be stored in the POS to facilitate easier refunds, Resort Charge, and other RTP|One functionality, like RTP Payment Plans.

This feature is NOT supported for: Any resort with NO active agreement with Heartland Payments. Note that token integration into the POS is only supported on the recent RTP|One version 2021 .

This guide will review how to set up Heartland as a Payment Gateway in Aspenware Commerce. For more information on general release notes, see 2.21 Release Notes.

Overview

Resorts based in the USA can choose to work with Heartland Payments for their e-commerce credit card processing. Heartland is a preferred provider for Aspenware. Heartland offers enhanced token-based functionality and the ability to integrate tokens into RTP|One as well, available for users of the latest version of RTP|One (2021). Our robust integration includes all the standard credit card and integrated fraud prevention functions.

Configuration Guide

NOTE: Aspenware is currently developing a more detailed guide for steps required to get started with Heartland Payments. If you are interested in implementing Heartland Payments, please reach out to Phil Kirpatrick at Heartland (philip.kilpatrick@e-hps.com).

  • Work with your Aspenware Representative to install the Heartland Payments Plugin. Go to Configuration > Local Plugins and find the Heartland Payment Provider plugin to install it. You need to restart the application for the plugin install to take effect.

  • Once installed, go to Configuration > Settings > Payment methods. Select to Configure ‘Heartland Payment Provider.’

    1. Use Sandbox: checked for test environment, Unchecked if configuring for a production environment.

    2. Public Key: This will be received from Heartland to input. Note that the public and secret keys are unique, and cannot be interchanged between Sandbox and Production environments.

    3. Secret Key: This will be received from Heartland to input. Note that the public and secret keys are unique, and cannot be interchanged between Sandbox and Production environments.

    4. Requires Billing Address: Must be checked, so AVS verification can function.

  • The following values can be entered from the Configure screen to customize the field labels and error messages on the payment page. The following items can be customized:

    1. Card Number Label

    2. Card Number Placeholder

    3. Card Number Invalid Title

    4. Card Number Invalid Message

    5. Expiration Label

    6. Expiration Placeholder

    7. Expiration Invalid Title

    8. Expiration Invalid Message

    9. CVV Label

    10. CVV Placeholder

    11. CVV Invalid Title

    12. CVV Invalid Message

    13. Name Label

    14. Name Placeholder

    15. Name Invalid Title

    16. Name Invalid Message

  • Next, from Configuration > Settings > Payment methods choose to Edit the Heartland Payment Provider. Check Is Active and Update to activate.

  • Finally, from Configuration > Languages > English, search for the resource name: 'Checkout.ResortCharge.UsePaymentCreditCardForResortCharge.' Change the value associated with this string to edit the reminder that the card you have entered will be saved for Resort Charge use in RTP|One.

Coming Soon

  • The ability to update resort charge credit cards in my account is not yet supported but is expected to be announced for the 2.22 (mid-Oct 2021) release.

  • The ability to utilize Aspenware Payment Plans and Subscriptions is not yet supported but is expected to be announced for the 2.23 (mid-Nov 2021) release.