Alkami Release Notes - 2024.3.1

Product: Account Opening - Instant Open (optional product)

3rd Party Dependency: Fi Vision

Description: Fi Vision is depreciating support for showing the Instant Open SSO as an iFrame.

Expected Benefit: The Instant Open SSO will show as a new window or tab with the code update.

Activation: Open a JIRA Delivery ticket to asses the needed steps to change from an iFrame to a new window. If your Instant Open SSO is already showing as a new window, there is no need to open a ticket

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, the Instant Open SSO would display the single sign-on in an iFrame.

New Behavior: Now, the Instant Open SSO will show the single sign-on in a new window or tab.

Product: Alkami Digital Account Opening Platform

3rd Party Dependency: N/A

Description: The Promo Code field label on the Promo Code Checkout page is configurable.

Expected Benefit: Financial institutions can configure the Promo Code Checkout page to use it for promotions that don't use a promo code. For example, the page might be used for a Referral Name.

Activation: Open a JIRA Delivery ticket - this may require a Client Change Request (CCR)

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start an application. On the Promo Code page, the field label is {}Promo Code{}.

New Behavior: Start an application. If configured, the field on the Promo Code page displays the updated field label.

Product: Alkami Digital Banking Platform - Business Admin - Payees

3rd Party Dependency: N/A

Description: Updated the Guatemala Payee Information Corporate Tax ID field to support 14 digits for the payee international wire payment method.

Expected Benefit: Resolved an Issue

