Log into Sandbox

This guide contains setup information and guidelines that should be reviewed prior to simulating incoming ACH transactions in the <<glossary:CV>> environment. See <a href="doc:simulating-incoming-ach-transactions" target="_blank">Simulating Incoming ACH Transactions</a> for instructions for the actual simulations. For instructions on testing outgoing ACH transactions, see “Testing outgoing ACH in the <a href="doc:ach-at-galileo" target="_blank">ACH at Galileo</a> guide.

Warning

Do not follow this procedure in <<glossary:Production>>. The simulating incoming ACH endpoints are only valid in CV.

Before simulating incoming ACH transactions, you should be familiar with the concepts in these guides:

  • <a href="doc:about-ach" target="_blank">About ACH</a> — Provides an overview of general ACH use cases, terminology, standards, and the movement of funds in a typical ACH transaction.

  • <a href="doc:ach-at-galileo" target="_blank">ACH at Galileo</a> — Explains terminologies and concepts for ACH, including transaction types, incoming vs outgoing ACH, NACHA files, and more. This will help in understanding how ACH works, as well as provide clarity in what values to use for Simulating ACH Transaction templates.

  • <a href="doc:galileo-ach-workflows" target="_blank">Galileo ACH Workflows</a> — Provides flowcharts that illustrate the different ACH workflows. Review the incoming ACH credits for information relevant to this guide.

  • <a href="doc:ach-endpoints" target="_blank">ACH Endpoints</a> — Provides guidance for using the ACH endpoints. The information relevant to simulating ACH transactions are the <a href="doc:ach-endpoints#creating-an-ach-transaction" target="_blank">creating</a>, <a href="doc:ach-endpoints#viewing-ach-accounts" target="_blank">viewing</a>, and <a href="doc:ach-endpoints#canceling-an-ach-transaction" target="_blank">canceling</a> ACH sections.

Note

This guide assumes that you have already set up your products in CV with the same characteristics that you will be using in <<glossary:Production>>.

## Initial setup

ACH requires additional setup. Work with Galileo to complete product setup.

## General guidelines when simulating incoming ACH transactions

The simulation endpoints do not support all of the possible values for an incoming ACH transaction. The supported values are defined by the template you specify in the <a href="page:create-simulated-ach-transaction" target="_blank">Create Simulated Incoming ACH Transaction</a> request. You must include either `CreditsAndDebits` or `ManualReviewNameMatching` in the template name or the request will fail.

  • Transaction data is stored and periodically processed on a scheduled basis. Reach out to Galileo to inquire about the processing schedule for your core.

  • After creating the simulated transactions, use these endpoints to see pending transactions and their results:

    • To view a transaction before it is processed:

      • <a href="page:get-simulated-ach-transaction" target="_blank">Get Simulated Incoming ACH Transaction</a> — Retrieve a simulated transaction by the transaction ID.

      • <a href="page:get-all-simulated-ach" target="_blank">Get All Simulated Incoming ACH Transactions</a> — Retrieve all simulated transactions.

    • To cancel a transaction before it is processed:

      • <a href="page:cancel-simulated-ach-transaction" target="_blank">Cancel Simulated Incoming ACH Transaction</a> — Cancel a simulated transaction by specifying the transaction ID.

    • To view processed transactions:

      • <a href="ref:post_getdeposithistory" target="_blank">Get Deposit History</a> — Retrieve deposit history for either your entire program or for a specified customer. Omit the `accountNo` parameter to get the history for your entire program. (Incoming credit transactions only.)

      • <a href="ref:post_getalltranshistory" target="_blank">Get All Transaction History</a> — Retrieve all processed transactions.

Note

Simulated incoming ACH transactions are processed periodically and results may not be immediately available.