Alkami Release Notes - 2024.3

Product: Address Validation - Smarty Streets (optional product)

3rd Party Dependency: Smarty Streets

Description: Alkami has resolved an issue for Address Validation using Smarty Streets that caused addresses with an incorrect state to still show the incorrect state even after it was updated to the correct state.

Expected Benefit: Resolved an Issue.

Activation: Automatically Resolved with the Release.

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, for FIs using Smarty Streets for address validation, If an incorrect state was input for an address, both the incorrect state and correct state were being selected in the state dropdown. The dropdown would display 2 items selected and the end user would need to manually fix this before saving the address.



!Previous Experience_2 items selected.png|thumbnail!

New Behavior: Now, for FIs using Smarty Streets for address validation, if an incorrect state was input, it is corrected with address validation and only shows the correct state. The end user is then able to save the address with the correct state.

!Corrected State.png|thumbnail!

Product: Alkami Digital Account Opening

3rd Party Dependency: N/A

Description: Resolved defect where search engines can discover unavailable promotional products.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile App, Admin

Previous Behavior: Go to your preferred search engine. Search for a promotional product that isn't available to the general public. You can see search results for the product.

New Behavior: Go to your preferred search engine. Search for a promotional product that isn't available to the general public. You won't see search results for the product.

Product: Alkami Digital Account Opening - FIS IBS (RDAO)

3rd Party Dependency: FIS IBS

Description: Fixed an issue where the Transfers API call failed due to a formatting error on the Transfer Amount field. The field value was updated so that commas aren't included.

Expected Benefit: Resolved an issue

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The Transfers API call failed to send when the funding amount was greater than or equal to $1000.

New Behavior: The Transfers API call is sent successfully when the funding amount is greater than or equal to $1000.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Updated the Standard Document Imaging Index File to include customer number, member number, and external ID.

Expected Benefit: Financial Institutions can link the Standard Document Imaging Index File to the customer or member the Standard Document Imaging Index File belongs to based on the customer or member number.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Submit an order. Approve the order. When the Document Imaging vendor receives the order, the file can't be automatically linked to the customer or member.

New Behavior: Submit an order. Approve the order. When the Document Imaging vendor receives the order, the file is automatically linked to the customer or member.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Made Two-factor authentication text message content customizable.

Expected Benefit: Financial Institutions can customize two-factor authentication text message content to align with their marketing strategy.

Activation: Open a JIRA Delivery ticket - this may require a Client Change Request (CCR). Include the new content you wish to include.

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. Enter your phone number. Send a two-factor authentication text message to your phone number. You see the default content.

New Behavior: Start a deposit application. Enter your phone number. Send a two-factor authentication text message to your phone number. You see an updated message if the content is customized.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Updated BSA questions on the Dashboard to respect Checkout configurations.
Show only BSA questions that are configured in Checkout.
The BSA question label uses the title of the page as the label in Dashboard.
Use the same enums configured for dropdowns on Checkout and Dashboard.
All BSA questions are optional in the Edit Action window

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. Fill out the BSA questions. Submit the application. Go to the Order Profile on the {}Dashboard{}. All available BSA questions appear on the {}Application t{}ab and in the Edit Action window. The labels won't match the question titles configured in Checkout.

New Behavior: Start a deposit application. Fill out the BSA questions. Submit the application. Go to the Order Profile on the {}Dashboard{}. Only BSA questions configured in Checkout appear on the {}Application t{}ab and in the Edit Action window. The labels match the question titles configured in Checkout.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Updated showing and hiding fields based on ID Type selection on Identification Checkout pages. When Military ID is selected for {}ID Type{}, ID Number and State of Issue are hidden and Country of Issue is shown. When Passport is selected for {}ID Type{}, Country of Issue is shown.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposits application. On the Identification pages, select Military ID for {}ID Type{}. ID Number and State of Issue are shown. Country of Issue is hidden.

New Behavior: Start a deposits application. On the Identification pages, select Military ID for {}ID Type{}. ID Number and State of Issue are hidden. Country of Issue is shown.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Resolved a defect in the Dashboard where the Documents tab crashed when viewing a core response that wasn't formatted as JSON.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Submit an application. In the Dashboard, go to {}Order Profile{}. Approve the order. Send the order to core. Go to the Documents tab. Click a core response. The Documents tab crashes if the core response isn't in JSON.

New Behavior: Submit an application. In the Dashboard, go to {}Order Profile{}. Approve the order. Send the order to core. Go to the Documents tab. Click a core response. The Documents tab doesn't crash if the core response isn't in JSON.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Added configurability to hide specific add-ons (such as eStatements) from the Add-Ons Store or Checkout page.

Expected Benefit: User experience

Activation: Open a JIRA Delivery ticket - this may require a Client Change Request (CCR). State which add-ons you wish to not display.

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start an application. When selecting add-ons, mandatory add-ons appear with a checkbox selected that can't be cleared.

New Behavior: Start an application. If configured, mandatory add-ons aren't displayed when selecting add-ons.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Resolved defect where applicants on a bad actors list weren't being auto-declined before running identity verification.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Start an application. Enter bad actor information. Submit an application. You aren't auto-declined.

New Behavior: Start an application. Enter bad actor information. Submit an application. You are auto-declined.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Created Checkout page to collect an applicant's previous financial institution.

Expected Benefit: Financial institutions can track the previous financial institution of new applicants.

Activation: Open a JIRA Delivery ticket - this may require a Client Change Request (CCR). State configuration options for "Previous FI" question.

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. The Alkami Platform doesn't ask you questions about your previous financial institution.

New Behavior: Start a deposit application. If configured, the Alkami Platform asks you about your previous financial institution. Log into Dashboard. Click the Order Profile for the submitted application. Click the {}Application t{}ab. You can see the previous FI for the applicant.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Created Checkout pages to collect Bank Secrecy Act (BSA) responses on primary and joint applicant's citizenship status.

Expected Benefit: Financial Institutions (FIs) can collect an applicant's intended account activity to help prevent the account from being used for criminal activities such as money laundering or tax evasion. FIs can view and edit this information on the Dashboard.

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

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. The Alkami Platform doesn't prompt you nor any joint applicants to answer a BSA question about citizenship status (US Citizen, permanent resident, non-resident alien).

New Behavior: Start a deposit application. If configured, the Alkami Platform prompts you and any joint applicants to answer a BSA question about citizenship status (US Citizen, permanent resident, non-resident alien).

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Created Checkout page to collect Bank Secrecy Act (BSA) responses if an applicant owns, operates, or replenishes ATMs.

Expected Benefit: Financial Institutions (FIs) can collect an applicant's intended account activity to help prevent the account from being used for criminal activities such as money laundering and tax evasion. FIs can view and edit this information on the Dashboard.

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

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. The Alkami Platform doesn't prompt you to answer a BSA question if you own, operate, or replenish an ATM.

New Behavior: Start a deposit application. If configured, the Alkami Platform prompts you to answer a BSA question if you own, operate, or replenish an ATM.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: Alkami Digital Account Opening - Instant Account Verification

Description: Resolved defect where the Fund Account Later button displayed over the Yodlee interface to link an external account. Added a fix to ensure the Fund Account Later button doesn't display for Certificate of Deposit applications.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit account application. On the Funding Method page, click {}Instantly Connect an Account{}. The Fund Account Later button appears over the Yodlee interface.

New Behavior: Start a deposit account application. On the Funding Method page, click {}Instantly Connect an Account{}. The Fund Account Later button appears under the Yodlee interface. If the application is for a Certificate of Deposit, the Fund Account Later button doesn't appear.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Resolved a defect where users returning to the DAO Store to access documents saw the original document, not the updated document.

Expected Benefit: Resolved an Issue.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start an application. Add a debit card. Make a selection on the Reg E page. Abandon the application. Return to the DAO Store and log into {}Your Orders{}. Click View on a disclosure. The applicant sees the original document.

New Behavior: Start an application. Add a debit card. Make a selection on the Reg E page. Abandon the application. Return to the DAO Store and login to {}Your Orders{}. Click View on a disclosure. The applicant sees the updated document.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Updated agreements on the Create Account and Product Store Agreements checkout pages so that the checkbox is only shown after the user has viewed the agreements. The color of the agreement title in the agreement boxes was updated to comply with ADA & WCAG.

Expected Benefit: This clarifies that the agreements must be viewed before the user signs them. Updated for compliance with ADA & WCAG.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start an application. On the Create Account page or Product Store Agreements page, a checkbox appears next to the agreement before the end user views and signs the agreement.

New Behavior: Start an application. On the Create Account page or Product Store Agreements page, after the end user views and signs the agreement, a checkbox appears next to the agreement.