Activation: {color:var(--ds-text, #172b4d)}Automatically Enabled/Resolved with the Release{color}

Delivery Channel: Desktop, Mobile App

Previous Behavior: When adding an international payment method to a payee in Guatemala, the Nit ID/TaxId field only supports 11 digits.

New Behavior: When adding an international payment method to a payee account in Guatemala, the Nit ID/Tax Id field supports 14 digits,

Product: Alkami Digital Banking Platform - Business Admin Sub User Limits

Description: This update supports enhanced limits updates to external transfers.

Expected Benefit: When a Business Admin user sets up sub users, the sub users' external transfer limits validate against the enhanced external limits. These include retail ACH and add-on services such as RTP (Real-time Payments), FedNow, and debit cards. This enables Business Admin users to ensure their sub users can process payments successfully based on the enhanced new limit types.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile App

Previous Behavior: When creating or modifying a sub user, the sub user's limits for external transfer limits are validated against a single payment method limit.

New Behavior: When creating or modifying a sub user, the sub user's limits are validated against retail ACH debit and credit limits and add-on payment products such as RTP (Real-time Payments), FedNow, and debit cards.

Product: Alkami Digital Banking Platform - Message Center

3rd Party Dependency: N/A

Description: Alkami resolved an issue that allowed admin with Read Only VAU permissions to delete a message in the Message Center. Admin users with this permission can no longer delete messages.

Expected Benefit: Resolved an Issue

Activation: Automatically Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Previously, admin users with Read Only VAU permissions could delete a message from the client Message Center.

!Delete_Message Center Read Only Access Previous.png|thumbnail! !Deleted Message_Message Center Read Only Access Previous.png|thumbnail!

New Behavior: Now, admin users with Read Only VAU permissions can't delete a message from the client Message Center. If an admin user attempts to delete a message, they receive a notification indicating they don't have permission to perform the action.

!Delete_Message Center Read Only Access.png|thumbnail! !Incorrect Permissions Message_Message Center Read Only Access.png|thumbnail!

Product: Alkami Digital Banking Platform - Transaction Sync Status Failure Message

3rd Party Dependency: None

Description: Alkami implemented a message in digital banking that, upon login, informs the end user that not all transactions have been successfully synched from the core. This message is now configurable for all FIs. Using a setting in FI Admin, clients can prevent this message from being viewed in the mobile apps.

Expected Benefit: FIs can configure the Transaction Sync Status Failure message on or off.

Activation: Automatically Enabled with the 2024.3.1 Minor Release and the 4014.1.0 Mobile Release, clients must have both releases to use this functionality.
The setting to turn the message on or off is located in FI Admin by navigating to {}Setup > Widget Settings > MyAccountsV2{}.
The setting name is {}{{disableTransactionSyncStatusIndicator}}{}.
When set to true, the message doesn't appear.
When set to false, the message appears.

Delivery Channel: Mobile App and FI Admin

Previous Behavior: The system might display the Transaction Sync Status Failure message to all end users. Some financial institutions (FIs) reported an increase in call volumes because end users were confused by the message, which FIs couldn't deactivate. See the attached failure message for reference.

New Behavior: A new widget setting enables FIs to indicate whether the message appears to their Mobile app end users. This functionality will extend to Desktop end users in the future.

Product: Alkami Digital Banking Platform - Transfers

Description: Resolved an issue that could cause dual authorization to incorrectly be authorized by a business sub-user.

Expected Benefit: This change allows for Transfers to remain in a Needs Authorization status even when the transfer is edited by the initiator.

Activation: This change will be automatically enabled with this release.

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, if a business sub-user scheduled a Transfer that Needs Authorization and they edit the transfer details (ex: memo) then after saving their changes, the transfer status would update out of the Needs Authorization status bypassing the need for secondary authorization{_}.{_}

New Behavior: Now, even when the initiator edits the transfer (ex: updates the memo value) the transfer will remain in a Needs Authorization status.

Product: Alkami Digital Banking Platform - Transfers

Description: Removed the External Transfers User Level Override record when the end user is moved across packages in the Admin UI

Expected Benefit: Resolved an issue.

Now, when a User is moved across packages their access to External Transfers will match with the parent level package level configuration

Activation: This change will be automatically enabled with this release.

Delivery Channel: Admin

Previous Behavior: Previously, if an end user had an override record with External Transfers enabled and they moved into a package with External Transfers disabled and the package allowed overrides, the end user would still have access to External Transfers

New Behavior: Now, when an end user moves across packages their access to External Transfers will match with the parent level package level configuration. Their External Transfers privilege will match 1:1 with the existing package level configuration when they are moved into a package.

Product: API Account Endpoint (AFX/v2/api/accounts)

3rd Party Dependency: Clients can create registered applications in Alkami Admin and connect directly to Alkami APIs.

Description: Alkami supports DTC (Direct-to-Consumer) and B2B (Business-to-Business) APIs.

We identified an issue where admin users could access arbitrary accounts through the DTC endpoint, which wasn't the intended functionality.

The intended process for accessing arbitrary accounts is through the admin endpoint (/admin/v1/users/\{userIdentifier}/accounts/\{accountIdentifier}).

To correct this, we’ve updated the DTC endpoint to ensure it aligns with our original design and security protocols.

Expected Benefit: Resolved an issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile App, Admin

Previous Behavior: When an FI called Alkami's APIs directly, admin users were able to access arbitrary accounts through the DTC endpoint.

New Behavior: Admin users can't access arbitrary accounts through the DTC endpoint.

Product: Data eXchange - Sync Accounts

3rd Party Dependency: PSCU Data eXchange credit card processor

Description: Resolved an issue where business card reads fail

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The business card reads fail.

New Behavior: The business card reads are successful.

Product: Digital Account Opening - Retail Digital Account Opening

3rd Party Dependency: Symitar Core

Description: Resolved an issue with beneficiaries not being mapped to the core for existing user applications.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a DAO application as an existing user. Add a beneficiary. Approve and book the order to the core. The beneficiary isn't mapped to the core.

New Behavior: Start a DAO application as an existing user. Add a beneficiary. Approve and book the order to the core. The beneficiary is mapped to the core.

Product: Digital Account Opening - Retail Digital Account Opening

3rd Party Dependency: None

Description: Created a rule to check if the user's address is within the sales region.

Expected Benefit: FIs can identify when a user's address is within the sales region, and use this information as part of decisioning for an application.

Activation: Open a JIRA Delivery ticket to turn on this rule.

Delivery Channel: Desktop

Previous Behavior: A rule can identify if the user's zip code is included in a list of zip codes, but the rule doesn't automatically update sales regions.

New Behavior: A rule can identify if a user's zip code is within the FI's sales region. This rule automatically updates when sales regions are changed.

Product: Digital Account Opening - Retail Digital Account Opening

3rd Party Dependency: None

Description: Optimized the existing user lookup service to improve the load time on the Social Security Number (SSN) page.

Expected Benefit: End users will have a shorter load time or no load time on the SSN page.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile Web

Previous Behavior: End users experienced long load times when submitting the SSN page due to the processing time of the existing user lookup service.

New Behavior: End users experience a very short or zero load time after submitting the SSN page.

Product: Digital Account Opening - Retail Digital Account Opening - Jack Henry Symitar

3rd Party Dependency: Jack Henry Symitar

Description: Added support to pass the mailing address for joint owners when creating a new account on Jack Henry Symitar. The mailing address is stored as a name record with type 2.

Expected Benefit: FIs can store the mailing address of a joint owner when creating a new account on Jack Henry Symitar.

Activation: Open a JIRA Delivery ticket. This change requires installing a new Jack Henry Symitar PowerOn to enable storing the joint owner mailing address.

Delivery Channel: Desktop

Previous Behavior: The joint owner's mailing address wasn't stored in Symitar when a new account was created.

New Behavior: The joint owner's mailing address can be stored in a name record with type 2 when a new account is created on Symitar.

Product: Digital Account Opening - Retail Digital Account Opening - Jack Henry Synergy

3rd Party Dependency: Jack Henry Synergy

Description: Alkami can create separate Synergy files for approved and declined applications. This allows Alkami to configure the Synergy file fields to different values based on whether the application was approved or declined.

Expected Benefit: FIs can configure separate files for approved and declined applications, which enables the FI to pass the appropriate information based on the application's status.

Activation: Open a JIRA Delivery ticket.

Delivery Channel: Desktop

Previous Behavior: The same Synergy file field mapping was used for all applications regardless of the application status.

New Behavior: The Synergy file field mappings for approved and declined applications can be configured separately.

Product: Flux Advanced Analytics > Engaged Users dashboard

3rd Party Dependency: N/A

Description:

The Engaged Users dashboard has been fully deprecated.

The main focus of this dashboard was the user Relationship Score which was deprecated earlier, primarily for the following reasons:
The Customer Insights and Marketing Automation platform (formerly Segmint) provides a more extensive set of end user metrics called Key Lifestyle Indicators (KLIs).
The Customer Insights and Marketing Automation’s KLI finder streamlines customizing audiences for these types of aggregate calculations.
The factors that FIs want to evaluate in the Relationship Score vary and have evolved beyond the scope of this aggregated metric.

Activation: Automatically resolved

Delivery Channel:* Admin

Product: Horizon - Registration

3rd Party Dependency: FIS Horizon core

Description: Resolved an issue where the business end user sees a We are unable to locate your record based on the information you provided message when attempting to register a new account.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The business end user can't register a new account.

New Behavior: The business end user can register a new account.

Product: IBS - Sync Transactions

3rd Party Dependency: FIS IBS core

Description: Resolved an issue where an error from the core, when attempting to read account holds, resulted in the core provider not returning posted transactions.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user's posted transactions weren't being returned when the core attempted to read account holds.

New Behavior: The end user's posted transactions are returned by the core even if the reading of the account holds fails.

Product: KeyStone - Login

3rd Party Dependency: Corelation KeyStone core

Description: FIs can restrict end user access to digital banking based on the KeyStone table LOGIN column {{LOGIN_LOCK}} field {{newContents.}}

Expected Benefit: The FI can restrict digital banking access for individuals based on the KeyStone login lock status.

Activation: Configured by FI, new KeyStone provider setting {{UserHonorLoginLock}}
Description: When enabled, the Alkami Platform queries the table LOGIN column LOGIN_LOCK during user login. If the {{newContents}} field is N (for Not Locked), the Alkami Platform allows the user to log in. When not enabled, the Alkami Platform doesn't query this table.
Format: Boolean
Default: FALSE
Required? No

Delivery Channel: Desktop, Mobile App

Previous Behavior: The FI couldn't configure end user access to digital banking.

New Behavior: The FI can configure end user access to digital banking.

Product: KeyStone - Sync User

3rd Party Dependency: Corelation KeyStone core

Description: Resolved an issue with Core Restrictions.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: End users with member account exceptions returned from KeyStone were able to log into digital banking.

New Behavior: End users with member account exceptions returned from KeyStone aren't able to log into digital banking.

Product: Notification Manager - Alkami Digital Platform.

Description: Due to a security vulnerability identified with the Notification Manager in the Admin application, some alerts are no longer editable using that tool.

Expected Benefit: Resolves Security vulnerabilities that would have impacted the entire platform.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: All alerts were editable through the Notification Manager.

New Behavior: Some alerts are no longer editable through thr Notification Manager if they include Global or System parameters in the template such as the following alerts (alerts may differ per end user):
AddressChanged
BusinessACHAuthorizedAlert
BusinessACHCanceledAlert
BusinessACHExtendedPassThruDeliveryFailedAlert
BusinessACHExtendedPassThruRejectedByFIAlert
BusinessACHNeedsAuthorizationAlert
BusinessACHPendingFIReviewAlert
BusinessACHRejectedByFIAlert
BusinessACHSubmittedAlert
BusinessACHSucceededAlert
BusinessACHTemplateAuthorizationRejectedAlert
BusinessACHTemplateEditedAlert
BusinessACHTemplateExpiredAlert
EmailAddressChanged
PayeeChangeTemplate
PhoneChanged
TransactionAlert
TransactionFeeAlert
TransferFailedAlert
TransferSucceededAlert

If end users update these alerts that have System or Microsoft variables in them, they will receive an error in the Notification Manager.

!image-2024-06-28-11-26-44-994.png!!image-2024-06-28-11-27-39-168.png|width=618,height=370!

Product: Platform - Sync Account

3rd Party Dependency: N/A

Description: Resolved an issue where the Alkami Platform doesn't unhide accounts from end users. This scenario occurs when the Alkami Platform reads a core-scheduled transfer to a new account for the end user, and the account sync occurs after the read of the scheduled transfer. The scheduled transfer sync creates the account as a hidden account because it isn't associated with the end user in the Alkami Platform at the time of the sync, and the account sync doesn't unhide the account when it's being read from the core.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user doesn't see new accounts in their accounts list when the above scenario occurs.

New Behavior: The end user sees new accounts in their accounts list when the above scenario occurs.

Product: Premier CoO - Framework

3rd Party Dependency: Fiserv Premier core with Communicator Open interface

Description: Premier CoO system performance was improved by reducing the number of times it reads configuration settings.

Expected Benefit: Improved system performance

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The Alkami Platform performed redundant system calls when reading configuration settings.

New Behavior: The Alkami Platform reduces system calls to read item settings by replacing CoOSettings with ICoOSettings.

Product: Premier CoO - Sync Accounts

3rd Party Dependency: Fiserv Premier core with Communicator Open interface

Description: Resolved an issue where the end user doesn't see dividend transfer account information.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user doesn't see dividend transfer account information.

New Behavior: The end user sees dividend transfer account information.

Product: Premier CoO - Sync Accounts

3rd Party Dependency: Fiserv Premier core with Communicator Open

Description: To read RegDCount from TranCounter.Count where {}TranCountType = RegD6{}.

Expected Benefit: The ability to read RegDCount from the core so they may be applied to Reg D limits.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The Reg D count isn't read from the core.

New Behavior: The Reg D count is read from the core and may be applied to Reg D limits.

Product: Premier CoO - Sync Accounts

3rd Party Dependency: Fiserv Premier core with Communicator Open interface

Description: Added the ability to configure the account permissions associated with a Premier account relationship for Retail and Business Banking end users.

Expected Benefit: FIs can configure the permissions associated with a relationship for Retail and Business Banking end users.

Activation: Configured by FI
New Premier CoO provider setting PartyAccountPermissionsRetail
Description: Assigns Alkami user-account access rights based on the relationship from the core for Retail users.
Format: Same format as PartyAccountPermissions
Default: Alkami uses the PartyAccountPermissions configuration if this setting is not specified
Required? No
New Premier CoO provider setting PartyAccountPermissionsCorporate
Description: Assigns Alkami user-account access rights based on the relationship from the core for Business Banking users.
Format: Same format as PartyAccountPermissions
Default: Alkami uses the PartyAccountPermissions configuration if this setting is not specified
Required? No

Delivery Channel: Desktop, Mobile App, Admin

Previous Behavior: The permissions associated with account relationships are the same for Retail and Business Banking end users.

New Behavior: FIs can configure relationship-based permissions for Retail and Business Banking end users.

Product: Premier CoO - Sync Accounts

3rd Party Dependency: Fiserv Premier core with Communicator Open interface

Description: Eliminated the call to read account details for closed accounts when the FI has the core provider setting ExcludeClosedAccounts enabled.

Expected Benefit: Fewer Communicator Advantage API calls when ExcludeClosedAccounts is enabled.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user saw closed accounts due to Core provider API reading account details for closed accounts.

New Behavior: The end user sees information only for accounts that are currently open.

Product: Premier CoO - Sync Transactions

3rd Party Dependency: Fiserv Premier core with Communicator Open interface

Description: Resolved an issue where the core, when reading account holds, resulted in the Alkami Platform deleting the previously downloaded holds for the account.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user's previously downloaded account holds for an account were soft-deleted when the core returned an error on subsequent account hold reads.

New Behavior: The end user's previously downloaded account holds aren't soft-deleted when the core returns an error on subsequent account hold reads.

Product: Spectrum - Update User

3rd Party Dependency: Fiserv Spectrum core

Description: End users can override Member, Share, and Loan Restrictive Flags 11 and 12 when attempting to update a phone number.

Expected Benefit: The end user can update a phone number on a restricted account, such as a closed account.

Activation: Configured by FI, new Spectrum provider setting: UserOvrdRestrictionsOnUpdatePhone
Description: When enabled, the Alkami Platform performs an override (OVRD) on any Member/Share/Loan Restrictive Flag 11 or 12 returned by Spectrum when attempting to update a user's contact information. When disabled, the Alkami Platform doesn't perform an override on these errors.
Format: Boolean
Default: FALSE
Required? No

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end users couldn't update phone number on restricted accounts.

New Behavior: The end users can update phone number on restricted accounts.

Product: upSWOT Business Analytics (optional product)

3rd Party Dependency: upSWOT

Description: The following updates were made to upSWOT's FI Admin Panel (Premium feature): (1) Business Health tab, (2) the Credit Score, Cash Flow Forecast, and Analytics sections changed locations, and (3) the Client Card has enhanced visibility. For Business Analytics, a new search feature allows businesses to search for transactions.

Previous Behavior: New features - upSWOT widget for v5.10.3 to be available with the Alkami release 2024.3.1.

New Behavior: +Improved feature functionality for three Admin panel (Premium) features and introduced two new features, including the client-facing Business Analytics Widget (Standard and Premium)+
# {}Admin Panel (Premium){}: FI Admins can view the Business Health Dashboard in the Client Card on a Business Health tab. The information is read-only, offering a complete view of the Business Health components and corresponding client data. The demo mode is unavailable in the current implementation. The FI Admin can view business information exactly as clients see it.
!image-2024-08-14-13-08-30-529.png|width=737,height=407!
# Admin Panel (Premium): The General tab on the Client card gives FI Admins more visibility and flexibility to work with client information. This includes:
Additional External ID and Created Date fields in the Company Details widget
Improved Bank Accounts widget
New Apps Connected section
Removed Financial Metrics and Business Metrics widgets
Removed Credit Score Boosted and Apps status fields from the Dashboard Usage section
These tabs are no longer available in the Client Card. They are now available in the {}Business Health Dashboard{}.
!image-2024-08-14-13-11-11-060.png|width=945,height=465!
# {}Admin Panel (Premium){}: The General tab on the Client card gives FI Admins more visibility and flexibility to work with client information. This includes:
Additional External ID and Created Date fields in the Company Details widget
Improved Bank Accounts widget
New Apps Connected section
Removed Financial Metrics and Business Metrics widgets
Removed Credit Score Boosted and Apps status fields from the Dashboard Usage section
!image-2024-08-14-13-18-35-722.png|width=877,height=456!
# Business Analytics Widget (Standard & Premium): A new Accounts feature allows business owners to search their account transactions. Each selected account offers a search field and a filter to refine the transactions with the following attributes:
Type of Transaction
Date Period
Amount
This enhancement enables quick transaction search, offering business owners a practical way to manage their account operations.
!image-2024-08-14-13-19-05-136.png|width=768,height=339!

+New+

{}Business Analytics Widget (Standard & Premium){}: The new Accounts Component feature allows business users to analyze their daily business spending on a Spending tab. Business owners can use the date picker and filter to refine their spending review. The Spending feature analyzes expenditures based on data from the user's connected cash or credit card accounts. It breaks them into ten categories: nine primary and one generic (Other), which covers the remaining expenses. End users can drill down into each category to explore the transactions in detail. This enhancement improves the visibility of business expenses for business owners, enabling them to make timely decisions and control their budgets.
!image-2024-08-14-13-23-29-837.png|width=1031,height=453!

Expected Benefit: Continuous improvements to upSWOT's Business Analytics widget and Admin panel enable businesses (and FIs) to have an enhanced view of the business activities, create more accurate business valuations, and disconnect unwanted apps, all in a secure platform.

Activation:

Standard version is automatically available in Staging and Production. Premium version requires a separate purchase. Contact your Client Sales Executive to upgrade to the Premium feature.

{}Standard Version{}: Automatically available in Staging and Production with the release. In FI Admin, the FI can go to Admin > {}Setup{}. Click Packages and then click {}Edit the Package{}. Click the toggle to select the Business Analytics widget to add it to packages. For more information about adding a widget to a package, see the {_}Administration (Admin) Product Guide{_}. To add upSWOT to your navigation menu, in FI Admin, go to Setup > {}Navigation Builder{}. For more information about Navigation Builder, see the {_}Navigation Builder Product Guide{_}. The Standard version only includes Alkami data synced from the FI's core and shows the following sections: {}Forecast Builder{}, Insights, Analytics, and Settings.

{}Premium Version{}: Contact your Client Sales Executive to enable full access for your businesses. This includes the previously listed sections in the Standard version, plus access to over 100 integrated connections, intelligent analytics from those connections, business credit score boosting abilities with insights, and more robust KPIs. FIs can view and act upon this information in a separate, FI-only portal.

Delivery Channel: Desktop, Mobile App

Product: XP2 - Sync User

3rd Party Dependency: Fiserv XP2 core version 2020-2 or newer

Description: The Alkami Platform only supports reading and updating a single email address in the core. For this reason, it uses the end user's primary email address in the core. Alkami resolved an issue where the Alkami platform didn't read any email addresses from the core if the end user didn't have one of their email addresses tagged as a primary. Now, the Alkami platform uses the first email address returned for the end user if the end user doesn't have a primary email address tagged in the core.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user didn't see any email addresses in digital banking if a primary email address wasn't defined in the core.

New Behavior: The end user sees the first email address returned from the core if they don't have an email address tagged as a primary.