Deploying Banno apps

We make sure that distributing new versions of your app is as easy as possible. For the most part, there won’t be a lot to do on your end when it’s time to send your customers the newest and coolest features available! But sometimes, new requirements come in from Google Play or the Apple App Store that require some additional configuration on your end. When those times come, we make sure to give you the full rundown on what you need to do. We’ll send you anything you need to do directly through a monthly update, but in case you lost your email, we’ve got those updates covered below.

Certificate renewal

If there are any issues with the renewal process, an engineer will contact your institution. For Online certificate renewal questions, you can email launchcontrol@banno.com.

Banno

Our engineers take the certificate renewal process off your plate by automatically handling it. They have all required renewal dates on their calendar and it requires no action from your institution.

Engineers begin the renewal process two to four weeks out and install certificates about a week before expiration. As we order and install a certificate for Banno Online or CMS, your institution receives emails sent to the same address we used for validation when initially setting up your institution’s certificates (ex. postmaster@domain.com, admin@domain.com, etc). If you receive a validation email that sends at the same time we order a certificate, you can validate it or wait for us to validate the certificate on our end. After it’s validated, you will receive an email with the certificate.

Institutions

Overall tasks your institution manages include:

  • Accepting your Apple agreements.
  • Having a valid Apple developer membership.
  • Delegating the correct permissions to Banno.

Update app descriptions

Android

At any time, update the the Android description in the Play Store. The short description has an 80 character limit, and the long description has a 4,000 character limit.

iOS

Update the iOS description by opening a support case and letting us know exactly what you want in the description. We’ll update the description so that it displays in the next release. There’s a 4,000 character limit, and the first 170 characters display as the short description.


Android Application Keys

Start here

Upcoming changes to Google’s policy requires updating keys for your Android application. You’ll need to navigate between to two separate webpages to accomplish the update.

  1. Your Banno Enterprise platform
  2. Google Play Developer console
Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊
•⎯⎯⎯⎯➋
•⎯⎯⎯➌

Log into your Banno Enterprise platform, and select People (1). This takes you to the Dashboard and expands the menu on the left-side of the webpage. Next, select Settings (2) and then App Keys (3). Next, you’ll check your App Integrity settings within Google Play and determine whether you need to complete Option A Opt in to Play App Signing or Option B provide Banno with information about your signing key from Google.

Check your App Integrity settings

This tutorial is also available in video form.

Open a separate window, and log into the Google Play Developer Console using your owner credentials. Once you’ve logged in, you should see a screen similar to the following, but with your own applications:

Alt text

From the top 10 list, select your Banno application by clicking on it.

Alt text
•⎯⎯⎯➊

In the left hand menu, underneath Setup, select App Integrity (1).

Alt text
•⎯⎯⎯⎯⎯⎯➊

This takes you to the Play App Signing webpage. If the page displays Opt in to Play Signing (1), continue on to Option A Opt in to Play App Signing. If the page displays Google is managing your app signing key (2, below) and App signing key certificate (3, below), skip to Option B provide Banno with information about your signing key. You will only need to complete Option A or Option B, but not both.

Alt text
•⎯⎯⎯⎯⎯⎯➋
•⎯⎯⎯⎯⎯⎯➌

Option A Opt in to Play App Signing

This tutorial is also available in video form.
Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊

Return to the window open to *People* where you'll complete Option A. Select *Download Keys* (1) to download your `SigningKey.pepk` and `UploadKey.pem` key files. The key files will either automatically download, or you'll be prompted to download the two key files. If you're prompted, select *Save File* for each prompt.

Whether the two key files automatically downloaded or you were prompted to download them, you should be able to find the key files in your computer’s Downloads folder. You’ll need to access these files in a later step.

Alt text
•⎯⎯⎯⎯⎯⎯➊

Return to the window open to the *Opt in to Play Signing* webpage in your Google Console, select the center option, *Export and upload a key from Java keystore* (1). There is a lot of information on this page, but steps 1 and 2 have already been completed. We'll focus on steps 3 and 4.
Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊
•⎯⎯⎯⎯⎯⎯➋

Under step 3, click Upload private key (1). Choose the SigningKey.pepk file you downloaded earlier in People.

Under step 4, select Show instructions. Click Upload your upload key certificate (2). Choose the UploadKey.pem file you downloaded earlier in People.

Now that you’ve uploaded the files, the Save button in the bottom right-hand corner should be blue and clickable. Select Save, and the page will update to display several lines of data labeled fingerprint. This indicates a successful upload.

Finalize the setup by returning to the People webpage. Select Migration Complete. Once that’s selected, you’ll view the message Android application keys upgrade completed. No further action required.

This concludes the steps necessary for the Android application key upgrade. Now that you’re done, securely delete the SigningKey.pepk and UploadKey.pem files from your computer.

If you notice it says No android store key found. Set one now. under Android store key, stay calm. This is a separate, but necessary setup outlined in another tutorial.

Once you’ve finished opting in to Play App Signing, you’re done! You don’t need to complete Option B and provide Banno with information about your signing key.

Option B provide Banno with information about your signing key

This tutorial is also available in video form.
Alt text
•⎯⎯⎯⎯⎯⎯➊

On the *App signing key certificate* webpage, select *Download certificate* (1). The certificate file will either automatically download, or you'll be prompted to download the certificate file. If you're prompted, select *Save File* and then *OK* in the prompt. Whether the file automatically downloaded or you were prompted to download it, you should be able to find the certificate file in your computer's *Downloads* folder. You'll need to access this file in a later step.

