Thankful for your partnership

As we head into the holiday season we want to express our heartfelt gratitude for your continued trust and collaboration. It is truly a joy to work alongside you to create meaningful, innovative solutions that impact the lives of your accountholders. We’re inspired every day by your commitment to your communities and it’s an honor to help you succeed. Thank you for being part of this journey, for your friendship, and continued support.

Matt Kerner
Senior Director of Product

Attach ACH batches in Conversations

We've been hard at work on a better way for business users to engage with one another — and with your Support team — regarding ACH batches. What better way to engage than with a conversation?

Authorized Banno Business users will soon have the option to attach ACH batches to Conversations for Business. Similar to attaching transactions, accounts, and bill payments, this feature will let your accountholders more easily share context with your staff and their fellow organization members. Here's what to expect:

• Initial release: Business users can attach batches to conversations, providing much-needed context for resolving issues. Using Banno Support, your staff can also send a batch list request that lets the accountholder click a button to open their batch list and provide missing context.
• Future releases: Conversation participants will be able to interact with attached batches. Functionality will include editing, initiating, or approving the batch by linking to it directly from the conversation.

As part of our larger push toward keeping sensitive discussions inside the authenticated channel, we're also working on the option to attach wires to Conversations! We will provide more information on this Wires feature once ISO 20022 is in the rearview.

No support case is required for attaching ACH or attaching wires, as we will automatically roll out both features (respectively) once they're built, tested, and ready to use! Keep an eye on future statements for more details and timelines.

Updates to the Jack Henry Digital Terms of Use

We are updating our Digital Terms of Use, also known as the End User License Agreement (EULA), effective February 5, 2025. On or after the effective date, all end users on the Digital Online Banking Platform will need to review and agree to the updated Digital Terms of Use to continue accessing the platform.

What's changing?

These changes create a more consumer-friendly explanation of Jack Henry’s role as a service provider and the end user’s rights, permitted use, and obligations when using the Digital Online Banking Platform.

Key updates include:

• Alignment with Jack Henry’s branding by removing references to Banno Online and Banno Mobile.
• Expanded explanation of privacy laws and end user rights regarding platform usage.
• Definitions for “account information” and “registration information.”
• Details about enabling and using optional platform features.
• Introduction of the JH Conversations chat feature with AI Assist.
• Clarifications on rights and responsibilities related to unauthorized access and use.
• Enhanced information about using the platform on mobile devices, including technical standards and compatibility requirements.
• Explanation of service-related alerts from the platform.
• Clarification of risks associated with using the platform over telecommunication networks.
• Description of Jack Henry’s role in translating the platform.
• Additional details regarding termination and suspension rights for both Jack Henry and end users.

Note: As we continue to expand on these updates, we will send a final service level announcement (SLA) with a reminder and final list of these key updates.

We encourage you to familiarize yourself with these updates before the effective date to ensure compliance and a seamless experience. Thank you for your understanding and support of the Digital Banking Platform.

Mobile push notification update

As we’ve announced in recent statements, we will be updating how we send push notifications in Banno Mobile next month. This change will occur in Mobile version 3.19, which is expected to land in app stores in early December.

Once Mobile version 3.19 rolls out, previous versions will no longer receive push notifications, so it will be critical to ensure your institution is set up to receive the latest versions. We’ll continue to update you, but in the meantime, ensure you’re set up for auto-app-deployments. If you aren’t, you can follow these steps.

Enhanced Default 2FA Methods

As a reminder, we want to make sure you are ready for the new 2FA functionality announced in our September issue! This change will be available soon, so keep your eyes peeled for updates on this upcoming feature in our next digital statement.

At roll out, Security Levels will be set to Standard. The institution will then have the control of requiring higher security levels based on user type (retail vs. business). In addition, we are introducing configurable step-up authentication methods for high-risk actions (Passkeys + 2FA OR Passkeys + Password).

As a part of this project, we will be activating all 2FA methods for you. We encourage you to begin testing FIDO keys as soon as possible. No support case is needed to access this feature once available. To learn more about 2FA methods, passkeys, high-risk actions, and more, check out this Knowledge Base article.

Identity App for Financial Institutions

Reminder for our credit union business institutions! We are preparing to release the Identity App, part of the Unified Identity Service (UIS), which aims to provide a secure, user-friendly application for managing consumer users.

Currently, financial institutions are able to manage security settings such as password resets, 2-step verification, passkeys, and devices in People. At roll out, this functionality can be managed in either People or the Identity App. It is important to note that this functionality will eventually be removed from People. For more information about UIS or the Identity App, head over to this Knowledge Base article!

🎗️Forget-me-nots

Here are a few things to remember this month!

Block high-risk actions on new devices

We recently announced this highly awaited feature in the October statement! In case you missed it, your employees with the Manage security settings permission now have access to activate this powerful feature set, which includes three options that put you in control of how high-risk actions are managed. With these controls, you can stop fraudsters in their tracks and protect your accountholders like never before!

For more information, see the High-risk actions section in our Digital Banking Security documentation on the Knowledge Base.

Upcoming events

Save your seat now for these upcoming events:

• Digital Toolkit Meetup: Don't forget to join us on Tuesday, December 10, 2024 at 11:00 a.m. CT
• Digital Banking Meetup: Don't forget to join us on Friday, December 13, 2024 at 11:00 a.m. CT
• Digital Security Meetup: Don't forget to join us on Wednesday, February 5, 2024 at 3:00 p.m. CT