Product: Alkami Digital Account Opening - Retail Deposit Account Opening

3rd Party Dependency: N/A

Description: Updated color of the email link in the DAO Store and Checkout footer to ensure sufficient contrast with the background to comply with ADA & WCAG.

Expected Benefit: Compliance with ADA & WCAG.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Go to DAO Store. In the page footer, the email link color won't pass an accessibility test.

New Behavior: Go to DAO Store. In the page footer, the email link color will pass an accessibility test.

Product: Alkami Digital Account Opening - Retail Deposit Opening

3rd Party Dependency: FIS IBS

Description: Alkami is integrated with FIS IBS to create customers and retail accounts on the FIS IBS core.

Expected Benefit: FIs can automatically create customer and retail accounts on the FIS IBS core after an application for a new customer is approved in the Alkami Digital Account Opening Platform.

Activation: This is an optional product. Contact your Client Success Manager to purchase

Delivery Channel: Desktop, Mobile Web

Previous Behavior: No integration with FIS IBS is available to create customer and retail accounts.

New Behavior: Alkami is integrated with FIS IBS to create customer and retail accounts on the FIS IBS core.

Product: Alkami Digital Account Opening - Retail Deposit Opening

3rd Party Dependency: Yodlee - Account Verification

Description: Updated the Yodlee integration from FastLink 3 to FastLink 4.

Expected Benefit: Alkami is migrating all Yodlee instances from FastLink 3 to FastLink 4. This provides end users with an improved user experience, improves configuration options, and maintains support for the Yodlee Account Verification feature.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile Web

Previous Behavior: Retail Deposit Opening applications used FastLink 3 to provide instant account verification.

New Behavior: Retail Deposit Opening applications use FastLink 4 to provide instant account verification.

Product: Alkami Digital Account Opening - Yodlee Verification

3rd Party Dependency: Yodlee Verification

Description: Added a setting to configure the Yodlee user interface by setting the configName parameter.

Expected Benefit: The FI can customize the Digital Account Opening Yodlee Verification interface.

Activation: The setting is available to use on release. Please open a Jira Support ticket to request a change to this setting.

Delivery Channel: Desktop

Previous Behavior: The Yodlee Verification interface in DAO always used the default configuration.

New Behavior: The Yodlee Verification interface in DAO can be configured to a different template. If no configuration name is provided, the default configuration is used.

Product: Alkami Digital Account Opening Platform

3rd Party Dependency: FIS IBS, Fiserv DNA, or Keystone Corelation

Description: In the Alkami Digital Account Opening application, Alkami shows a list of internal accounts that allow transfers out and have a balance greater than $0. The end user can select an internal account to fund the new deposit account to which the end user is applying. If the application is approved, Alkami initiates the funds transfer from the designated funding account to the newly opened deposit account in real-time.

Expected Benefit: End users can fund new accounts from an existing internal account. FIs might see a higher funding rate and a higher conversion rate of applications from existing users.

Activation: Open a JIRA Delivery ticket to enable internal funding. A CCR may be required to implement internal funding for a core that is not currently supported.

Delivery Channel: Desktop, Mobile Web

Previous Behavior: An end user couldn't fund a new account using an existing internal account from the Digital Account Opening application.

New Behavior: An end user sees a list of their internal accounts on the Funding page. The user can select one of these accounts to fund their new account.

Product: Alkami Digital Account Opening Platform

3rd Party Dependency: N/A

Description: Configuration has been added to support temporary user accounts for Joint Applicants who are added to an order. Joint Applicants are given the option to accept or decline being added to an order. Joint Applicants can sign in to DAO, sign agreements, and view disclosures.

Expected Benefit: Mitigates the risk of Joint Applicants being fraudulently added to an order, while providing Joint Applicants access to sign and view agreements.

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

Indicate which functionality you want Joint Applicants to have:
Joint Applicant can view agreements
Joint Applicant can approve or decline being added to an order
Joint Applicant can sign agreements

Delivery Channel: Desktop, Web Responsive

Previous Behavior: Start a deposit application. Add a Joint Applicant. Joint Applicants can't accept or decline the option to be a Joint Applicant on the order, sign in to DAO, sign agreements, and view disclosures.

New Behavior:* Start a deposit application. Add a Joint Applicant. If configured, Joint Applicants can accept or decline the option to be a Joint Applicant on the order, sign in to DAO, sign agreements, and view disclosures.

Product: Alkami Digital Account Opening Platform - Retail Digital Account Opening - FIS IBS

3rd Party Dependency: FIS IBS

Description: Added the ability to fund CD accounts using an internal funds transfer.

Expected Benefit: FIs using FIS IBS can now automatically fund CD accounts using an internal transfer on the IBS core.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: CD accounts funded using an internal account couldn't be automatically funded on the core.

New Behavior: CD accounts can now be funded from an internal account using an internal transfer on the IBS core.

Product: Alkami Digital Banking - Daily Extract Report

Description: The Householding Daily Extract Report is available to FIs using Flux Premium Data or Pro FI. The extract provides the following details:
# Account Extract provides the Business Name, Household ID, Limits, Payment Company(s), Account(s), and Account permissions (and additional fields).
# Limit Extract provides the Business Name, Household ID, Link Type, Payment Company ID, Limit Type, and Limits (and additional data not listed).

Expected Benefit: This extract provides details for householding that aren't available in the Basic Reports.

Activation: To get this:
FIs with Householding that currently have Flux Premium Data or Pro must submit a support request to set up daily delivery of the extract files.
FIs that don't currently use Flux Premium Data or Pro must contact their Client Success Manager.

Delivery Channel: Flux Premium Data or Pro FI

Previous Behavior: Reports are only available through Basic Reports.

New Behavior: FIs receive data extract files with householding details that aren't in the current Basic Reports.

Product: Alkami Digital Banking Platform - Authentication

3rd Party Dependency: N/A

Description: Alkami is adding a new bot mitigation tool, Turnstile, to the Authentication/Login screen to provide an always-on technology to address credential stuffing attacks and other automated attacks against the Digital Banking platform. Turnstile displays an additional visible widget on the login page to help identify real users versus bots.

!image-2024-01-31-17-23-02-129.png|width=288,height=365! !image-2024-07-01-07-25-10-887.png|width=287,height=351!

Expected Benefit: Turnstile provides significantly improved bot and credential stuffing mitigation with a better user experience than a traditional Captcha page. Previously, Alkami would implement a Captcha intercept page during significant credential stuffing attacks; Captcha appeared before login and was unbranded. That generated an undesirable experience for real users and increased support costs and friction for FIs.

With Turnstile, end users land on the normal branded login page and in many cases don't have to interact with the Turnstile widget as it conducts automatic verification when possible. Some end users might need to click a dynamically generated Verify you are human checkbox to complete verification.

