Guides
Log into Sandbox

Galileo ACH Workflows

Suggest Edits

The workflow for ACH processing at Galileo depends on whether the transaction is incoming or outgoing and whether it debits or credits the receiver’s account.

📘

Note

If an ACH transaction is denied after the RDFI receives the transaction, then the return workflow starts.

Outgoing ACH debit workflow

This flowchart illustrates an outgoing ACH transaction that moves funds out of an external account. The steps are described below.

In this example, product settings specify four hold days.

  1. Your customer makes an ACH debit request on Monday at 13:30 and you pass the request in a Create ACH Transaction call.
  2. Galileo prepares a Nacha file at the next scheduled time, Monday at 13:45 in this example. The file contains the transaction data, and Galileo sends the file to the ODFI via SFTP. The timer for hold days starts, with Monday being day one.
  3. The ODFI sends the Nacha file to the ACH operator.
  4. The ACH operator sends a Nacha file to the RDFI that contains the transaction request.
  5. The RDFI verifies that funds are available and debits the amount from the receiver’s account.
  6. On Friday at 00:00, the hold days expire and Galileo credits your customer's account. The funds are now available.
  7. The ACH operator moves funds between the ODFI and RDFI during settlement.

Outgoing ACH credit workflow

This flowchart illustrates an outgoing ACH request that moves funds into an external account. The steps are described below.

  1. Your customer makes an ACH credit request and you pass the data to the Create ACH Transaction endpoint.
  2. Galileo adjusts the amount for the transaction from your customer’s account and transfers the funds to the ODFI.
  3. Galileo prepares a Nacha file and sends it to the ODFI via SFTP.
  4. The ODFI sends the Nacha file to the ACH operator.
  5. The ACH operator sends a Nacha file to the RDFI that contains the transaction.
  6. The RDFI verifies that the receiver’s account can accept the funds.
  7. The RDFI credits the receiver’s account.
  8. The ACH operator moves funds between the ODFI and RDFI during settlement.

Outgoing ACH returns workflow

This flowchart illustrates the process that occurs when the RDFI rejects an ACH credit or debit request from your customer in the Galileo system. The steps are described below.

  1. The RDFI receives a Nacha file that contains the customer's request.
  2. The receiver or RDFI rejects the transaction request from your customer.
  3. If necessary, the RDFI adjusts the transaction amount for the receiver’s account.
  4. The RDFI prepares a Nacha file containing information for the return and sends it to the ACH operator. The information includes a notice of change that states the problem and how to correct it.
  5. The ODFI sends the Nacha file to Galileo.
  6. Galileo processes the Nacha file and reviews the notice of change.
  7. If necessary, Galileo adjusts funds for your customer’s account.
  8. Your customer receives a notification of the return.
  9. The date of return and the return code are recorded in your customer’s account transaction history.

Incoming ACH debit workflow

This flowchart illustrates an incoming ACH transaction that moves funds out of your customer’s account in the Galileo system. The steps are described below.

  1. The external originator makes an ACH request to move funds out of your customer’s account. The originator sends the request to their ODFI.
  2. The ODFI prepares a Nacha file and sends it to the ACH operator. The timer for the waiting period starts.
  3. The ACH operator sends a Nacha file to the RDFI that contains the request.
  4. The RDFI sends the Nacha file to Galileo.
  5. Galileo validates the Nacha file and verifies that funds are available.
  6. Galileo adjusts the amount from your customer’s account and transfers them to the RDFI.
  7. The ODFI moves the funds into the originator’s account after the mandatory waiting period expires.
  8. The ACH operator moves funds between the ODFI and RDFI during settlement.

Incoming ACH credit workflow

This flowchart illustrates an incoming ACH transaction that moves funds into your customer’s account in the Galileo system. The steps are described below.

  1. The external originator makes an ACH request to move funds into your customer’s account. The originator sends the request to the ODFI.
  2. The ODFI prepares a Nacha file and sends it to the ACH operator.
  3. The ODFI debits the funds from the originator’s account.
  4. The ACH operator sends a Nacha file to the RDFI that contains the transaction.
  5. The RDFI sends the Nacha file to Galileo.
  6. Galileo validates the Nacha file and verifies that the receiver can accept the funds.
  7. The RDFI transfers the funds to Galileo.
  8. Galileo credits your customer’s account with the funds for the ACH transaction.
  9. The ACH operator moves funds between the ODFI and RDFI during settlement.

Incoming ACH returns workflow

This flowchart illustrates the process that occurs when you or Galileo reject an ACH credit or debit from an external originator. The steps are described below.

  1. You or Galileo reject an incoming ACH transaction and mark it for return. You can reject an incoming ACH transaction before or after the funds transfer to the receiver.
  2. If necessary, Galileo adjusts the transaction amount for your customer’s account.
  3. If necessary, Galileo transfers funds to the RDFI.
  4. Galileo prepares a Nacha file with the return and sends it to the RDFI.
  5. Galileo also sends an ACH return code and a trace code that the ODFI can use for tracking.
  6. Galileo records the date of return and the return code in your customer’s transaction history.
  7. The RDFI sends the Nacha file to the ACH operator.
  8. The ACH operator sends the Nacha file to the ODFI.
  9. The ODFI processes the Nacha file and verifies the return.
  10. If necessary, the ODFI adjusts funds back to the originator’s account.

Incoming ACH reversals workflow

This flowchart illustrates an incoming ACH reversal. The steps are described below.

  1. The originator sends a request to their ODFI to reverse an incoming ACH debit or credit transaction to your customer’s account.
  2. The ODFI submits the ACH reversal transaction to the ACH operator.
  3. The ACH operator sends the Nacha file to the RDFI.
  4. The RDFI parses the Nacha file and sends the relevant transaction to Galileo.
  5. Galileo validates the Nacha file and verifies that the receiver can accept the funds.
    a. Credit reversals – No attempt is made to find the original transaction. Galileo posts the reversal and credits your customer’s account without any special conditions.
    b. Debit reversals – Galileo attempts to match the incoming debit reversal with a prior credit for the same transaction amount and from the same account within a 10-day window.
    1. If a match is found and the original credit has posted, the debit reversal is posted.
    2. If a match is found and the original credit has not been posted, both transactions (debit reversal and credit) are canceled. Furthermore, the transactions will not appear in the cardholder's transaction history.
    3. If no match is found, the reversal is processed as a regular debit.

Updated 3 months ago

Galileo Financial Technologies, LLC 2024

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.