Files 📁

Your financial institution may use a Document Storage solution, such as: MVI LaserFiche, JackHenry Synergy, Fiserv Nautilus, etc.
​

Glide will securely send any documents related to accounts to your configured SFTP destination. From this server, it is up to your financial institution how you would like to uptake files from this server into your chosen Document Storage vendor.

Account Opening Documents 📑

How it Works

Glide automatically generates or collects a number of documents related to the applicant’s account: ChexSystems reports, signature cards, identification documents (Driver’s Licenses, Passports, etc.), and eligibility verification documents.

Once collected from the applicant, Glide will send any new documents collected from our application to your SFTP server every 5 minutes. If a document is missing from the SFTP server, it may be because it has recently been created/received and the next scheduled delivery run has not yet occurred.

Naming Conventions

Glide is happy to abide by your financial institution’s existing naming conventions for documents — meaning, if certain document types follow a naming format that is used to differentiate it from other document types, Glide will work with your IT team during the integration to ensure we are naming files correctly.
​

For solutions such as Jack Henry Synergy (and others), if a companion file is required to be sent alongside a given file, we will work with your IT team to configure the companion file correctly.

ACH Origination & NACHA Files 🔔

How it Works

Glide is able to generate NACHA Files for ACH funding transactions submitted via Glide for that day of transaction activity. The time at which this document is sent to your financial institution is up to you and your accounting team.
​

We are able to combine debit & credit transfers into one file, or separate them out into individual files. We are also able to delay sending credit files, if your financial institution does not warehouse ACH credit files. Let us know how you handle ACH and we are happy to work with you!

For more info on ACH origination & NACHA files, see here.

Signature Pads 📝

Glide is able to automatically complete your financial institution’s signature card upon applicant disclosure opt-in. Once an applicant agrees to the disclosures presented, we will automatically fill out the signature card and prepare it for delivery via the SFTP method outlined above.
​

However, if an applicant is opening an account in-branch, we are natively integrated to the Topaz Signature Pads that your financial institution uses. Please refer to "Configuring Signature Pads in branch" guide below on how to install to requisite software for this purpose.
​

Domain Name System 🗄

At two points in the Glide integration period, we will ask your IT team to add DNS records to your chosen DNS vendor or system:

1. To allow Glide to send automated e-mails from your financial institution’s domain (e.g. no-reply@xyzcreditunion.org)

2. To host the final online applicant experience at your financial institution’s domain (e.g. join.xyzcreditunion.org)

For #1, we will send over 4 Records (2 MX, 1 SPF, 1 DKIM), generated from our chosen e-mail vendor Customerio. We will require the e-mail address that you’d like applicants to receive e-mails from, as well as a reply to address for replies to be routed to. Once your IT department adds these records, Glide is able to then automatically send e-mails during the Account Opening process to your applicants.
​

For #2, we will send over 4 NS Records to be added to your root domain (e.g. xyzcreditunion.org). One of these is to set up the domain certificate for your chosen production domain, and the other is to host the production applicant-facing application.

Please note that this is the only supported method of hosting the Glide application at your financial institution’s domain. If you’d like to opt for another method, additional fees will be incurred in order to support and maintain your financial institution’s custom DNS setup. The integration period may need to be extended in order to achieve a custom setup.
​

Document and ID Capture: Mobile Devices Only

Glide does not integrate with standalone document scanners or check scanners (such as Epson TM-S9000 or Digital Check Smart Source Elite).

For ID capture and document scanning within the Glide digital channel and staff dashboard, a mobile device with a camera is required — such as an iPhone or iPad. Plaid uses the device camera to capture and process identity documents via its IDV flow.

If your branch uses dedicated scanners for other purposes (e.g., check processing), those devices are not compatible with Glide's document capture workflow.