Frequently Asked Questions
If you can't find the information you're looking for below, please contact us.
If you are looking to build a custom integration, we recommend you start with our API Documentation. If you are looking to use one of our pre-certified shopping cart plugins, then head over to the Downloads page.
Your production keys will appear after you have completed a request for production keys. This process can take a business day to complete if all paperwork is complete and certification requirements are met.
Certification is our sandbox environment in which you can develop with test credit cards to ensure that your solution is working as expected. This is a formal process in which we ask developers to run specific dollar amounts against specific cards using their solution to ensure that transactions are coming across the wire correctly.
Heartland is a payment option in many of the most popular online payment platforms. For a complete list, please view our Full Plugin Details page.
A single use token is a string that represents a credit card. It can be used only one time and expires after a short duration. This token should not be stored. You can perform any action with our SDK that you would if you were using the card itself (charge, authorize, etc).
A multi-use token is a string that represents a credit card stored on Heartland's server. You can store this token on your server and perform any action with our SDK that you would if you were using the card itself (charge, authorize, etc). These tokens do not expire.
Using our tokenization jQuery (or Prototype) library correctly ensures that no credit card data is ever submitted to your server. This can reduce your PCI Scope as you are no longer dealing with credit card data. It is possible that this can remove your need for costly PCI scans in the future.