🚧

Work in Progress

ACH Overview

ACH transactions can be originated via the Create ACH Transfer endpoint. Please note that all ACH transactions created are originations, meaning that the ACH file is generated by your partner bank and sent to an external bank for processing. ACH transactions fall into one of two categories:

• ACH Push Origination
  • Generates a request to 'push' funds to an external account.
  • Your customer's account will be debited and the external account will be credited.
  • Indicated by 'C' for debitCreditIndicator in the /createAchTransfer call.
• ACH Pull Origination
  • Generates a request to 'pull' funds from an external account into your customer's account.
  • Your customer's account will be credited and the external account will be debited.
  • Indicated by 'D' for debitCreditIndicator in the /createAchTransfer call.
  • Your partner bank will typically require a set number of 'hold days' before ACH pull originations post to your customer's account to reduce returns and mitigate fraud.

Creating ACH Accounts

Before an ACH transaction can be initiated, you must create an ACH account to associate with the given customer (see Create ACH Account).

After creating the ACH account, you will receive an achAccountId which will serve as the unique identifier for the external account. Use this ID when calling the Create ACH Transfer endpoint.

📘

Please note

Your partner bank will likely limit the number of ACH account connections per customer account to limit fraud. ACH accounts can be removed via Remove ACH Account.

Plaid Integration

If you have a Plaid configuration with Spidr, you can use the processorToken to securely transmit the external account information. Using Plaid tokens obviates the need for storing or handling external account information. Please reach out to a Spidr contact if you are interested in integrating with Plaid.

If using a Plaid token, the external account balance is automatically validated to ensure sufficient funds for ACH pull originations.