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

[Add](🔗), [modify](🔗), and [remove ACH account](🔗) do not trigger an event. Please 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.

## Adding an ACH account

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:

• <a href="ref:post_addachaccount" target="_blank">Add ACH Account</a> — Add a personal account

• <a href="ref:post_addachaccountcorporate" target="_blank">Add ACH Account Corporate</a> — 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.

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 <a href="doc:ach-at-galileo#plaid-integration" target="_blank">Plaid integration</a> for more information.

The Add ACH Account and Add ACH Account Corporate endpoints return an `ach_account_id` that you will pass through the <a href="ref:post_createachtransaction" target="_blank">Create ACH Transaction</a> 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 <a href="ref:post_addachaccount" target="_blank">Add ACH Account</a> endpoint.

### Add ACH Account Corporate

This table describes parameters that are specific to the <a href="ref:post_addachaccountcorporate" target="_blank">Add ACH Account Corporate</a> endpoint.

## Viewing ACH accounts

Use the <a href="ref:post_getachaccount" target="_blank">Get ACH Account</a> endpoint to retrieve ACH account information. Pass the customer's PRN for `accountNo`, which you used in the <a href="ref:post_addachaccount" target="_blank">Add ACH Account</a> or <a href="ref:post_addachaccountcorporate" target="_blank">Add ACH Account Corporate</a> 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 <a href="ref:post_modifyachaccount" target="_blank">Modify ACH Account</a> 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 <a href="ref:post_removeachaccount" target="_blank">Remove ACH Account</a> 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.

## Creating an ACH transaction

Use the <a href="ref:post_createachtransaction" target="_blank">Create ACH Transaction</a> 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.

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

## Viewing ACH transactions

There are several endpoints for viewing posted and pending ACH transactions. When you view transactions for a specific account, the `accountNo` that you pass to the endpoint should be associated with at least one ACH account created with the <a href="ref:post_addachaccount" target="_blank">Add ACH Account</a> or <a href="ref:post_addachaccountcorporate" target="_blank">Add ACH Account Corporate</a> 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.

## Canceling an ACH transaction

Use the <a href="ref:post_cancelachtransaction">Cancel ACH Transaction</a> 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 returns](🔗) 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.

## 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 <a href="ref:post_modifypendingdepositstatus" target="_blank">Modify Pending Deposit Status</a> 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`).

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