Decisioning Logic

Last updated: September 23, 2026

Understand the how to create auto decisioning rules

Overview

Glide offers extensive customization options for creating rule sets to automate application decisions. Financial institutions can define rules based on various factors to determine whether an application is automatically approved, sent to pending, or denied.

How to Request a New Rule

When submitting a request for a new rule, provide the following details:

Rule Name
A unique name to identify the rule.
Description
A brief overview of the rule's purpose and how it operates.
Dashboard Text
The message displayed in the dashboard for this rule.
Pending Reason
The reason shown to staff when an application is sent to pending status.
Action
Specify whether the application should:
- Be sent to pending, or
- Be automatically denied.
Level
Indicate the scope of the rule (can choose multiple):
- Membership level
- Share level
- Role level
Environment
Specify where the rule applies:
- Applications submitted via the dashboard
- Applications submitted via the digital channel

Standard Rules

Rule name	Verbiage in Dashboard	Action	Level	Environment	Notes
Member address is classified as a commercial/business address.	Member address is classified as a commercial/business address.	Pending	Membership	Dashboard, digital channel
ChexSystems® report requires manual review.	ChexSystems® report requires manual review.	Pending	Membership, Share	Dashboard, digital channel
Applicant has failed ChexSystems.	Applicant has failed ChexSystems.	Pending	Membership, Share	Dashboard, digital channel
Applicant ID information has an address mismatch.	Applicant ID information has an address mismatch.	Pending	Membership	Dashboard, digital channel	If an ID is scanned and the address on the ID does not match the address entered into the application.
Fraud checks require manual review.	Fraud checks require manual review.	Pending	Membership	Dashboard, digital channel
SSN matches Primary Member	SSN matches the primary applicant on this membership	Pending	Role	Dashboard, digital channel
SSN matches Existing Role (non-primary)	This SSN matches an existing role on this membership	Pending	Role	Dashboard, digital channel

Supported Variables

The following variables can be used when setting up decisioning rules:

Age of Member: Define conditions based on the applicant's age.
Location of Member: Apply rules using the applicant's zip code or city.
Number of Joints/Beneficiaries: For example, send to pending if more than one joint applicant is listed.
International Flow: Trigger rules if the applicant selects "No" to the question, "Do you have a SSN/ITIN?"
Selected Product: Set rules based on the product chosen during the application.
Existing Product: Trigger actions if the account holder already holds a specific product.
Membership Creation: Identify whether the membership was created before or outside of Glide.
System Flags: Use warning codes (Symitar), stop codes/alerts (XP2), or notes (Keystone) as variables.
- Note: Please consult your Digital Program Manager (DPM) to confirm supported variable levels.
Address Match: Check if the inputted address matches the address on the submitted ID (if the ID includes an address).
Eligibility Type: Trigger rules based on the specific eligibility type selected.
Non-U.S. Person: Send applicants that select "No" to “Are you a U.S. citizen or other U.S. person, including a resident alien individual?” to pending.