Restricting Money Movement with Warning Codes
Restricting movement via warning codes is a feature that allows credit unions to control a member’s access to digital banking features using warning codes in Symitar, which helps manage risk and reduce potential fraud. Credit unions can configure which warning codes control which feature. Once a membership has a warning code applied to it, any feature that is configured to be controlled with that warning code will be disabled for the membership.
How does this feature work?
Warning codes are applied to memberships in Symitar. When a warning code is applied to a membership, Banno will detect the warning code and determine if a feature needs to be restricted based on that warning code. If the warning code is not expired, access to any feature that is configured to be controlled by that warning code will be restricted. Banno looks for changes in warning codes on every sync. When a feature is restricted by a warning code, the end user will completely lose access to that feature.
For example, if warning code 50 restricts access to Zelle, any user tied to a membership with warning code 50 will no longer see Zelle in their menu within Banno Online or Mobile.
Since warning codes are applied to entire memberships and not individual users/name records or specific shares/loans, all users tied to that membership will be impacted by the warning code across all shares/loans. This applies to all types of users in Banno (traditional retail users, household users, and business users).
When Banno detects a warning code has been applied to a membership, any user that has enrolled using that member number will be impacted. A banner will display at the top of the Permissions tab on their profile in People and any feature that is impacted will become uneditable.
Institution administrators with the proper permissions can manage these configurations in Banno, linking one or more warning codes (as single codes, ranges, or a combination) to a restriction. Administrators can also review warning code configurations in Banno People and cross-reference that configuration with the warning codes attached to the membership in Banno People. At this time, identifying which feature is being restricted due to a warning code is not supported. While the impacted features will be uneditable, there will be no visual indication that the reason the feature is uneditable is due to a warning code.
Financial Institution Configuration
In order for a credit union administrator to manage the warning code settings, a group they are part of must have the People > Settings > Manage warning codes permission enabled.
Financial institution administrators with the appropriate permissions will be able to see and edit the warning code configuration settings under People > Settings > Warning codes.
Financial institution administrators without appropriate permissions will be able to see, but not edit, the warning code configuration settings.
Financial institutions can configure Banno to remove access to features based on warning codes. Warning codes can be entered as a single warning code, a range, or a combination of both. Multiple warning codes can be configured for a feature and the same warning code can be used for multiple features.
Not all features support being restricted based on warning codes and not every feature can be restricted for every type of user. Below is a list of the supported features and user types to which they apply.
- Both retail and business users
- The following features can be disabled for household users, traditional retail users, and business users:
- Bill pay
- Inbound/outbound external transfers
- Rapid transfers
- RDC
- Retail users only
- The following features can be disabled for primary household users and traditional retail users:
- Zelle (send and request)
- Business users only
- The following features can be disabled for business users:
- ACH
- Wires
- Tap2Local