Enabling eChecks in CoreBridge allows you to quickly process checks directly through your CoreBridge system while also allowing your customers to make eCheck payment through the customer portal. 


Note: eChecks are currently only available when using Fiserv (formerly Clover Connect) as your integrated processor. 

    * For more information on how to enroll with Fiserv, please refer to Fiserv (Formerly Clover Connect) - A CoreBridge Integrated Merchant Services Provider.

    * If currently integrated with Fiserv, eCheck is an optional add-on to the standard merchant account. If you wish to add Echeck added to your account, complete the following form: CoreBridge | Fiserv. In the "Comments" box, include your current Fiserv merchant ID #, noting that you are interested in eChecks.



Table of Contents



Enabling eChecks


Once your eCheck account has been approved, please reach out to support@corebridge.net to have the eCheck functionality added to your CoreBridge system.

After the eCheck functionality have been added to your system by support, you can enable and manage it by completing the following steps:

1. Navigate to Management Module > Global Settings > Services.

2. Under Merchant Services, click Manage Settings for Fiserv. 



3. Toggle Enable eCheck to ON. 

4. Click Save Settings.




Using eChecks


eChecks can be entered by team members into your CoreBridge system, or by your customers through the Customer Portal. 


To enter an eCheck into your system:


1. Navigate to Sales Module > Orders and select the order you would like to add the eCheck payment to.

2. Click Enter Payment.



3. Select eCheck (online) from the Payment Type dropdown menu. 

4. Ensure eCheck has been selected from the Payment Method dropdown. 

5. Input the desired Payment Amount.

6. Input all eCheck information.

7. Input any needed Payment Notes. 

8. Click Submit Payment. 





Non-Sufficient Funds Applications for eChecks


Non-Sufficient Funds (NSF) applications are now available for eChecks. This enhancement gives users more flexibility when managing returned or rejected bank transactions—especially those due to insufficient funds. Instead of relying only on refunds to resolve these issues, users can now apply NSF logic to handle these cases more efficiently.


To access this enhancement:


1. Navigate to Sales Module > Orders and select the order.

2. Click on the Overrides tab.

3. Click Remove Payment.

4. Select the Action on the individual payment you would like removed.


Note: This feature is also available for ACH, EFT, and Wire Transfers.




Frequently Asked Questions


1. What is the difference between a decline and a reject / return?


  • Decline - A decline happens when a transaction is being processed. This can occur if the bank account (DDA) is recognized as invalid—such as if it's closed, doesn't exist, or has a history of issues. Once a DDA has been declined, it will always be declined. Reusing the same account for another payment attempt won’t work. Instead, the customer will need to use a different payment method.


  • Reject / Return - This usually occurs a few days after a transaction. A reject (or return) is a notice from the bank that the money transfer didn’t go through. When this happens, the original transaction is voided. If the reject is received before the funds are sent, the transaction won’t be funded. If the funds have already been sent, the money will be pulled back from the receiving bank account.