In order to process ACH transactions for member deposits, Glide generates NACHA files for transactions submitted via Glide.
NACHA files are generated on business days and do not generate on federal bank holidays. Cutoff times do not observe daylight savings time. Files are sent via SFTP to the credit union.
If your credit union warehouses ACH credits, we combine the debit and credit transfers into one file. If your credit union does not warehouse ACH credits, we can separate the debits and credits into individual files and send the credit with a delay for protection against return risk.
To view our set up instructions, ACH Origination Set Up guide.
ACH Origination Flow of Funds
ACH Deposit Journey Overview
Member would log in to their bank via Plaid Link within Glide.
Glide collects information such as how much the member wants to fund and the account and routing numbers
The next day, Glide generates a NACHA file with all the transactions from the previous day and SFTPs it to the credit union for processing.
Because the credit union will be originating the transactions, they will handle any returns directly in the core system.
Account and Routing Number Validation
Glide uses Plaid Link to receive external account and routing number. Members can verify their account and routing number by logging into their external financial institution or opt to receive a micro deposit to verify ownership of the account. Glide also leverages Plaid Identity to verify the initiator matches ownership of the linked bank account and Plaid Balance to verify the linked bank account has enough funds.