Toolkit corner: User Support with the Admin API video

Many of you have asked: “How do I use the Admin API in tandem with my existing user support tools?”

The good news is that the Developer Relations team has put together a new video, Support with the Admin API, that describes how to use that part of the Digital Toolkit for that very purpose.

The DevRel team also updated the existing guide, Building User Support Tools, with that same video as a companion to the content contained within the guide.

Wire Transfer migration to ISO 20022

The compliance deadline for ISO 20022 is quickly approaching in March, and your Banno and Treasury Management product teams are hard at work to ensure a smooth transition. This migration represents a shift from the current FAIM messaging standard to ISO 20022, a new global standard that supports more detailed and structured financial messaging.

At this time, no action is required on your part, as we’re managing all aspects of the migration to meet the compliance timeline. We’ll be sharing more information soon, but for now, please visit the Wires page on the Knowledge Base to read more about key terminology changes that will take place as part of this migration.

Treasury Management customers— for more information, visit the For clients page!

Minimum version requirements for browsers and operating systems

As discussed in the most-recent Digital Banking Meetup and the October Statement, starting with Banno Mobile 3.19 release in December 2024, the minimum supported Android operating system (OS) version will change to Android OS 9.

In March 2025, our minimum-supported Banno Mobile app version will become Mobile 3.19.

Why Banno Mobile 3.19 is particularly important

Version 3.19 of the Banno Mobile app includes key updates such as anchor device enhancements, and more. To fully benefit from and leverage these features, especially those tied to authentication and security, it is critical that your personnel encourage end users to upgrade to the latest version.

Things to keep in mind

As the March timeframe approaches, please remind your support teams to verify that end users have upgraded to Banno Mobile version 3.19 or newer before attempting to troubleshoot issues.

Earlier versions of our Mobile app will still support basic functionality. However, the latest version is always strongly recommended for optimal performance and access to new features—including the always-important security enhancements.

Note: Automatic updates may not be enabled for everyone, so proactive communication and support are essential. Let's ensure readiness for this important milestone!

Electronic Statements Interactive (ESI) Multi-Doc Download Enhancement

As announced via SLA on November 15, the Multi-Doc Download and large document support enhancement is now enabled for most ESI financial institutions (see eligibility restriction below).

This enhancement allows users to select one or more documents to download with a single click and enhances the previously released feature of document filtering.

When a user selects one or more documents from their filtered results, the Download button becomes active. When clicked, the browser begins downloading the documents and placing them in the Downloads folder when complete.

There is no action require to receive this enhancement, and is available for eligible Banno FIs via the ESI SSO.

Eligibility Restriction: Currently, the enhancement is not available for Banno FIs using Full Service Credit.

Treasury Management - Holiday processing reminders

Don’t forget to make any needed updates to your Processing Cut-off Times for ACH, Wires, Exceptions, etc. for the Thanksgiving and Christmas holidays!

From TM Back Office, select Configuration > Processing Configuration > Processing Times to make updates. You can remove an entire date from the processing calendar by using the Holiday Exceptions feature. Within the Processing Configuration page, shown above, select Holiday Exceptions from the menu on the left. Adding an exception disables the date for end-user selection for all payment types.

Configurable waitlist for high-risk action blocking

As we’ve worked through feedback from beta testers and our earliest users of the new high-risk action blocking features, we will be implementing a small change that gives you more control over the waitlist setting. Specifically, you’ll soon be able to choose how long new devices will be waitlisted for.

You won’t need to request this when it is ready, and we’ll share more information on this enhancement soon.

Reminder: API Scope Management Changes Coming Soon

This is a friendly reminder about the upcoming changes to API scope management. Starting December 17, 2024, all new consumer applications will require defined scopes to enhance security and user privacy.

What are API scopes?

API scopes control access to specific parts of your API, ensuring that only authorized users and applications can access the necessary data.

Key takeaways:

• New applications: Any consumer application added after December 17th must have defined scopes.
• Existing applications: Existing applications are legacied and can continue using all scopes. However, if you edit a legacied application after December 17th, you must define its required scopes.

Thank you for your understanding and cooperation as we work to improve security for everyone.

Power up your PowerOns: Member to Member Transfers

We wanted to make you aware that we have an updated version of the Member to Member Transfers PowerOn that contains several miscellaneous bug fixes as well as a couple of enhancements to the Member to Member Transfers PowerOn. The enhancements are related to how the program determines if a recurring transfer can be edited.

To receive more details about these updates, or if you are interested in upgrading your Member to Member Transfers PowerOn to the latest version, please submit a Support case on the For Clients portal.

Need to check your Member to Member Transfers PowerOn version? Follow these steps.

Documentation updates

Visit the JH Digital Knowledge Base to see our most recently updated docs:

• Security: Brush up on 2FA methods, passkeys, high-risk actions, and more.
• Banno Language Support: Be sure to explore this overview of how we deliver an exceptional user experience across multiple languages.
• Unified Identity Service: Check out our latest documentation related to our Consumer Authentication platform and the new Identity App!
• Wires: Don't forget to read up on the new terminology related to the new ISO 20022 updates.