Overview

Glide supports a special configuration where account 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 member's account.

This configuration was originally available for certificates and now also supports savings and checking accounts. Each FI can choose to apply it to all eligible product types or to certificates only.

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

Configuration Option

When this configuration is enabled, the FI selects which products it applies to:

• All product types — the real-time core transfer applies to certificate, savings, and checking funding on approval.

• Certificates only — the real-time core transfer applies to certificate funding only; savings and checking continue to fund via standard ACH.

Why This Configuration Exists

There are three 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 as soon as the approval happens, rather than wait for the ACH funding to land (where applicable to the product).

3. You'd like your members to see the money in their account as soon as they fund.

High-Level Flow Summary

There are two distinct and intentionally decoupled actions:

Real-time core transfer

• Funds the member's account (certificate, savings, or checking) 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, savings, checking, or certificate.

Detailed Flow of Funds

Operational Considerations

• A hold on the account 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.

• Behavior is identical across all enabled product types — holds, ACH return handling, and the no-auto-unwind rule apply the same way to certificate, savings, and checking funding.