Instant

The Galileo Instant Developer Hub

Welcome to the Galileo Instant developer hub. You'll find comprehensive guides and documentation to help you start working with Galileo Instant as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Cardholder Agreements

There are three agreements your customer must read and agree to before you can create a Cardholder. These include the Electronic Communications Agreement, Deposit Account Agreement, and Privacy Policy. A fourth agreement may be added, if necessary, including information specific to your use case that isn't covered in the other three agreements.

The agreements

Electronic Communications Agreement

By default, banks are required to deliver certain information in writing. The Electronic Communications Agreement obtains your cardholders' consent to receive communications in electronic form vs. physical form. This agreement must be the first agreement presented to your customer. If the customer doesn't agree to electronic communications, you will be unable to continue with their enrollment process because paper documents and "wet signatures" would be required.

Deposit Account Agreement

The Deposit Account Agreement, also known as a Cardholder Agreement, defines everything that is expected from the card program from a legal standpoint. It outlines everything from account creation to ACH transfers to customer service.

Privacy Policy

The Privacy Policy explains how a cardholder's personal data are handled, including data gathering, data use, and data protection.

Presenting the Agreements to Your Customers

Step 1: Accessing the agreements

Your cardholders must agree to each agreement during their on-boarding process. Use the API to get the Agreements, passing in your business_id (found in the Dashboard by clicking "Settings" > "Account Information") and product_id as the path parameters. The response contains the agreement_id and url of each agreement.

Step 2: Present the Electronic Communications Agreement

The Electronic Communications Agreement must be presented to and accepted by cardholders before presenting the other agreements. Use the url associated with the Electronic Communications Agreement (agreement_type = electronic_communications) to present the Agreement PDF to the customer. While presenting the agreement, the screen title should read "Electronic Communications Agreement." At the bottom of the screen, below the last page of the agreement, provide a button for accepting the agreement, with accompanying language that reads "By tapping 'Accept,' I agree to the Electronic Communications Agreement."

Step 3: Present the Deposit Account Agreement

Use the url associated with the Deposit Account Agreement (agreement_type = deposit_account_agreement) to present the Deposit Account Agreement. The screen title should read "Deposit Account Agreement." At the bottom of the screen, below the last page of the agreement, provide a button for accepting the agreement, with the accompanying language that reads "By tapping 'Accept,' I agree to the Deposit Account Agreement."

Step 4: Present the Privacy Policy

Use the url associated with the Privacy Policy (agreement_type = privacy_policy) to present the Privacy Policy. The screen title should read "Bancorp Privacy Policy." At the bottom of the screen, below the last page of the agreement, provide a button for accepting the agreement, with the accompanying language that reads "By tapping 'Accept,' I agree to The Bancorp Privacy Policy."

Step 5: Notify Galileo that the agreements have been accepted

The API request to create a cardholder has a required parameter, agreements, that is a list of each agreement_id from the three agreements that were accepted in Steps 2 through 4 above. All three are required to create a cardholder.

Handling updates to the agreements

After the agreements have been accepted during on-boarding, they will continue to be updated as the program evolves. Galileo will send an email, notifying cardholders of upcoming updates. It is not necessary for cardholders to indicate their acceptance every time an agreement is updated. If a cardholder objects to an update and prefers to discontinue use of the product rather than accepting the new terms, they will be asked to close the account before the new update takes effect.

Making the agreements available within your app

Cardholders must be able to easily access each agreement from your app. You should consider including a "Legal" section in your app's "Settings" or "User Profile" sections to display the agreements.

Updated 2 months ago


Cardholder Agreements


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.