This article is for haulers who use FiServ / CardPointe. If you use Hauler Hero Payments, a returned ACH payment is reversed in Hauler Hero automatically, so you don't need these steps. See ACH Display Status.
Unlike credit cards, ACH transactions act more like checks and are not authorized in real time, which means transactions can be rejected (similar to a bounced check).
The network provides status codes when an ACH transaction is rejected. An ACH reject can occur for a number of reasons. For example, the bank account may be frozen or lack sufficient funds to cover the transaction.
If payments are unsuccessful, you are usually notified within two to four business days of the transaction (much quicker than the five to 10 days it takes with paper checks).
CardPointe does not send ACH rejections to Hauler Hero. We recommend regularly checking for failed ACH payments and/or requesting email notifications.
To locate rejected ACH payments in CardPointe:
Report > Transactions > Method = ACH Reject
(The date range defaults to the last 7 days. Select the Date dropdown to the left to extend the view if needed.)
If the ACH has been rejected, we recommend marking the payment as ACH FAILED within Hauler Hero. This logs the failed payment in the payment history and sets the invoice back to Unpaid.
Sign up for email notifications for your failed ACH payments
Email Notification Set-up:
Log into cardpointe.com as administrator.
From the Dashboard, you can configure the types of notifications that you receive by email.
Select the configure link.
Then select the tab 'Email Notifications'.
Place a check next to any item you wish to send you an email notification, then select Save.
CardPointe ACH Reject display (February 2024)
In February 2024, CardPointe changed how ACH Rejects are displayed in the CardPointe web application and API.
What Changed?
Previously, when a Fiserv ACH sales transaction was rejected, it resulted in the creation of an ACH return transaction line item that was included in a funding batch regardless of whether the transaction was successfully funded or not. ACH Rejects were displayed as negative entries within a funding batch and, in the case where the transaction was not successfully funded, the reporting was missing the positive entry for the transaction.
Now, when a transaction is rejected and has not been funded, no new ACH Reject transaction record is created. Instead, the status of the original sales transaction is marked as Rejected. The ACH return code linked to this transaction will be visible in the transaction table within the Transactions tab under Reporting, as well as on the Transaction Details page under Transaction History and History Data.
The offsetting ACH reject transaction no longer appears on the Funding tab within the Reporting section. Instead, the original transaction is assigned a funding batch and marked as "Rejected."
Below is an illustration of the previous reporting view, showcasing the creation of a new transaction record with a negative entry due to a rejected transaction.
Below is a snapshot of the current reporting view. This indicates that the Status of this transaction record has been updated to Rejected, instead of generating a negative entry in the reporting.
What Do I Need to Do?
As a result of the modification in ACH Reject reporting, you might need to make some adjustments in your financial records and accounting procedures. These changes in ACH Reject reporting could potentially impact how you maintain your books, which may require you to review and adapt your existing financial processes to ensure accuracy and consistency.
Feedback? Questions?
We'd love to hear your feedback to help us improve your experience. Please submit feedback through the chat bubble or email to support@haulerhero.com.