Activation: {color:#172b4d}Turnstile is automatically enabled in Production with the 2024.3 release if it hasn't been enabled previously.{color}

Delivery Channel: Desktop and Mobile Web, Mobile App (not on Biometric)

Previous Behavior: The experience was different when Alkami implemented a Captcha intercept page.

No Captcha Scenario:
# The end user visits the login page such as [https://example.com/authentication|http://example.com/authentication].
# The login page displays Username and Password fields.
# The end user enters their credentials in the Username and Password and clicks {}Log in{}.
# The end user is logged into Online Banking.

Captcha Scenario (Activated by Alkami to address elevated automated activity):
# The end user attempts to visit the login page such as [https://example.com/authentication].
# The end user is directed to a Captcha page without FI Branding.
# The end user must pass a dynamic Captcha challenge.
# The end user is directed to the login page with Username and Password fields.
# The end user enters their credentials in the Username and Password fields and clicks {}Log in{}.
# The end user is logged into Online Banking.

New Behavior:

The experience is different for FIs with Tethered Login.

Authentication Page Scenario:
# The end user visits the login page such as [https://example.com/authentication].
# The login page displays the Username and Password fields as well as the Turnstile widget. The Turnstile widget validates the end user, either automatically or requiring end user interaction.
The Turnstile widget autovalidates the user:
Turnstile displays a _Verifying_ message.
!image-2024-01-31-17-29-57-143.png!
After verification is complete, Turnstile displays a _Success_ message.
!image-2024-01-31-17-30-19-224.png!
Or the Turnstile widget requires interaction to validate the end user. This mode is automatically enabled for an individual end user based on risk signals of the end user and their connection.
Turnstile displays a Verify you are human checkbox.
!image-2024-01-31-17-31-29-937.png!
After the end user selects the checkbox, Turnstile displays a _Success_ message.
!image-2024-01-31-17-31-49-852.png!
# After Turnstile confirms successful verification, the end user can log in as normal.



Tethered Login Scenario:

If your FI supports Tethered Login, where the authentication credentials are collected on a public marketing site and posted to the Alkami Online Banking Platform, the end user experience is as follows:
# Visit your FI's public homepage such as [https://alkamiexample.com|https://alphafinancial.com/].
# Find the login Username and Password fields and enter your authentication credentials.
!image-2024-01-31-20-26-23-140.png|width=195,height=201!
# You're redirected to an Authentication page to process the login.
# The page displays Turnstile.
!image-2024-01-31-17-29-57-143.png!
# After authentication is complete, Turnstile displays a _Redirecting_ message until online banking opens.
!image-2024-07-01-07-26-45-701.png|width=330,height=131!
# The online banking platform displays the Dashboard or Accounts widget.



Validation Guidance:

Given that this update makes a change to the user experience on the login page, Alkami highly recommends that FIs conduct specific validation of this feature in Production when you receive the 2024.3 release.

In the Production environment, confirm the following:
# The Turnstile widget appears on the desktop Login page as expected.
# End users receive a _Success_ message and the Log in button is enabled.
# End users can log in with authentication and access the Dashboard or Accounts widget as expected.
# Tethered Login (if configured at your FI) works as expected. With Tethered Login, end users see Turnstile on the transition page as authentication processes.
# An end user sees no change in the Mobile BioMetric login experience.

Product: Alkami Digital Banking Platform - Business ACH and Business Wires

3rd Party Dependency: None

Description: The cutoff time for Business ACH and Business Wires has been added to the pending authorization alerts sent to business users.

Expected Benefit: Displaying the cutoff time in the pending authorization alert clarifies the FI's cutoff time for the business user.

Activation: Automatically Enabled with the Release

Delivery Channel: Desktop, Mobile App, Admin

Previous Behavior: The pending authorization alert didn't include the cutoff time for Business ACH and Business Wires.

New Behavior: The pending authorization alerts sent to business users include the cutoff time for Business ACH and Business Wires.

Product: Alkami Digital Banking Platform - Business Wires

3rd Party Dependency: Payments Exchange: Fedwire

Description: New encryption method implemented for authentication as required by Fiserv.

Expected Benefit: Fedwire announced a required change to the encryption method used for authentication within the API integration between Alkami and Payments Exchange.

Activation: {color:var(--ds-text, #172b4d)}Automatically Resolved with the Release {color}{color:var(--ds-text, #172b4d)}This is an optional product. Contact your Client Success Manager to purchase{color}

Delivery Channel: Desktop, Mobile App

Previous Behavior: Payments Exchange used the CBC (Cipher Block Chaining) encryption method for authentication.

New Behavior: Payments Exchange requires a transition to the GCM (Galois/Counter Mode) encryption method for authentication, with an implementation deadline of October 1, 2024.

Product: Alkami Digital Banking Platform - Card Management

3rd Party Dependency: Debit or In-House credit cards on the JHA Silverlake core

Description: This enhancement adds the ability to activate Debit and In-House Credit cards at the JHA Silverlake core through jXchange.

Expected Benefit: FIs can expect an increase in activations of credit and debit cards, as well as digital engagement. End users can self-service card activation within the digital channel without having to call the call center.

Activation: This is an optional product. Contact your Client Success Manager to purchase.

Delivery Channel: Desktop, Mobile App

Product: Alkami Digital Banking Platform - Card Management

3rd Party Dependency: PSCU Ondot Alerts and Controls

Description: Alkami's integration to PSCU Ondot Alerts and Controls within Card Management expands to include Regional Alerts and Controls.

Expected Benefit: This is expected to allow cardholders to define regions used to control transactions and trigger transaction alerts. This capability complements our existing PSCU Ondot Alerts and Controls capabilities.

Activation: This is an optional product. Contact your Client Success Manager to purchase.

Delivery Channel: Desktop, Mobile App

Product: Alkami Digital Banking Platform - Card Management

3rd Party Dependency: JHA Silverlake (In-House Credit/Debit)

Description: Alkami now supports the ability for end users to report a card as lost, stolen, or damaged to the JHA Silverlake core for In-House Credit and Debit. Optionally, when reporting a card as lost or stolen or damaged, the FI can let the end user decide if they would like a new replacement card. If configured, the end user has the option to accept or decline a replacement card.

Expected Benefit: The ability for an end user to report a card as lost or stolen or damaged from within the Alkami Digital Banking Platform saves the end user time and reduces strain on FI staff that would have previously assisted those users. Additionally, the ability to offer optional card replacement could be a significant cost savings for the issuer.

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

Delivery Channel: Desktop, Mobile App

Product: Alkami Digital Banking Platform - Card Management Premium

3rd Party Dependency: Tokenizable Mastercard branded cards

Description: This feature allows Mastercards that appear in Card Management to be push-provisioned to Apple Pay and Google Pay.

Expected Benefit: This is expected to reduce friction in getting cards into end users' mobile wallets and encourage use of the card.

Activation: This is an optional product. Contact your Client Success Manager to purchase.

Delivery Channel: Mobile App

Product: Alkami Digital Banking Platform - CD Maturity Integration

3rd Party Dependency: A financial institution must be on the Fiserv DNA CoreAPI platform.

Description: Alkami has expanded its integration with the Fiserv DNA CoreAPI platform to support allowing users to designate what should happen with their Certificate of Deposit (CD) accounts upon maturity. End users can opt to have the CD renew using its existing terms and rate or they can have the entire balance transferred to one of their accounts within the financial institution (FI).

Expected Benefit: In the current interest rate environment, FIs are promoting CDs to their end users as a way of earning more interest. For the FI, it also means locking in more money on-deposit. However, managing the CDs when they mature can be a manual and time-consuming process. By enabling end users to self-service the disposition of their CDs upon maturity, FIs can reduce the time spent on this process. This should also appeal to end users who prefer self-service options through the digital channel.

Activation: Open a JIRA Delivery ticket - This requires a Client Change Request (CCR).

Delivery Channel: Desktop and Mobile App

Previous Behavior: End users on the Fiserv DNA CoreAPI platform could see all the details about their CD accounts in digital banking. However, there was no way for them to provide instructions on how the CDs should be handled upon maturity. The FI used manual processes to assist with CD account management.

New Behavior: End users on the Fiserv DNA CoreAPI platform can select to have their CDs automatically renew or have the entire balance of the CD transferred to another internal account at the FI upon maturity. This is expected to reduce the work effort required of the FI for managing these accounts.

Product: Alkami Digital Banking Platform - Crypto

3rd Party Dependency: NYDIG

Description: The crypto widget is no longer available.

Expected Benefit: On July 31, 2023 crypto enrollments and buys were disabled and all crypto was liquidated on September 29, 2023. With the 2024.3 release, the Crypto widget will no longer be available. FIs can contact NYDIG directly to obtain tax documents.

Activation: Automatically deprecated with the Release

Delivery Channel: Mobile App

Previous Behavior: Previously, the Crypto widget was available and tax documents were accessible by the end user.

New Behavior: The Crypto widget is not available, however, FIs can obtain tax documents directly from NYDIG.

Product: Alkami Digital Banking Platform - Extract Management - Transfer extract

3rd Party Dependency: N/A

Description: Alkami identified an issue with the Transfer extract released on July 18, 2024. The primary identity column ({}transfer_id{}) was reporting the wrong identifier. This has been corrected. The data type is still of BIGINT type{}.{} For FIs that are already consuming data from the Transfer extract, Alkami recommends purging it from your lake or warehouse and then backfilling. To get a one-time backfill, in the FI Admin go to {}Data > Extract{}, click on the Filter button next to the Transfer extract (#1), leave the Process Date time (in UTC), change the Process Date to 7/18 (#2), set Time Range to Month (#3), and click Run Now (#4). This will generate an extract that can be downloaded to refill the FI's data lake or warehouse. Any Transfer extracts generated 8/13 or beyond will have the correct transfer_id.

!RELNT-3269.png|thumbnail!

Expected Benefit: Resolved a bug.

Activation: Automatically Enabled/Resolved as of 8/12

Delivery Channel: Admin

Previous Behavior: In FI Admin, go to Data > Transfer and the extract reports the transfer_id as the identifier associated with the record in the Alkami Platform database.

New Behavior: In FI Admin, go to Data > Transfer and the extract reports the transfer_id as the identifier associated with the record in the Alkami Platform database.

Product: Alkami Digital Banking Platform - FI Admin

3rd Party Dependency: N/A

Description: Updated FI Admin Staff permissions so only business users with the Modify Users - Elevated permission can update the {}Business Tax ID{}.

Expected Benefit: Resolved an Issue

Activation: Automatically Resolved with the Release

Delivery Channel: Desktop, Admin

Previous Behavior: Business users without the Modify Users - Elevated permission can select Support > Members (or {}Customers{}), select any Master User, go to their {}Business Information{}, and update and modify the {}Business Tax ID{}.

New Behavior: Business users that don't have the Modify Users - Elevated permission can't modify the {}Business Tax ID{}. Only users with the Modify Users - Elevated permission can do so.

Product: Alkami Digital Banking Platform - FI Admin

Description: This new feature enables FI Admin users to assign package or business banking limits set at the business or master user to all sub users under the business profile. If the sub user limits are set to the max limit for the business, sub user payment and dual authorization limits update to match the business limit. Dual authorization limits aren't updated for sub users with dual authorization limits set under the business max limit; only payment limits are updated.

Expected Benefit: For FIs that manage sub users, this feature reduces the number of steps the FI Admin user must take to update business sub user limits.

Activation: Open a JIRA Delivery ticket to turn on the feature flag.

Delivery Channel: Desktop

Previous Behavior: When an FI Admin user updates the master user's payment limits, the FI Admin user must select View As User (Full Access) for the master user. After the FI Admin is logged in, they click {}Business Admin{}, {}Users{}, select a user to be updated, click the Payment Permissions tab, click Manage Limit for each payment type limit that must be updated, and save the changes. The FI Admin user repeats the process for each sub user.

New Behavior: An FI Admin user views a master user, scrolls to {}Features and Access{}, clicks Change in the Limits section, and selects Package or Business Banking limits. If the FI Admin user selects Package Limits, select the Update all sub user limits check box and click {}Save{}. All sub user limits are updated to match the package limits. If the FI Admin user selects or updates Business Banking Limits, they can update any limits that must be updated, select the Update all sub user limits check box, and click {}Save{}. All sub user limits are updated to match those displayed on the Limits page.

Product: Alkami Digital Banking Platform - FI Admin

Description: Enhanced the FI Admin Accounts tab (go to {}Support > Member or Customer > User > Accounts{}) to enable FI Admin users who can Manage Households to delete payment companies directly from the Accounts Tab. Messaging was also added when removing a single householded account and managing a household.

Expected Benefit: This enhancement reduces the previously needed steps to manage accounts and payment companies.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: FI Admin users go to Support > Members or {}Customers{}. They perform a search and select a Master User, click Accounts, and click {}Manage Households{}. Then, they enter the TIN for the Household to delete. Next, they search and clear the selected accounts, review their changes, and save them. The accounts were removed, but the payment company remained.

New Behavior: FI Admin users go to Support > Members or {}Customers{}. They perform a search, select a Master User, and click {}Accounts{}. A trash can icon appears next to the entity for the household. Click the trash can icon, confirm the deletion, or cancel. When deleting a householded account, click Remove and a message to delete the payment company or keep it appears if no other accounts are associated with the company.

Product: Alkami Digital Banking Platform - FI Admin - Support

3rd Party Dependency: N/A

Description: The existing Users Recent Activity widget in Admin>Support>User is redesigned to provide a single location for FI Customer Support and Fraud Analysts to see real-time chronological events that end users perform on the platform.

Expected Benefit: Alkami developed the new User Recent Activity widget to solve the problem of FIs not having a single location that provided evidence of all end user's changes on the Alkami Platform. FIs need proof of all end users' _changes_ within the platform, so they can reconcile back office systems, research suspicious behaviors, support end users, and respond to legal inquiries. Without this information they're not able to run daily operations. A single location to view enduser audit data allows FIs to complete critical operations in timely and efficient manner and allows to them to bypass navigating to multiple reports to resolve customer questions and issues.

Activation: Automatically enabled with the 2024.3 release

Delivery Channel: Admin

Previous Behavior: The existing Recent Activity widget in Admin>Support>Users didn't provide real-time chronological events taken by an end user on the Alkami Platform. The existing widget provided an end user's recent activity for the past seven days and only provided a subset of all actions taken.

New Behavior: The updated User Recent Activity widget in Admin>Support>Users now provides FI Customer Support and Fraud Analysts a single location to see real-time chronological events taken by an end user on the Alkami Platform. The updated widget displays the last 90 days of activity for a given end user. The widget displays the following data points:
Date Time Activity (Action) Occurred
Initiated By (Admin or User)
Activity (Action)
Login
Transfers
Audit/Security
Summary
Status
Description
From Account
To Account
Amount
Session ID
* IP Address



!User Recent Activity1.png|thumbnail!

!User Recent Activity2.png|thumbnail!

!User Recent Activity3.png|thumbnail!

Product: Alkami Digital Banking Platform - Limit Management

Description: Alkami allows a permissioned business user to request a Business ACH or Business Wire transaction limit increase when a submitted transaction would otherwise be blocked due to insufficient transaction limits, established by the FI. If the business user requests a limit increase, the submitted transaction moves to an FI review status which requires a limit increase prior to continuing the standard submission process. Business master users can grant permission to sub users, allowing them to also request a limit increase on behalf of the business. Business limit increase requests trigger notifications to the requesting user and the business master user. All business limit increase requests are audited by the Alkami Platform and are available to the FI in standard reports.

Expected Benefit: Impress your auditors with automated process management and tightened control over business limits while providing a seamless experience for large businesses requesting limit increases.

Activation: Configured by FI. This product is self-serve where the FI must use the FI Admin to enter values such as:
FI admin Staff Permissions (go to Setup > Staff and click Admin Roles).
Add one or more Limit Management feature flags to Business Packages. To do this, you must add the following:
For Business ACH
ACH Collections Over Limit Request
ACH Payments Over Limit Request
For Business Wires
Wires Over Limit Request
Configure the {}Message Center Queue{}.
Alkami changes the SLA timer
Alkami sets whether you want Expedited for the SLA time or both Expedited and Standard.

Optional configuration:
Billing
Site Text

Delivery Channel: Desktop, Mobile App, Admin

Current Behavior: Currently, when a master user or sub user tries to submit an ACH or Wire over their current limit, the transaction is rejected. The business users must call the FI and request an increased limit.

New Behavior: Permissioned business users can request an increase to their limits when submitting a Business ACH or Business Wire.

Product: Alkami Digital Banking Platform - Memo Fields for Transactions and Remote Deposit Capture

3rd Party Dependency: N/A

Description: Alkami reduced the available special characters that end users can enter in the {{Memo}} fields for Transactions and Remote Deposit Capture (RDC).

Expected Benefit: Resolved an issue.

Activation: Automatically resolved with Mobile Release 4014.0.0.

Delivery Channel: Mobile App

Previous Behavior: End users had more options of special characters they could enter in the {{Memo}} fields for Transactions and Remote Deposit Capture.

New Behavior: End users have fewer options of special characters in the {{Memo}} fields for Transactions and RDC. They can enter only the following characters:

|&|Ampersand|
|@ |At |
| ,|Comma|
|$|Dollar sign |
|"|Double quotation mark |
|!|Exclamation point |
|-|Hyphen |
|%|Percent |
| .|Period|
|#|Pound |
|?|Question mark |
|'|Single quotation mark|
|<>|Space|
|_|Underscore |

Product: Alkami Digital Banking Platform - Transaction Limit Management, Business ACH

3rd Party Dependency: None

Description: When Transaction Limit Management isn't enabled globally for the FI but it's overridden as enabled at the package or business levels, the override settings are ignored and a business can't submit a limit increase request.

Expected Benefit: Resolved an Issue

Activation: Automatically Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Businesses can't submit a limit increase request due to the override settings being ignored.

New Behavior: The override settings to enable a package or business-level access to Transaction Limit Management are respected.

Product: Alkami Digital Banking Platform - Transfers

Description: This update enhances the external transfer limits by breaking out the limit configuration to be specific to each transfer method. For example, RTP, FedNow, Debit Cards, and ACH.

Expected Benefit: FIs can closely control the limits associated with external transfers by allowing for a more granular level of configuration.
Note, if a FI does NOT currently have split limits configured, this change _will_ _not enable split limits_

Activation:
This change will automatically enable this additional limit configuration capability
FI's must configure their limits as desired within Admin.
RTP, FedNow, and Debit Cards are add-on products, to purchase these products, contact your Client Success Manager.
If your FI does not have RTP, FedNow, or Debit Card transfers enabled, then this change is not currently applicable to your FI.

Delivery Channel: Admin, Desktop, Mobile App

Previous Behavior: Previously, External Transfers were combined under a single category.

With Split Limits enabled:
Admin UI:
!image-2024-06-25-17-33-39-909.png|width=351,height=192!
End user UI: Make a Transfer Limits side sheet

!image-2024-06-25-17-47-44-656.png|width=315,height=186!

Without Split Limits enabled:
Admin UI

!image-2024-06-25-17-34-11-143.png|width=322,height=138!
End user UI: Make a Transfer Limit side sheet

!image-2024-06-25-17-52-57-380.png|width=328,height=192!

New Behavior: Now, FI's can configure limits at the below granularity:

With _Split Limits_ enabled:
Admin UI

!image-2024-06-25-17-36-28-177.png|width=277,height=225!

End User UI: Make a Transfer Limit side sheet

!image-2024-06-25-18-00-19-409.png|width=246,height=231!



Without _Split Limits_ enabled:
Admin UI:

!image-2024-06-25-17-37-03-931.png|width=221,height=173!
End user: Make a Transfer Limit side sheet

!image-2024-06-25-18-01-23-531.png|width=207,height=192!

Product: Alkami Digital Banking Platform - Transfers

Description: Resolved an issue that caused a continuous loading spinner to display on the Multi-Account Transfer result screen even when the transfer submission was successful.

Expected Benefit: The outcome of the transfer submission status will display as intended.

Activation: This change will be automatically enabled with this release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, when submitting a multi-account transfer, the result screen would sometimes result in a continuous loading spinner:

!image-2024-06-26-06-01-06-121.png|width=329,height=130!

New Behavior: Now, the outcome of the transfer submission displays as intended:



!image-2024-06-26-06-02-52-932.png|width=223,height=428!

Product: Alkami Digital Banking Platform - Transfers

Description: Originally in RELNT-2068, Alkami introduced the ability for FIs to populate the Loan Payment Type used in the Retail ACH transfer within the discretionary data field in the NACHA and InFiles for the PPD SEC Code only, now this functionality has been expanded to include the additional SEC codes of {}WEB{}, {}CIE{}, and {}CCD{}.

Expected Benefit: This change allows for the loan payment type used in a given Retail ACH transfer to be passed in the Discretionary data field in the Retail ACH Nacha and Infiles.
Nacha file location for reference:
Entry Detail 6 record
Field 9
Length 2
Position 77-78

Activation: To activate this feature, submit a Jira Delivery ticket for activation.

The following is the configuration details for reference:
Set the NACHA ACH Output Provider Setting _ShowLoanPaymentTypeInDiscretionaryData_ = True
Navigation in Admin for reference: Setup > Integration Settings > Providers > _ACHOutputFile_ > NACHA ACH Output Provider > _ShowLoanPaymentTypeInDiscretionaryData_



Delivery Channel: Admin

Previous Behavior: Previously, the discretionary data field was not passing the loan payment type information.

New Behavior: Now, when the _ShowLoanPaymentTypeInDiscretionaryData_ setting is chosen to be activated and the SEC (Standard Entry Class) code for the transaction is either PPD, WEB, CIE, CCD, Alkami will add the Loan Payment Type information to the Discretionary Data field in the NACHA and Infile. The first character of the code corresponds to the Loan Payment Type. The second character of the code indicates if there was an additional principle, escrow, or both.
Nacha file location for reference:
Entry Detail 6 record
Field 9
Length 2
Position 77-78

For example, based on the tables below, if a loan payment has a Loan Payment Type of Standard and there is an additional principal added, the inserted code would be _31._
The scope of this feature is to populate the below codes into the discretionary data field in the NACHA file.
* Each FI will be responsible for using this discretionary data to process the payment correctly on their core.



!image-2024-06-26-06-37-21-251.png!

Product: Alkami Digital Banking Platform - Transfers

Description: Newly added external accounts are pre-populated on the Make a Transfer screen.

Expected Benefit: This allows for greater synergy between the Account Linking and Transfer widgets. Adding an account and transferring to and from that account is now streamlined.

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

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, there was no pre-population logic occurring when the end user added or linked an external account.

New Behavior: Now, after an end user adds an external account and navigates back to the Make a Transfer page, the newly added account is pre-populated on the page. Additionally, the button label on the Account Linking confirmation screen displays as Done.

Product: Alkami Digital Banking Platform - Transfers

Description: Updated the _DegreesOfParallelismForAutoTransactions_ Retail ACH value from one to two.

Expected Benefit: As part of an FIs daily retail ACH Admin processing, if the FI has auto-debit enabled, at the time of the Approve Batch step internal debits are processed against the FI's core. With this configuration update, the amount of time it takes for these auto-debits to process is greatly reduced by sending two debits to the core at a time instead of one.

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

Delivery Channel: Admin

Previous Behavior: Previously, auto-debits would be sent to the core one at a time for processing.

New Behavior: Now, the system sends two debits at a time to the core for processing which will reduce the amount of time the auto-debit process takes to complete.

Product: Alkami Digital Banking Platform - Transfers

Description: If an end user doesn't have External Transfers access, they will no longer see their previously added external accounts in the Settings > Accounts navigation.

Expected Benefit: Resolved an issue.

Activation: This change will be automatically enabled with this release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Previously, end users were able to view and edit their previously added external accounts in the Settings > Accounts navigation, even after the FI Admin had removed their external transfer access:

!image-2024-05-21-11-47-04-320.png|width=807,height=322!

New Behavior: Now, once an FI Admin removes an end users external transfers access, the end uer will no longer be able to view their accounts in the Settings > Accounts navigation:

!image-2024-05-21-11-48-08-171.png|width=985,height=321!

Product: Base2000 - Framework

3rd Party Dependency: FIS Base2000 credit card processor

Description: The Alkami Platform honors the Time To Live (TTL) value when using Domain Name System (DNS) lookup responses.

Expected Benefit: The Alkami Platform doesn't use expired DNS TTL values, which can lead to communication failures with Base2000.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The Alkami Platform doesn't honor the DNS TTL value, which can lead to communication failures with Base2000.

New Behavior: The Alkami Platform performs a new DNS lookup when the current DNS TTL value expires.

Product: Basic Reports > Business Banking – Scheduled Transfers Report

3rd Party Dependency: N/A

Description: The Business Name filter in the Basic Reports > Business Banking - Scheduled Transfers Report is less restrictive.

Expected Benefit: End users can more easily filter on the Scheduled Transfers Report to show specific Business Name records.

Activation: Automatically enabled with the release

Delivery Channel: Admin

Previous Behavior: Users could only filter business records on the Scheduled Transfers Report when they filtered for the exact match of the {}Business Name{}.

New Behavior: Users can filter to find business records on the Scheduled Transfers Report without having the exact match for the {}Business Name{}.

Product: CD Maturity

3rd Party Dependency: N/A

Description: Resolved an issue where the Alkami Platform doesn't properly persist the maturity and dividend transfer accounts for CDs.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Maturity transfer accounts aren't properly stored in the Alkami Platform.

New Behavior: Maturity transfer accounts are properly stored in the Alkami Platform so they can be displayed to the CD maturity end user.

Product: Chat - Glia (optional product)

3rd Party Dependency: Glia

Description: Support added for Glia DirectID Authentication. This provides an authenticated chat experience for end user's information to securely pass to Glia. This information helps the Glia operator (agent) be confident with whom they are interacting. Authenticated chat sessions are indicated to FI agents using Glia.

Expected Benefit: Increase confidence for service agents with whom they're engaging, so that additional verification questions may not be required. This saves the service agent time and ability to focus on assisting the end user. DirectID is the gateway for future enhancements such as more personalized Glia Virtual Assistant (GVA) responses including balance inquiries, transaction history, and direct deposit information.

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

Delivery Channel: Desktop, Mobile App

Previous Behavior: DirectID authentication was not previously available and the end user would not show as authenticated with Glia Hub.

!Glia Hub_No DirectID.png|thumbnail!

New Behavior: When enabled and configured, Glia DirectID Authentication will confirm that the engagement is authenticated as indicated in Glia Hub with the Visitor Authenticated and green check mark icon.

!Glia Hub_With DirectID Auth.png|thumbnail!

Product: Chat - Glia (optional product)

3rd Party Dependency: Glia

Description: Alkami has resolved an issue with how the post-engagement survey was appearing to end users using the Glia integration for Desktop and Mobile Web.

Expected Benefit: Resolved an Issue

Activation: Automatically Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Previously, after an engagement is complete, the post-engagement survey would appear to the end user with incorrect formatting for some questions and responses.

!Glia Survey Formatting Issues.png|thumbnail!



New Behavior: Now, after an engagement is complete, the post-engagement survey appears with questions and responses that are formatted as expected.

!Glia Survey Correct Format.png|thumbnail!

Product: Chat - Glia (optional product)

3rd Party Dependency: Glia

Description: Updated the integration with Glia in the mobile apps to introduce additional functionality that increases parity with the Glia experience on Desktop.

Optional feature: Live Observation on mobile allows operators to monitor a visitor's actions on your website or mobile app to ensure better support. This can be configured in the Glia Hub to notify the end user that there is an ongoing live observation.

Optional dialog box: The User Consent & Disclosure appears before the start of engagements and can be customized to include disclaimers and links to the Terms & Conditions and Privacy Policies.

Resolved an issue with the Glia Virtual Assistant (GVA) deep links on iOS not automatically minimizing the chat experience when navigating an end user to another page.

Expected Benefit:
Live Observation on mobile improves the agent experience and allows agents to quickly assist end users as they navigate the mobile application by being able to view the end user's mobile app screen.
User Consent & Disclosure is a dialog box that appears before the start of engagements. Its primary purpose is to inform the visitor about the data that the app collects and uses during engagements.
Resolved an issue for GVA Deep Linking on iOS where the chat engagement wasn't being automatically minimized when navigated to another page within the app through deep links.

Activation: Configured by FI. This is an optional product. Contact your Client Success Manager to purchase.

With this version of the mobile application and later, the following functionality requires configuration within the Glia Hub (Glia Admin) by the FI to utilize this functionality.

+Live Observation on Mobile+

In {}Glia Hub > Admin Console > Advanced > Privacy & Security > Privacy & Security{}, you can set the following settings that determine the visitor's experience during engagements with live observation on mobile:
Live Observation on Mobile - Enables or disables live observation for native mobile applications.
Show Indicator - Determines whether the visitor will be notified of live observation at the beginning of the engagement.
Available only if Live Observation on Mobile is on.

!Glia Mobile_Live Observation on Mobile_Glia Hub.png|thumbnail!



+User Consent & Disclosure+

To show the User Consent & Disclosures confirmation dialog before engagements, make the Request Confirmation for Mobile Engagements toggle in Glia Hub > Admin Console > Advanced > Privacy & Security > Privacy & Security set to {}On{}.

!Glia Mobile User Consent and Disclaimers_Request Confirmation for Mobile Engagements (1).png|width=263,height=126!

The confirmation dialog can only be turned on or off for all engagements at once, it cannot be applied selectively to specific media types.

You can customize the title and message of the confirmation dialog using Glia custom locales.

In addition, the confirmation dialog allows for the use of link-outs. Link-out is a hyperlink embedded in the confirmation dialog. When selected, it directs the visitor to an external webpage or document containing more detailed information related to the dialog's content. For example, you can provide link-outs leading to your app's Privacy Policy and {}Terms and Conditions{}.

By default, the link values are null and will not be included in the dialog. However, you can set your values with custom locales.

To modify the text and set link-out values, follow these steps:
# Go to {}Glia Hub > Admin Console > Settings > Locales{}.
# Select the custom locale from the list of existing options or create a new one.
# Make sure that the Show Native-Mobile Strings toggle is on and type the key name of the string you would like to change:
## engagement.confirm.title
## engagement.confirm.message
## engagement.confirm.link1.text
## engagement.confirm.link1.url
## engagement.confirm.link2.text
## engagement.confirm.link2.url
## engagement.confirm.link1.accessibility.label
## engagement.confirm.link2.accessibility.label
# Provide the values and save the result.

!Glia Custom Locales_User Consent and Disclosures Confirmation.png|width=315,height=149!

Delivery Channel: Mobile App

Previous Behavior: Previously, Live Observation on Mobile and User Consent & Disclosures were not a supported functionality for Glia on Mobile.

New Behavior:

+Live Observation on Mobile+

When Live Observation on Mobile is enabled (within Glia Hub), the agent can view the end user's screen within the mobile application during an engagement.

!Live Observation on Mobile_Glia.png|thumbnail!



+User Consent & Disclosure+

When the confirmation dialog is enabled, the visitor will receive the confirmation dialog about collecting the data before the start of every engagement.
If the visitor is willing to proceed and selects {}Allow{}, the engagement request is created, and the call begins as soon as the operator accepts it.
If the visitor selects {}Cancel{*}, the engagement request is not created, and no engagement begins.

Default User Consent & Disclosure Confirmation Dialog

!User Consent and Disclaimer_default.png|width=137,height=297!

User Consent & Disclosure Confirmation Dialog modified using Glia Custom Locales - includes links to T&Cs and/or Privacy Policies (based on what is configured by FI within Glia).

!User Consent and Disclaimer_modifed with custom locales.png|width=147,height=319!

Product: Customer Insights & Marketing Automation

3rd Party Dependency: N/A

Description: The Clicks report includes the {}First Impression Date{}.

Expected Benefit: Seeing the first impression date on the Clicks report helps the FI understand when the campaign started serving impressions to their account holder.

Activation: Automatically enabled with the release

Delivery Channel: Desktop

Previous Behavior: FIs couldn't see the First Impression Date on the Clicks report.

New Behavior: FIs can see the First Impression Date populated on the Clicks report.

Product: Customer Insights & Marketing Automation

3rd Party Dependency: N/A

Description: The {}Influences Report{}, {}Impressions Report{}, and Impression Efficiency Report within the Customer Insights and Marketing Automation platform are enhanced to provide Marketing Admin users the ability to:
Export report data to CSV files.
Filter the report by the campaign goals.
Expand and collapse rows to provide more or less report details.
View enhanced report visualizations, providing time series charts (days, weeks, months or quarters) and the ability for the user to select the data points that are charted.

Expected Benefit: FIs can more easily customize their report view, and easily extract report data to analyze outside of the platform for use in their own reporting tools and share insights with peers.

Activation: Automatically enabled with the release

Delivery Channel: Desktop

Previous Behavior: N/A

New Behavior: FIs can export report data to CSV files, select time series visualizations (days, weeks, months, or quarters), select the data points to be charted, filter by campaign goals, and expand and collapse report rows.

Product: Customer Insights & Marketing Automation

3rd Party Dependency: Salesforce CRM License (or FSC) and Salesforce Marketing Cloud

Description: The Customer Insights & Marketing Automation platform provides a seamless, turnkey integration with Salesforce Marketing Cloud that enables FIs to securely sync KLI-targeted audience lists to Salesforce CRM. With these audiences, FIs can send emails in Salesforce Marketing Cloud and track ROI of account holder engagements or use these audiences for account holder engagements managed via Salesforce CRM.

Expected Benefit: When financial marketers build their account holder engagement campaigns, they might struggle to source insights to personalize their outreach. Account holder data is typically siloed and requires multiple resources to aggregate and secure the data, delaying marketers’ campaign execution. Marketers can solve these challenges with a unique set of insights to deliver personalized email messages. With the integration of Alkami Customer Insights & Marketing Automation and Salesforce Marketing Cloud, FIs can send targeted, relevant emails in an integrated delivery solution and keeping account holders’ data secure. This integration empowers financial marketers to leverage real-time account holder insights for engagement campaigns, such as:
Digital onboarding
Drip campaigns
Cross sell
Product and service adoption
Financial education and wellness

Activation: This is an optional product. Contact your Client Success Manager to purchase.

Delivery Channel: Desktop

Previous Behavior: N/A

New Behavior:* The Customer Insights & Marketing Automation platform provides a seamless, turnkey integration with Salesforce Marketing Cloud and Salesforce CRM.

Product: Data eXchange - Transfer

3rd Party Dependency: PSCU Data eXchange credit card processor

Description: The TaskCanceledException causes the Alkami Platform to query Data eXchange to determine if the transfer was successful or not.

Expected Benefit: Resolved an Issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: TaskCanceledException errors on right-time payment or cash advance requests to Data eXchange resulted in an error message for the end user. The end user sometimes submitted the transfer request again, resulting in duplicates due to original transfers being submitted successfully.

New Behavior: TaskCanceledException errors on right-time payment or cash advance request to Data eXchange causes the platform to query Data eXchange to determine if the transfer submission was successful and display a success message to the end user. If the Data eXchange side of the transfer was not successful, the platform displays a message to the end user that the transfer was successful but might not be reflected until the next business day. Data eXchange is notified of the transfer during the nightly processing of the tap tran file from the primary core.

Product: Digital Account Opening - Retail Digital Account Opening - Fiserv DNA

3rd Party Dependency: Fiserv DNA

Description: When creating a new account on the core, Alkami sets the isValid field to true for all users. This indicates that a person's identity has been verified.

Expected Benefit: FIs no longer need to manually change the Verified flag to true for accounts opened by the Alkami Digital Account Opening platform.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop, Mobile Web

Previous Behavior: The isValid field wasn't set, which resulted in the field defaulting to false on the Fiserv DNA core.

New Behavior: The isValid field is set to true in Fiserv DNA when new accounts are opened on the core.

Product: Digital Account Opening - Retail Digital Account Opening - Fiserv DNA

3rd Party Dependency: Fiserv DNA

Description: When creating a new account in Fiserv DNA, you can configure the field FundSourceCD for internal and external funding sources. For example, if the funding source is external, the FundSourceCD value passed is NEWC, and if the funding source is internal, the value passed is NEWP.

Expected Benefit: FIs can use the field FundSourceCD to track whether a newly opened account was funded using existing funds internal to the FI or with new funds external to the FI.

Activation: Open a JIRA Support ticket.

Delivery Channel: Desktop

Previous Behavior: The value of the field FundSourceCD was hardcoded to NEWC.

New Behavior: The value of the field FundSourceCD can be configured by funding source.

Product: Digital Account Opening - Retail Digital Account Opening - Fiserv DNA

3rd Party Dependency: Fiserv DNA

Description: Alkami's Retail Digital Account Opening core integration with Fiserv DNA can be configured with a custom field map for Fiserv DNA user fields. This allows FIs to configure data to pass to Fiserv DNA user fields according to the FI's Fiserv DNA configuration. User fields can be set to a custom text value or be mapped to any of the following application data:
BSA responses
Employment Status
Occupation
Referral method

Expected Benefit: FIs can use Fiserv DNA user fields to track data from applications approved in the Alkami Digital Account Opening platform.

Activation: Open a JIRA Delivery ticket. The Jira Delivery ticket must include the user field codes and user field values to be added. May require a Client Change Request (CCR) if the request is to add a user field value that is not currently supported.

Delivery Channel: Desktop, Mobile App

Previous Behavior: User fields passed in the Fiserv DNA integration at account creation weren't configurable. These values were hard-coded for each project and couldn't be changed.

New Behavior: User fields passed in the Fiserv DNA integration at account creation are configurable. User fields can be set to a custom text value or be mapped to any of the following application data:
BSA responses
Employment Status
Occupation
Referral method

Product: Digital Account Opening Platform - Retail Digital Account Opening - FIS IBS

3rd Party Dependency: FIS IBS

Description: On FIS IBS, when creating new accounts, the customer record is selected using the following logic:
# If there are only prospects, create a new customer record.
# If there is more than one customer record select the latest one and update any missing fields.
# If there is more than one latest customer record on the same day select the one with a higher customer number.

Expected Benefit: Ensures that accounts are created under the appropriate customer record on the core.

Activation: Automatically Enabled/Resolved with the Release

Delivery Channel: Desktop

Previous Behavior: Accounts were created under the incorrect customer record.

New Behavior: Accounts are created under the most recent customer record that is a customer; not a prospect.

Product: DNA CoreAPI - Sync Core-hosted Transfers

3rd Party Dependency: Fiserv DNA core with Core API interface

Description: Resolved an issue where reading core-hosted transfers failed when one of the user's scheduled transfers didn't have an amount assigned in the core yet, DisplayTransfersBeforeAmountKnown was enabled, and neither the destination account next payment date nor the next payment amount due was available.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Core-hosted transfers were intermittently being read incorrectly and therefore some transfers failed to appear in online banking.

New Behavior: The transfer with the missing destination account information is filtered out and the remaining end user core-hosted transfers appear in online banking as expected.

Product: DNA CoreAPI - Sync Transactions

3rd Party Dependency: Fiserv DNA core with Core API interface

Description: Added the ability to control how credit transactions appear for loans. Since credits lower the balance of a loan, some FIs like to display loan credits as negative dollar amounts and loan debits as positive dollar amounts. However, some FIs believe this can be confusing to their end users and prefer loan credits to be positive dollar amounts and loan debits to be negative dollar amounts.

Expected Benefit: FIs can display loan credits in the desired format.

Activation: Configured by FI, new CoreAPI core provider setting: TrxnDisplayLoanCreditsAsNegative
Description: When TRUE, the Alkami Platform displays loan account credit transactions as negative numbers and debit transactions as positive numbers. When FALSE, ORB displays loan account credit transactions as positive numbers and debit transactions as negative numbers.
Format: Boolean
Default: TRUE
Required? No

Delivery Channel: Desktop, Mobile App

Previous Behavior: FI was unable to configure how loan credits appeared.

New Behavior: FI can configure how to display loan credits.

Product: DNA CoreAPI - Transfer

3rd Party Dependency: Fiserv DNA core with Core API interface

Description: Resolved an issue resulting in a transfer error when end user attempted a cash advance from their credit card.

Expected Benefit: Resolved an issue.

Activation: Automatically resolved with the release.

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user received a null reference error when attempting to make a cash advance from their credit card.

New Behavior: The end user can perform cash advances from credit cards successfully.

Product: DNA CoreAPI - Transfer

3rd Party Dependency: Fiserv DNA core with Core API interface

Description: Shortened transfer description wording: from _External_ to _Ext,_ and from _Transfer_ to _Xfer._ The new descriptions use fewer characters and provide more characters for additional description information.

Expected Benefit: More characters to provide space for more information in transfer descriptions.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Additional information was being truncated on transfer descriptions.

New Behavior: More information can be included in the transfer descriptions.

Product: Flux - Data Extract

3rd Party Dependency: N/A

Description: Alkami is releasing two new extracts, Transfer and BillPay, to provide a comprehensive set of properties for those data topics in the Alkami Platform. These extracts include the go-forward column naming standards and intend to be more efficient for FIs to consume, join with other extracts, and conduct offline analysis. They are intentionally not over reporting user data that is better sourced from dedicated user extracts as that creates multiple sources of truth for those data points. The Accounts extract has also been updated to use the go-forward column naming standards, include additional data on ACH accounts, and the extract name itself changed from the plural to singular in support of industry data model naming standards.

Expected Benefit: This collection of extracts enable FIs to track which accounts and transfers are utilizing new features such as IAV, RTP/FedNow, and Debit Card Instant Transfers.

Activation: Automatically enabled with the release of the extracts between July 8 - 19, 2024. The new Account extract is going to be released along side of the Accounts extract. This will provide FIs time to move from the Accounts source to Account. The Accounts extract will be deactivated on August 15th 2024. FIs can self-service activate the Transfer, BillPay, and Account extracts when they're ready through the Extract Management widget - {}Admin > Data > Extracts{}.

Delivery Channel: Admin

Product: IBS - Sync Transactions

3rd Party Dependency: FIS IBS core

Description: Added the check number from the core to the GeneralDescription for the Demand Deposit Accounts (check number) and loan (note increase) transactions.

Expected Benefit: The end user can see the check number on the transaction history screen without having to go into the transaction details.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The GeneralDescription for check transactions displayed {{{}CHECK{}}}.

New Behavior: The GeneralDescription for check transactions displays {{{}CHECK #1234{}}}. This change only impacts newly downloaded transactions.

Product: JHA SmartPay mRDC, for business customers/members

3rd Party Dependency: JHA SmartPay mRDC Purchase through Alkami

Description: JHA SmartPay mRDC is a commercial mobile remote deposit capture solution built exclusively for businesses. This application enables them to conveniently deposit checks anytime, anywhere using camera-enabled smartphones and tablets.

JHA SmartPay mRDC (formerly ProfitStars) provides the unique functionality businesses need, like the ability to accommodate multiple checks in a single deposit and make deposits into multiple accounts. The solution allows payment data to be added to deposits while tracking all deposit activity. It includes advanced risk mitigation tools and is supported by proven, customizable marketing materials and campaigns. Compatible with camera-enabled iOS and Android mobile devices, JHA SmartPay mRDC leverages the latest video capture technology to provide high image capture rates.

With the rise of businesses moving to remote work, there is a need for a mobile deposit functionality for business users. Alkami provides the ability for business RDC users the capability to use their mobile devices to access the mRDC platform through Alkami integration.

Mobile Deposit Features:
Supports multiple end users, each with login credentials.
Enables many checks to be included in a single deposit.
Allows deposits into multiple accounts.
Provides audit trails and detailed reporting.
Allows checks to be associated with customer account data.

Alkami won't provide an auto-launch subordinate app integration to the SmartPay business mobile RDC product (mRDC).
- JHA Smartpay will manage the application, like download, use, branding, and maintenance.
- JHA doesn't support connecting the Alkami platform to the mRDC app, this is not a sub-app. Business users need to download the app from the Apple or Google app store and access this app separately. They will not be able to go through the Alkami platform.

Expected Benefit: FIs can purchase the business-focused mRDC product through Alkami.

Activation:
Purchased from Alkami
Download the separate SmartPay mRDC app that the business user will download from the Apple or Google App Store.

Delivery Channel: The SmartPay mRDC App

Previous Behavior: N/A

New Behavior:* FIs can purchase the SmartPay mRDC app through Alkami, but it will be a separate app that the business user will download from the Apple or Google App Store.

Product: KeyStone - Transfer

3rd Party Dependency: Corelation KeyStone core

Description: Resolved an issue where the Alkami Platform creates an exception error on insufficient funds (NSF) transfers.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user sees an exception error on NSF transfers.

New Behavior: The end user sees an Insufficient Funds error on NSF transfers.

Product: KeyStone - Transfer

3rd Party Dependency: Corelation KeyStone core

Description: The core provider returns the proper errors for transfer requests to the core that timeout or fail due to insufficient funds. Scheduled transfers retry the transfer during the next scheduled transfer job.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Transfer requests to the core that failed, due to timeouts or insufficient funds, aren't retried during the next scheduled transfers job.

New Behavior: Transfer requests to the core that fail, due to timeouts or insufficient funds, are retried during the next scheduled transfers job.

Product: Loan Payments SSO offered by Paymentus

3rd Party Dependency: Paymentus Loan Payments

Description: Paymentus Loan Payments increases end users payment options and can offer greater control and convenience by expanding payment methods to include debit cards, digital wallets (for example, PayPal, Venmo, Google Pay, and Apple Pay), and traditional methods, such as eChecks or ACH.

Paymentus Loan Payments is powered by the Paymentus Instant Payment Network (IPN) and provides FIs with a dynamic omnichannel experience with convenient channel options, which include web, mobile apps, IVR (available in English and Spanish), CSR assisted, and chat/chatbot. Borrowers can also pay through the PayPal App and at 4,500+ Walmart locations

This platform can serve non-end users, loan only, and indirect loan types. This enables FIs to deploy an integrated solution that operates outside of their digital banking platform, as long as the FI offers loan products to non end users.

Omni-Channel Convenience

Powered by the IPN, Paymentus Loan Payments brings together today’s most popular payment channels to deliver the highest level of seamless convenience. Borrowers can pay through web, SMS, IVR, CSR-assisted and chat/chatbot channels, while the patented Secure Service{^}®{^} technology removes your PCI burden without compromising the end users experience.

More Payment Choices

More payment choices can drive a greater end user satisfaction, loyalty, and on time payments. Borrowers can receive real-time alerts and notifications by email and text.

Real-Time Reporting and Operational Management

The Agent Dashboard can be an easy to use command center that offers direct access to real-time online bill presentment and payment activity. With the Dashboard, you can drill down to detail-level data to optimize business decisions and segment information based on the preferred classifications.

Paymentus Loan Payments Features
E-bills - Paymentus allows for billing borrowers electronically, which avoids possible problems and delays with USPS or other methods.
Once delivered electronically, the loan payment can be made using the IPN. This includes several different payment types, methodologies, and channels.
Loan payments can be made if the borrower is an authenticated or unauthenticated digital platform end user. The Paymentus system creates a platform for consistent payment types along with a singular management tool to manage all their loan payments.
The borrower benefits from being able to make simple payments over many different channels with several payment type options.
The FI benefits by promoting billing and payments, which will possibly allow the FIs to receive their funds faster, through a management portal to manage and improve that process.

Expected Benefit: Fis will gain multiple payment options for their borrowers with traditional and alternative payment methods. Powered by the IPN, FIs can expand payment methods to increase the end users payment options. External channels can be offered that will include PayPal and in-person at 4,500+ Walmart stores nationwide.

Activation: This is an optional product. Contact your Client Success Manager to purchase

Delivery Channel: Desktop, Mobile App.

New Behavior: This is a new SSO for Loan Payments. FIs will work directly with Paymentus for configurations.

Product: OpenServices - Framework

3rd Party Dependency: CO-OP OpenServices credit card processor

Description: Added a default of EffectiveDate for the core provider setting {}TransactionDateSearchField{}.

Expected Benefit: The CO-OP OpenServices interface expects the transaction-read date range to be specified using the transaction effective date. When this configuration setting isn't specified, the Alkami Platform falls back to the system-wide configuration value. If the system configuration value is set to {}PostingDate{}, the wrong dates are specified when reading transaction. This can result in dropped transactions.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The wrong dates were specified when reading transactions, possibly resulting in dropped transactions.

New Behavior: With the default effective date specified, the correct dates are specified when reading transactions.

Product: P1C - Transfers

3rd Party Dependency: FIS Payments One - Credit (P1C) credit card processor

Description: Added the ability to notify P1C immediately of a payment made through the Alkami Platform.

Expected Benefit: The end user sees their payment immediately reflected in their credit card account.

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

Delivery Channel: Desktop, Mobile App

Previous Behavior: The end user doesn't see their payment immediately reflected in their credit card account.

New Behavior: The end user sees their payment immediately reflected in their credit card account.

Product: Platform - Sync Accounts

3rd Party Dependency: Fiserv XP2

Description: Resolved an issue where the Alkami Platform was deleting and then recreating external credit card accounts when the end user's credit card number changed. This resulted in lost transaction history and lost scheduled transfers.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: External credit card accounts were deleted and recreated when the end user's credit card number changed.

New Behavior: External credit card accounts remain when the end user's credit card number changes.

Product: Platform - Sync User

3rd Party Dependency: N/A

Description: Resolved an issue where householding sync was not working for cores that are not able to distinguish between business and non-business members.

Expected Benefit: Resolved an issue

Activation: Automatically resolved with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: Householding sync did not work for cores that are not able to distinguish between business and non-business members.

New Behavior: Householding sync works for cores that are not able to distinguish between business and non-business members.

Product: Premier CoA/CoO

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

Description: Set the Alkami account field DisplayName based on the core value in the following sequence: Nickname first, then Desc (Description), then AcctTitle (Account Title).

Expected Benefit: The end user sees more descriptive display names for accounts when they have not yet set a nickname for the account.

Activation: Automatically enabled with the release

Delivery Channel: Desktop, Mobile App

Previous Behavior: The Alkami account field DisplayName was set based on the core value Nickname first, then the core value AcctTitle. The Alkami account field DisplayName didn't include the core value {}Desc{}.

New Behavior: The Alkami account field DisplayName is set based on the core value Nickname first, then the core value {}Desc{}, then the core value AcctTitle.

Product: SavvyMoney Credit Score - Auto-Enrollment

3rd Party Dependency: SavvyMoney Credit Score

Description: Alkami supports the Auto-Enrollment service offered by SavvyMoney.

Expected Benefit: Data suggests that end users are more likely to interact with the SavvyMoney Credit Score widget if the credit score is automatically visible to them versus having to go through a manual registration process. By increasing engagement with the widget, FIs have more opportunities to promote financial literacy and credit-building strategies with their end users, and can present Pre-Approved and Pre-Qualified Offers to drive growth in their loan portfolios.

Activation: This is an optional product. Contact your Client Success Manager to purchase.

Delivery Channel: Desktop and Mobile App

Previous Behavior: End users had to register for SavvyMoney Credit Score manually, which disincentivized some end users from registering.

New Behavior: End users are auto-enrolled in SavvyMoney Credit Score by accepting a new online banking disclosure.

Product: Virtual Assistant - Glia - 3rd Party Messaging (optional product)

3rd Party Dependency: Glia

Description: FIs can add the Glia Virtual Assistant (GVA) through Glia-supported and licensed third-party messaging Channels (SMS, WhatsApp, Facebook, and Apple Business Chat). This includes one additional CMS instance with User Goal response templates that are optimized for supported third-party messaging channels.

Expected Benefit: GVA allows end users to receive self-service support that is available 24 hours a day 7 days a week. This allows FIs to expand their support capabilities to additional channels and reduce wait and handling times.

Activation: This is an optional product. Contact your Client Success Manager to purchase

Delivery Channel: 3rd Party Messaging App

Previous Behavior: N/A

New Behavior: End users can engage with a Glia Virtual Assistant (GVA) through third-party messaging channels.

!Glia GVA 3rd Party SMS Messaging.png|thumbnail!

Product: Youth Financial Education - Goalsetter (optional product)

3rd Party Dependency: Goalsetter

Description: Alkami now supports a single sign-on integration to the Goalsetter platform.

Expected Benefit: This allows end users to connect directly to the Goalsetter platform.

Activation: Open a JIRA Delivery ticket as this will require a CCR to configure.

Delivery Channel: {color:var(--ds-text, #172b4d)}Desktop, Mobile App{color}

Previous Behavior: Previously, there wasn't an integration to the Goalsetter platform.

New Behavior: Integration directly to the Goalsetter platform.