Overview

Glide supports a special configuration where certificate funding is completed via a real-time share-to-share transfer (via the core's API), instead of leveraging the credit transaction on a NACHA file to move money into a members share.

In this configuration, no ACH credit ever posts to the member’s share or certificate. The member-facing funding is fully handled by the core transfer at approval time. This configuration is off by default.

Why This Configuration Exists

There are two primary reasons why your FI may opt to turn this configuration on:

1. Some cores do not allow inbound ACH credits into certificate accounts. When ACH credits attempt to post to certificates, they generate ACH exceptions that require manual resolution.

2. You'd like your members to start earning interest on the CD as soon as the approval happens, rather than wait for the ACH funding to land.

High-Level Flow Summary

There are two distinct and intentionally decoupled actions:

Real-time core transfer

• Funds the member’s certificate immediately upon approval.

ACH settlement via NACHA

• Moves money from the external bank into a CU GL account.

• Does not touch the member’s share or certificate.

Detailed Flow of Funds

Operational Considerations

• A holds on the certificate can be added simultaneous to the funding being added.

• ACH returns are handled by the credit union through standard return processes.

• Glide does not automatically unwind the core transfer if an ACH return occurs. Any corrective action follows manual procedures.