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.
HINT: Select show ‘100’ at the bottom of the screen to load and search from all plugins.
Once installed, go to Configuration > Settings > Payment methods. Select to Configure ‘Heartland Payment Provider.’
Use Sandbox: checked for test environment, Unchecked if configuring for a production environment.
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.
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.
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:
Card Number Label
Card Number Placeholder
Card Number Invalid Title
Card Number Invalid Message
Expiration Label
Expiration Placeholder
Expiration Invalid Title
Expiration Invalid Message
CVV Label
CVV Placeholder
CVV Invalid Title
CVV Invalid Message
Name Label
Name Placeholder
Name Invalid Title
Name Invalid Message
Next, from Configuration > Settings > Payment methods choose to Edit the Heartland Payment Provider. Check Is Active and Update to activate.
IMPORTANT: Make sure to mark all other payment gateways, except Affirm, as inactive so that only the Heartland Payment Plugin is installed for payment. Aspenware strongly recommends working with your Aspenware representative to uninstall other payment gateway plugins that are no longer in use.
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.