Finalize the setup by returning to the People webpage where you’ll complete Option B. Select Provide information. Click Choose file. Search and select the file deployment_cert.der you just downloaded from the Google Console. You should be able to find the file in your computer’s Downloads folder. Click Open. Select Submit. Once that’s selected, you’ll view the message Android application keys upgrade completed. No further action required.

This concludes the steps necessary for the Android application key upgrade. If you notice it says No android store key found. Set one now. under Android store key, stay calm. This is a separate, but necessary setup outlined in another tutorial.

Once you’ve provided Banno with information about your signing key, you’re done! You don’t need to complete Option A and Opt in to Play App Signing.

Android Store Financial Features
During this process, you may be prompted to complete a Data Safety form. Please ignore the prompt and do not complete the Data Safety form. Our team is working on an update to that form ahead of a future deadline.
  1. After logging into Google Play, you’re presented with a list of your applications. Choose the application you’d like to complete by clicking on View App. These steps will need to be completed for all of your live applications, not just Jack Henry applications.

  2. Scroll down to the bottom of the left sidebar and click App Content.

  3. You’re then presented with a page stating that the Financial features declaration needs attention. Click Start on the Financial features declaration. The console may state that there is more than one declaration that needs your attention but you need only be concerned with the “Financial features” declaration. We’re in the process of working through the other outstanding declarations internally, the deadline of which is December of this year. We’ll likely be complete with these changes by the end of September.

  4. You’re then presented with the actual form. Fill out the form by checking the boxes of the features you provide directly in the application. This includes features available from your plugins and SSO options. Click Next once you’ve reviewed the entire form. If you provide any of the following from within the application, you’ll have to provide further documentation to Google about the lending provider:

  • Personal loan direct lender
  • Loan facilitator
  • Payday loans
  1. Unless your app has any of the features mentioned in step 4, you’ll be presented with a screen stating that you do not require further documentation. If you’re required to provide further documentation, please walk through that process. Once you’re done, click Save on this page.

  2. You’ll the be presented a modal, click Go to overview

  3. Once you click, Send for review, you’ll be done with the financial features form.


Setting up App Store Connect API keys

It’s important for your end users to get new builds as quickly as possible. Whether they’re getting vital new features or the hottest performance improvements, we can ensure your end users always have the newest builds as soon as they’re available. Better still, setting up the App Store Connect API Keys that make this possible is a straightforward process, and we’ve outlined it below.

Enabling App Store Connect API key generation

First, you’ll need to log into App Store Connect.

Alt text
•⎯⎯⎯⎯⎯⎯➊

Select Users and Access (1) to continue.

Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊
•⎯⎯⎯⎯⎯⎯➋

Select the Keys heading (1), then the Request access button (2), which displays the submission dialogue.

Alt text
•⎯⎯⎯⎯➊
•⎯⎯⎯⎯⎯⎯➋

Check the agreement box (1) and click Submit (2) to see your App Store Connect API approval.

This screen means your setup was successful and your job is done! If you have any questions, contact your support representative.


Migration

Banno is a pretty amazing platform for for community banks and credit unions, yet we understand you might find a reason to change. If your institution migrates from Banno, your end users can be guided with a hard or soft prompt to download a link that acquires the new mobile app. At the start of your migration, you’ll work with Banno Support to configure which prompts and messages are right for you.

How does it work?

Soft prompt

If you choose to guide your end users with a soft prompt, the prompt allows them to log in to the app. Upon login, end users can choose to immediately download the new app or wait. If they wait to download the new app, the soft prompt will display on every single successful sync when the end user logs in. Our goal is to consistently remind the end user to download the new app and begin using it.

Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➋

Here’s a template to get you started:

Headline (1)
A new version of this app is available! The headline is non-customizable.
Message body (2)
This version will stop working on [insert date]. Please download and begin using the new version of our app today. The message body is customizable.
Not now
The Not now button dismisses the prompt. For Android end users, they can also click anywhere outside of the prompt to dismiss it. This button is non-customizable.
Download
The Download button links to the new app in the App Store or Google Play Store where the end user can then download the new app. This button is non-customizable.

Hard prompt

If you choose to guide your end users with a hard prompt, this prompt blocks them from logging into the app and directs them to download the new app.

Alt text
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊
•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➋

Here’s a template to get you started:

Headline (1)
This version of our app is no longer available. The headline is non-customizable.
Message body (2)
Please download and use our new app to login and access your account. The message body is customizable.
Download
The Download button links to the new app in the App Store or Google Play Store where the end user can then download the new app. The button text is non-customizable.

FAQ


How does Banno migration differ from goDough?
Our migration differs from goDough in that we display static text instead of a countdown timer that updates the end user on how many days until the app discontinues.

Mobile Store Setup Videos

In addition to our written documents outlining the steps for setting up keys and accounts for mobile stores, our operations team creates videos outlining the process in detail. See what’s available below.

Android store setup


FAQ


How often are new app versions deployed?
New app versions deploy once each month, but there’s no deployment in January.
How are institutions informed of app deployments?
Prior to uploading new app versions to the iOS and Android app stores, we publish release notes on ForClients.
Do institutions have the opportunity to test apps prior to deployment?
No, we automatically publish new app versions to live institutions.

Articles in this section