Loading...
Existing customers: Get your sandbox and production credentials for Heartland/Portico integration.
No, you will need to complete a certification for each type of transaction.
Required transaction types are SALE, VOID, and RETURN. You can also include optional transactions, including:
Yes, you may run other transactions. However you must run transactions for the amounts identified on the list of test cases. Otherwise, we won’t be able to issue your certification letter.
You should use the credentials assigned at the beginning of the process throughout certification so that transactions can be properly tracked and identified. This is required for us to issue your certification letter.
Please make sure that you’re working with a Sales Representative at the beginning of the certification process. If you don’t have one, please contact support, and we’ll assign one to work with you.
Please reach out to your Sales Representative or Relationship Manager. If you don’t have a Sales Representative or Relationship Manager, please contact support, and we’ll assign one to work with you.
Providing AVS and CVV data points is a key security feature that should be passed when processing card transactions.
This is not mandatory but we highly recommend it. AVS and CVV can protect merchants against chargebacks if the response code is returned as a match and later the transaction is found to be fraudulent.
To view transactions under your gateway account, make sure you’re processing transactions with the correct API keys. If you're unsure what your API keys are, please contact support.
Multi-use tokenization must be enabled on your account in order to receive tokens back in the response. Reach out to our support team to have this functionality added. Please note this can take up to 72 business hours.
Our SDKs that support Apple Pay are:
Please see the link below for information on setting up Apple Pay for your website.
Set up Apple PayOur SDKs that support Google Pay are:
Click on the link below to get all the details on setting up Google Pay for your website.
Set up Google PayWhen an integration attempts to obtain a single-use token from our gateway through our token service, a 403 response will only be returned if:
For example, a 403 response will be returned if the TID in use has been deactivated due to account termination.
If you get a 403 response, verify that the API key you are using is valid and that the account associated with the API key is active. If the key is valid and the account is active, contact support for assistance.
No problem! Please contact our support team and we’ll be happy to assist.
Site security must be implemented on the integrator’s side. We will provide the documentation for this when we send the certification credentials.
The Certification Team expects that your custom integration is built out so you can process the test cases according to the transaction type you want to get certified. At the same time, we understand there can be issues that need to be worked out. If you run into problems and need assistance, please contact us for support.
Make sure you’ve read the certification credentials email thoroughly so you don’t miss steps in the process. If you haven’t received an email with your credentials, please contact us for support.
You may receive the following response from Portico, which stems from schema validation errors usually caused because the data supplied in the request doesn’t conform to Portico's requirements. The error from the stack trace reads: Unexpected http status code [InternalServerError].
API Key delivery can be configured via webhook through the Developer Portal:
The public API key is used to obtain a single-use token for online payments.