ACH Endpoints

The following tables summarize ACH endpoints in the Galileo system. Endpoints are grouped by outgoing ACH and incoming ACH. See the sections below for information on how to use each endpoint.

Outgoing ACH endpoints

Use endpoints in this table to create and view outgoing ACH transactions that originate at Galileo.

📘

Note

The Add ACH Account, Modify ACH Account, and Remove ACH Account endpoints do not trigger an event. Refer to the API response to confirm the outcome of your request to these endpoints.

Incoming ACH endpoints

Use endpoints in this table to view and modify incoming ACH transactions from an external originator.

ACH accounts

There are two types of external accounts that can be added as ACH accounts: personal and corporate. A personal account belongs to a natural individual, and a corporate account belongs to a business entity. To add each type of account use these endpoints:

• Add ACH Account — Add a personal account
• Add ACH Account Corporate — Add a business account

By using these endpoints, you set up ACH transactions where the originator is your customer’s account in the Galileo system and the receiver is the external account. Each ACH account stores the information for only one external account. You will need to add a new ACH account for each external receiver account. Prior to calling these endpoints, you must have a US-based account with a PRN already set up that supports ACH.

When you add an ACH account, you provide the external bank account and routing numbers to make direct ACH transfers with the external account. Alternatively, you can use Plaid integration to get external account information. See Plaid integration for more information.

The Add ACH Account and Add ACH Account Corporate endpoints return an ach_account_id that you will pass through the Create ACH Transaction endpoint when your customer originates an ACH transaction with the external account.

📘

Note

A customer can have multiple ACH accounts that use the same account and routing numbers as long as each duplicate ACH account is linked to a different account type. For example, you can add separate ACH accounts to a checking account PRN and savings account PRN that each link to the same external account.

You can also call Add ACH Account multiple times for the same PRN, as long as the external account numbers are different.

Add ACH Account

This table describes parameters that are specific to the Add ACH Account endpoint.

Add ACH Account Corporate

This table describes parameters that are specific to the Add ACH Account Corporate endpoint.

Viewing ACH accounts

Use the Get ACH Account endpoint to retrieve ACH account information. Pass the customer's PRN for accountNo, which you used in the Add ACH Account or Add ACH Account Corporate endpoint, to this endpoint. Do not pass an ach_account_id for accountNo.

If there are multiple ACH accounts linked to the accountNo, the Get ACH Account endpoint returns information for each ACH account. The found field in the response data indicates the number of ACH accounts that are linked to the accountNo.

Modifying ACH accounts

Use the Modify ACH Account endpoint to update ACH account information. When using Modify ACH Account, you must specify the entityType of the account to modify:

• C — Corporate ACH account. The account was created using Add ACH Account Corporate.
• I — Individual ACH account. The account was created using Add ACH Account.

Depending on the value of entityType, other fields are also required:

• entityType: C — companyName is required
• entityType: I — firstName and lastName are required

Removing an ACH account

Use the Remove ACH Account endpoint to remove an ACH account. ACH account records cannot actually be deleted from the Galileo system, but a removed account is deactivated so that it can no longer be used for ACH transactions. A removed ACH account is set to status: D (deleted).

This table describes parameters that are specific to the Remove ACH Account endpoint.

ACH transactions

You can manage ACH transactions using the following procedures.

Creating an ACH transaction

Use the Create ACH Transaction endpoint to originate an outgoing ACH transaction where the originator is your customer in the Galileo system and the receiver is the holder of an external account.

📘

Note

When initiating a transaction with the Program API, the transactionId from the API request is copied to the external transaction ID field of all transactions that result from the request. The external transaction ID is available in the responses to transaction-retrieval Program API requests as external_trans_id, in the Posted Transactions RDF as EXTERNAL TRANSACTION ID, and in the Events API messages as ext_trans_id.

This table describes parameters that are specific to the Create ACH Transaction endpoint.

Viewing ACH transactions

You can use one of several endpoints to view posted and pending ACH transactions. The accountNo that you pass to the endpoint must be associated with at least one ACH account that was created with the Add ACH Account or Add ACH Account Corporate endpoint. If there are multiple ACH accounts linked to the accountNo, Galileo returns transaction information for each ACH account.

This table describes endpoints for viewing ACH transactions.

Consult Finding Transaction Data to see where else ACH transactions are visible.

Canceling an ACH transaction

Use the Cancel ACH Transaction endpoint to cancel an outgoing ACH transaction originated by your customer in the Galileo system. You cannot cancel an ACH transaction in this manner after Galileo processes the transaction and adds it to a Nacha file. If you need to stop a transaction after Galileo generates the Nacha file, you must initiate an ACH return. See ACH at Galileo for more information.

The cutoff time to cancel an ACH transaction varies from client to client. You can contact Galileo to get the approximate time the Nacha file is generated for your core.

When an ACH transaction is successfully canceled, any funds debited from your customer’s account are returned and a BADJ: adj event is generated.

This table describes parameters that are specific to the Cancel ACH Transaction endpoint.

📘

Note

If you call Create ACH Transaction, and then call Remove ACH Account, the transaction is not canceled, because the account existed at the time the transaction was created. The ACH transaction process does not check the account status again.

Modifying a pending ACH deposit status

A pending ACH deposit is an incoming ACH credit that has not been posted to the customer’s account. You can use the Modify Pending Deposit Status endpoint to either post or return a pending ACH direct deposit before it is posted to the account. In most cases you will modify pending ACH direct deposits that are flagged for review (status: i). When you post a pending ACH deposit, Galileo sends the BPMT: pmt event message.

This table describes parameters that are specific to the Modify Pending Deposit Status endpoint.

Testing ACH transactions

You can create simulated incoming ACH transactions in the CV environment using specialized endpoints. See Setup for Incoming ACH Transaction Simulation for instructions.